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 Mon, 25 Jan 2010 17:30:34 GMT

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

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

I suggested this last year but haven't gotten around to producing a patch: the Apache Commons
Configuration classes work well and support various data backends.  http://commons.apache.org/configuration

>From the main page:

 Configuration parameters may be loaded from the following sources:

    * Properties files
    * XML documents
    * Windows INI files
    * Property list files (plist)
    * JNDI
    * JDBC Datasource
    * System properties
    * Applet parameters
    * Servlet parameters

Different configuration sources can be mixed using a ConfigurationFactory and a CompositeConfiguration.
Additional sources of configuration parameters can be created by using custom configuration
objects. This customization can be achieved by extending AbstractConfiguration or AbstractFileConfiguration.


I'd say that's substantially better than just YAML if it works.  I haven't used it with anything
but Java property files and XML, though, so I'm not claiming it's a panacea.

Ted


> 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