hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-13936) Improve configuration framework
Date Sat, 27 Jun 2015 00:15:04 GMT

    [ https://issues.apache.org/jira/browse/HBASE-13936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14603821#comment-14603821
] 

Andrew Purtell commented on HBASE-13936:
----------------------------------------

bq. Moving from Configuration to ConfigurationManager 
(In the doc)

Are you are referring to o.a.h.conf.Configuration? If so, we inherited this, and XML site
files, back in the distant past when we were part of the Hadoop project. If we're going to
move away from Hadoop-style configuration for 2.0 or later then we can get away from that
class somewhat, however, use of Configuration (or classes derived from it) will still required
when interacting with Hadoop's filesystem abstractions and HDFS. 

Ideally we don't just outright replace our configuration with a new format. This implies keeping
Configuration or emulating Hadoop style site files with whatever we are replacing it with.
Consider Log4j as an example. If you try to go from v1 to v2, you go from properties style
configuration to a new XML format that might as well come from Mars, and depending on configuration
it can be impossible to come up with an identical configuration for v2. Whatever the outcome
of this project, can we agree not to subject our users to that type of experience?

> Improve configuration framework
> -------------------------------
>
>                 Key: HBASE-13936
>                 URL: https://issues.apache.org/jira/browse/HBASE-13936
>             Project: HBase
>          Issue Type: Umbrella
>            Reporter: Apekshit Sharma
>         Attachments: DynamicConfigs.v01.docx, design.png
>
>
> Here's the design doc: https://docs.google.com/document/d/1WiO2bqguR2DaVT-J2SZTCONbQ3pEhpbOI_bbLMaXRjE/edit#
> Main changes:
> get*("foo.bar", default_value)  ---> get*(HConfig.FOO_BAR)  // using enums
> Robust framework and better documentation for dynamic configurations.
> Basic overview of new design:
> !design.png!



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message