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

Todd Blose commented on CASSANDRA-671:
--------------------------------------

I went ahead and created a sample YAML alternative config (attached). I didn't 
include any comments on what the values actually represent in order to keep the 
config concise and easily readable. 

I really like how this looks, and pending approval, I could make advances 
towards rewriting DatabaseDescriptor for parsing the YAML config instead.

In addition to this, it'd be nice to have a script that actually runs the user 
through generating a config during installation. For each option, the user 
would be allowed to enter some value or permitted to skip it and use a default. 
The user could skip the entire process and just go with an entirely "default" 
config. This way, all config values would be explicit and determined by the 
user.

Finally, if for some reason config option(s) cannot be found, a list of those 
would be returned on startup, instructing the user to supply those values or to 
re-generate the config using the script.

Thoughts on 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.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.
-
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

        

Reply via email to