You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Duo Zhang (JIRA)" <ji...@apache.org> on 2016/10/26 12:29:58 UTC

[jira] [Comment Edited] (HBASE-16835) Revisit the zookeeper usage at client side

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

Duo Zhang edited comment on HBASE-16835 at 10/26/16 12:29 PM:
--------------------------------------------------------------

[~stack] The patch you committed in HBASE-15789 missed the asf header. Or we should exclude it from the rat check? This file

hbase-protocol-shaded/src/main/patches/HBASE-15789_V2.patch

And for protoc, we need protoc 2.5.0 for hbase-protocol and protoc 3.1.0 for hbase-protocol-shaded? We need some tricks in the pom.xml I think...


was (Author: apache9):
[~stack] The patch you committed in hbase-15789 missed the asf header. Or we should exclude it from the rat check? This file

hbase-protocol-shaded/src/main/patches/HBASE-15789_V2.patch

And for protoc, we need protoc 2.5.0 for hbase-protocol and protoc 3.1.0 for hbase-protocol-shaded? We need some tricks in the pom.xml I think...

> Revisit the zookeeper usage at client side
> ------------------------------------------
>
>                 Key: HBASE-16835
>                 URL: https://issues.apache.org/jira/browse/HBASE-16835
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Client, Zookeeper
>    Affects Versions: 2.0.0
>            Reporter: Duo Zhang
>            Assignee: Duo Zhang
>             Fix For: 2.0.0
>
>         Attachments: HBASE-16835.patch
>
>
> Watcher or not.
> Curator or not.
> Keep connection or not.
> ...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)