You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@accumulo.apache.org by "Christopher Tubbs (JIRA)" <ji...@apache.org> on 2014/02/06 01:46:09 UTC

[jira] [Created] (ACCUMULO-2330) Use CompositeConfiguration for ClientConfiguration

Christopher Tubbs created ACCUMULO-2330:
-------------------------------------------

             Summary: Use CompositeConfiguration for ClientConfiguration
                 Key: ACCUMULO-2330
                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2330
             Project: Accumulo
          Issue Type: Improvement
            Reporter: Christopher Tubbs


{{ClientConfiguration}} optionally gets its values from multiple sources... either from a set of defaults, a set of well-known locations, or from a file specified explicitly.

It could do this in an priority hierarchy using commons-configuration's {{CompositeConfiguration}}.

One of these layers could also be the system properties, so they can be used to interpolate user configuration. I'm not sure how much value this would add to {{ClientConfiguration}} today, but it could be useful in the future for things like specifying a default namespace to connect to that corresponds to {{$\{user.name\}}}



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)