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

Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2019/01/15 19:26:00 UTC

[jira] [Commented] (HBASE-21724) Introduce a createClusterConnection method in ClusterConnectionFactory

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

stack commented on HBASE-21724:
-------------------------------

Maybe we should call it something other than ClusterConnection now?  Or break up the CC Interface?  Or just prune it back to be about extra-Connection details?

In CC Interface there is some stuff that pertains to Connection allowing you get more detail on the Connection:hasCellBlockSupport, getConnectionMetrics, getBackoffPolicy, getStatisticsTracker, clear caches, get nonce, etc. This stuff seems like it should be available on any Connection, no?

Other stuff though is just about operation: getting client/admin on particular ServerNames or getting table and master state. Then there is the getting of an hbck Service....

Moving ClusterConnection to be in server only and not in client package seems to cut the client off from valuable faciilty?

> Introduce a createClusterConnection method in ClusterConnectionFactory
> ----------------------------------------------------------------------
>
>                 Key: HBASE-21724
>                 URL: https://issues.apache.org/jira/browse/HBASE-21724
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Duo Zhang
>            Priority: Major
>
> When we want a  cluster connection in the code, we should use this method to create one directly, instead of casting the one created by ConnectionFactory.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)