[
https://issues.apache.org/jira/browse/CASSANDRA-671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12828163#action_12828163
]
Ted Zlatanov commented on CASSANDRA-671:
----------------------------------------
Would it make sense to write a tool that generates/checks the configuration,
whatever the backend? It could be hooked into the Debian package and would
alleviate user configuration errors. It would generate the configuration as a
data structure and then convert it to the storage backend of choice. It would
also warn and insert any missing parameters. This would be independent of the
internal Cassandra validation but maybe they can share a common definition of
the parameters and their default values.
> 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.
