[
https://issues.apache.org/jira/browse/HBASE-15751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16179464#comment-16179464
]
Mike Drob commented on HBASE-15751:
-----------------------------------
Ah, I think we are miscommunicating.
ZK3.5.3 is relelased, and labelled a beta.
They don't do 2.0-alphaN, -betaN like we're planning, they have separate point
releases that are given alpha/beta tags, similar to our stable and latest
pointers, I'd say. Their full release history is:
3.5.3-beta
3.5.2-alpha
3.5.1-alpha
3.5.0-alpha
I'm unsure if 3.5.4 will be another beta or not.
> Fixed HBase compilation failure with Zookeeper 3.5 and bumped HBase to use
> zookeeper 3.5
> ----------------------------------------------------------------------------------------
>
> Key: HBASE-15751
> URL: https://issues.apache.org/jira/browse/HBASE-15751
> Project: HBase
> Issue Type: Improvement
> Components: dependencies, Zookeeper
> Reporter: Yufeng Jiang
> Assignee: Yufeng Jiang
> Priority: Critical
> Fix For: 2.0.0
>
> Attachments: HBASE-15751.patch
>
>
> From zookeeper 3.5 and onwards, runFromConfig(QuorumPeerConfig config) method
> throws AdminServerException.
> HBase uses runFromConfig in HQuorumPeer.java and hence needs to throw this
> exception as well.
> I've created a patch to make HBase compatible with zookeeper-3.5.1-alpha.
> However, since zookeeper 3.5+ does not have a stable version yet, I don't
> think we should commit this patch. Instead, I suggest using this JIRA to
> track this issue. Once zookeeper releases stable version of 3.5+, I could
> create another patch to bump the zookeeper version in HBase trunk.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
