cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-671) Config defaults behavior is inconsistent
Date Tue, 05 Jan 2010 23:05:54 GMT

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

Jonathan Ellis commented on CASSANDRA-671:
------------------------------------------

if we're talking wholesale rewrite (which isn't a bad idea imo), http://jyaml.sourceforge.net/tutorial.html
looks like it would require a lot less boilerplate than our current mostly-hand-rolled-xml
approach.  and be a lot more human-readable too.

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


Mime
View raw message