cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Blose (JIRA)" <>
Subject [jira] Commented: (CASSANDRA-671) Config defaults behavior is inconsistent
Date Wed, 14 Apr 2010 06:50:53 GMT


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

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:
>             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:
For more information on JIRA, see:


View raw message