[jira] Commented: (CASSANDRA-671) Config defaults behavior is inconsistent

["Jonathan Ellis (JIRA)" <ji...@apache.org>]

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

Jonathan Ellis commented on CASSANDRA-671:
------------------------------------------

Why xml [and anything else where you can't just say "give me a config object from that file over there"] sucks as a configuration format: http://stereolambda.wordpress.com/2010/03/19/why-is-json-so-popular-developers-want-out-of-the-syntax-business/

> Config defaults behavior is inconsistent
> ----------------------------------------
>
>                 Key: CASSANDRA-671
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-671
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>         Environment: debian lenny amd64 OpenJDK 64-Bit Server VM (build 1.6.0_0-b11, mixed mode)
>            Reporter: Brandon Williams
>            Priority: Minor
>             Fix For: 0.7
>
>
> Some configuration options when not present in the config file, such as MemtableObjectCountInMillions, will provide a default.  Others, such as DiskAccessMode will bail with a cryptic error.  Behavior amongst all the options should be consistent, and warnings should be emitted if defaults are being used.

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