[
https://issues.apache.org/jira/browse/ACCUMULO-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Elser updated ACCUMULO-1726:
---------------------------------
Fix Version/s: (was: 1.7.0)
1.8.0
> Typed configuration framework
> -----------------------------
>
> Key: ACCUMULO-1726
> URL: https://issues.apache.org/jira/browse/ACCUMULO-1726
> Project: Accumulo
> Issue Type: Improvement
> Reporter: Christopher Tubbs
> Assignee: Christopher Tubbs
> Fix For: 1.8.0
>
>
> The old Property enums were great, but now that we're looking at similar
> things for client-side configuration (for ACCUMULO-1009 and others), a more
> generic framework might be useful.
> Ideas:
> * The configuration objects themselves should be generic
> (org.apache.commons.configuration.Configuration, or java.util.Properties
> preferred... probably the former) so as to be flexible in their construction.
> * The possible keys in the configuration objects should be enumerated and
> come from a scope-specific source (example: MonitorProperties,
> TServerProperties, ClientProperties)
> * Use java generics, something like MonitorConfiguration extends
> TypedConfiguration<MonitorProperties> and TypedConfiguration<T> extends
> Configuration and MonitorProperties extends TypedProperties.
> * Sources should be combinable to support multiple scopes in a single
> configuration.
> * Basic types should be provided and extensible, and validated by the
> framework.
> * Values should be retrievable as any type, provided they validate as the
> target type.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
