You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Todd Blose (JIRA)" <ji...@apache.org> on 2010/04/14 08:52:48 UTC

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

     [ https://issues.apache.org/jira/browse/CASSANDRA-671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Todd Blose updated CASSANDRA-671:
---------------------------------

    Attachment: storage-conf.yaml

> 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
>
>         Attachments: storage-conf.yaml
>
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira