hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Elliott Clark (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-8294) Make HBaseConfiguration a singleton class
Date Mon, 08 Apr 2013 18:57:16 GMT

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

Elliott Clark commented on HBASE-8294:

Keeping it not a singleton allows testing to be independent much easier.  It also allows a
more fine grain control over Hconnections and allows two clients to connect to different clusters.

I don't think that we should make it a singleton, perhaps we should add a function to get
a shared version of the config (maybe getSingleton() )?  Then recommend that method for most
users.  This would still allow advanced users to decide how to create their own 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