You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Doug Meil (JIRA)" <ji...@apache.org> on 2013/04/08 20:47:16 UTC

[jira] [Commented] (HBASE-8294) Make HBaseConfiguration a singleton class

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

Doug Meil commented on HBASE-8294:
----------------------------------

Just out of curiosity, what if you had a client that wanted to connect to 2 different clusters?  (e.g., a copy job from from cluster to another).  How would that be affected by making this a singleton?
                
> 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