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

["Jeffrey Manno (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ACCUMULO-2330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jeffrey Manno resolved ACCUMULO-2330.
-------------------------------------
    Resolution: Not A Problem

ClientConfiguration was deprecated and replaced in 2.0

> Use CompositeConfiguration for ClientConfiguration
> --------------------------------------------------
>
>                 Key: ACCUMULO-2330
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2330
>             Project: Accumulo
>          Issue Type: Improvement
>            Reporter: Christopher Tubbs
>            Priority: Major
>              Labels: newbie
>
> {{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
(v8.3.4#803005)