hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Appy (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-19200) make hbase-client only depend on ZKAsyncRegistry and ZNodePaths
Date Tue, 14 Nov 2017 20:28:00 GMT

     [ https://issues.apache.org/jira/browse/HBASE-19200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Appy updated HBASE-19200:
-------------------------
    Release Note: 
ConnectionImplementation now uses asynchronous connections to zookeeper via ZKAsyncRegistry
to get cluster id, master address, meta region location, etc.
Since ZKAsyncRegistry uses curator framework, this change purges a lot of zookeeper dependencies
in hbase-client.
Now hbase-client only depends on only ZKAsyncRegistry, ZNodePaths and the newly introduced
ZKMetadata.

  was:Remove ZooKeeperRegistry, make ConnectionImplementation depend on ZKAsyncRegistry directly.
And also purge the zookeeper dependencies for hbase-client, now hbase-client only depends
on ZKAsyncRegistry, ZNodePaths and the newly introduced ZKMetadata.


> make hbase-client only depend on ZKAsyncRegistry and ZNodePaths
> ---------------------------------------------------------------
>
>                 Key: HBASE-19200
>                 URL: https://issues.apache.org/jira/browse/HBASE-19200
>             Project: HBase
>          Issue Type: Task
>          Components: Client, Zookeeper
>            Reporter: Duo Zhang
>            Assignee: Duo Zhang
>             Fix For: 2.0.0-beta-1
>
>         Attachments: HBASE-19200-v1.patch, HBASE-19200-v2.patch, HBASE-19200-v3.patch,
HBASE-19200-v4.patch, HBASE-19200-v5.patch, HBASE-19200.patch
>
>
> So that we can move most of the zookeeper related code out of hbase-client module.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message