cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Zlatanov (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-671) Config defaults behavior is inconsistent
Date Tue, 26 Jan 2010 13:58:34 GMT

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

Ted Zlatanov commented on CASSANDRA-671:
----------------------------------------

The point is you're unhappy with XML and YAML by itself locks you into another format you
may dislike later.  With ACC you can switch the format but keep the logical structure.  If
you're switching anyway, why lock into another limited format?  YAML doesn't even support
content encodings properly (UTF-8 and UTF-16 are de facto standards but can't be specified
as with XML).  In any case, you can do a YAML backend to ACC if you must have YAML configurations.
 From experience supporting YAML configurations though, I'd be wary: people see text and assume
it's free-form like a normal Unix config file, so they edit and break it.

The important point is, ACC will let you enforce defaults, validate the configuration, and
everything else you've listed.  Plus it supports includes, which YAML (with YamlBeans) does
not.  ACC is really a configuration framework while YamlBeans is much more limited.


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


Mime
View raw message