hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-8294) Make HBaseConfiguration a singleton class
Date Tue, 09 Apr 2013 06:12:17 GMT

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

stack commented on HBASE-8294:

bq. Ideally, we would like to have just one configuration object in the jvm.

Definitely do not want this in tests -- it is fundamental to quite a few tests that we can
float a different Configuration per daemon (e.g. so different 'Users' on hdfs).

In client, you can ask for new connection by specifying a new Configuration so being able
to have a new Config instance is important currently.

On server, there has been various juggling of the Configuration instance to do things like
a per column family 'view' on Configuration to do stuff like dynamic config.

I'd say call it out as a heavyweight construction and close as Invalid at least until there
is a better reason for changing how we treat Configuration.
> Make HBaseConfiguration a singleton class
> -----------------------------------------
>                 Key: HBASE-8294
>                 URL: https://issues.apache.org/jira/browse/HBASE-8294
>             Project: HBase
>          Issue Type: Improvement
>          Components: master, regionserver
>    Affects Versions: 0.95.0
>            Reporter: Himanshu Vashishtha
>            Assignee: Himanshu Vashishtha
> HBaseConfiguration.create() calls a new Configuration object. Ideally, we would like
to have just one configuration object in the jvm.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message