[
https://issues.apache.org/jira/browse/CASSANDRA-1000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Blose updated CASSANDRA-1000:
----------------------------------
Description:
This is to ensure existing users will have no issues making the transition to
YAML (CASSANDRA-990).
This will be a new Java program (that can be run via a shell script in bin) to
convert an existing XML config to YAML. The converter program will extract the
config values from the XML, and build a new YAML document according to the
schema outlined in CASSANDRA-990. The new config will reside in the same
location as the previous config.
was:
This is to ensure existing users will have no issues making the transition to
YAML (CASSANDRA-990).
The easiest way of accomplishing this to me would involve a single perl script
that takes as input the original XML config. The config would then be handled
by an XML parser to extract the values contained in it. After that phase, the
data would then be serialized to YAML and dumped into the new document,
according to the schema outlined in CASSANDRA-990. Therefore, migrating to the
new configuration would involve nothing more than calling the script with the
original configuration file as input.
> Create migratory script to generate new YAML config from cassandra.xml
> ----------------------------------------------------------------------
>
> Key: CASSANDRA-1000
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1000
> Project: Cassandra
> Issue Type: Task
> Components: Core
> Reporter: Todd Blose
> Assignee: Todd Blose
> Attachments: CASSANDRA-1000.patch
>
>
> This is to ensure existing users will have no issues making the transition to
> YAML (CASSANDRA-990).
> This will be a new Java program (that can be run via a shell script in bin)
> to convert an existing XML config to YAML. The converter program will extract
> the config values from the XML, and build a new YAML document according to
> the schema outlined in CASSANDRA-990. The new config will reside in the same
> location as the previous config.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
