Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Message-ID: <12547987.3991271647489508.JavaMail.jira@thor>
Date: Sun, 18 Apr 2010 23:24:49 -0400 (EDT)
From: "Stu Hood (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Subject: [jira] Commented: (CASSANDRA-990) Replace cassandra.xml with
 cassandra.yaml
In-Reply-To: <26469654.3441271397084930.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CASSANDRA-990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12858372#action_12858372 ] 

Stu Hood commented on CASSANDRA-990:
------------------------------------

Hey Todd, thanks for the update. I talked with a dev, and he agreed that we need a conversion tool to ensure a smooth transition. Could you open another issue to implement that utility, and link it to this issue? They should probably be merged around the same time.

> Replace cassandra.xml with cassandra.yaml
> -----------------------------------------
>
>                 Key: CASSANDRA-990
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-990
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 0.7
>            Reporter: Todd Blose
>            Assignee: Todd Blose
>         Attachments: CASSANDRA-990.patch, cassandra.yaml, cassandra_yaml_w_comments.txt, snakeyaml-1.6.jar, test_conf_cassandra.yaml.txt
>
>
> This is an entire rewrite of the XML storage configuration to YAML, inspired by the discussion in CASSANDRA-671.
> DatabaseDescriptor now parses conf/cassandra.yaml. It behaves the same way as before, but instead of dealing with an XML parse tree, a yaml parser is now created that associates a custom Java class (Config) with the entire config. In addition, keyspace and column family YAML entries are deserialized to new Keyspace and ColumnFamily instances, respectively.
> This was implemented using SnakeYaml (http://code.google.com/p/snakeyaml/).
> There are numerous benefits to this new approach: 1) a complete shifting away from an outdated, verbose data format 2) a cleaner, less bulky, human-readable config 3) significantly less code 4) simplicity of obtaining default values 5) trivial to update the keyspace and column family schemas
> Attached along with the patch are the replacement configurations for conf/cassandra.xml and test/conf/cassandra.xml, to emphasize the benefits of the transition, should the community approve of it. I included one version with comments and one without.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.