You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2010/01/05 23:27:54 UTC
[jira] Commented: (CASSANDRA-671) Config defaults behavior is
inconsistent
[ https://issues.apache.org/jira/browse/CASSANDRA-671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12796877#action_12796877 ]
Jonathan Ellis commented on CASSANDRA-671:
------------------------------------------
As a Python guy at heart, I am attracted to the "explicit is better than implicit" approach and requiring all options to be present in the config file. Is there any downside to this?
> 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.9
>
>
> 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.