[
https://issues.apache.org/jira/browse/CASSANDRA-1000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12859180#action_12859180
]
Todd Blose commented on CASSANDRA-1000:
---------------------------------------
Patch attached.
Summary:
- new shell script in bin to initiate the conversion: config-converter
- new Converter class in org.apache.cassandra.config. It locates the old config
using the classpath (looks for both cassandra.xml and storage-conf.xml), uses
XmlUtils to extract the old values, and finally generates the new config to
where the previous config resided (with the obvious name change).
> 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).
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
