[jira] [Resolved] (ACCUMULO-1726) Typed configuration framework

["Christopher Tubbs (Jira)" <ji...@apache.org>]

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

Christopher Tubbs resolved ACCUMULO-1726.
-----------------------------------------
    Resolution: Won't Fix

I started an experiment with doing this as a separate library at https://github.com/ctubbsii/blazon but didn't get very far. If this still matters, we can open a new issue at https://github.com/apache/accumulo/issues

> 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
>            Priority: Major
>
> 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
(v8.3.2#803003)