hbase-issues mailing list archives

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

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

Apekshit Sharma commented on HBASE-13936:

I think that Hadoop style site files is an good design and it should be left as such. The
scope of this project and the design changes we have thought so far (in the doc) will be invisible
to the users and will only impact dev.

bq. Moving from Configuration to ConfigurationManager

So the basic idea is to encapsulate Configuration within ConfigurationManager and provide
a better API for handling configurations. That will help in building a better framework for
dynamic configurations, type check configuration values, and get rid of few other bad patterns.
Since the aim here is to promote right patterns (and possibly design the framework so that
it's not possible to go otherwise), I will highlight major issues here and get everyone's
[~apurtell] On that note, what do you about the issue of set*() functions (my last post).

> 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

View raw message