[
https://issues.apache.org/jira/browse/HBASE-5790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13256241#comment-13256241
]
Jesse Yates commented on HBASE-5790:
------------------------------------
@stack: in short, yes. I don't see an easy way to set zk version, though I
guess we could add a config option if people want to run an old version (but
this gets into some really strange corner cases where we expect transaction for
newer features, but have to support non-transactional views; I'd rather just go
wholesale into the new stuff).
I didn't know that we have a requirement on supporting past versions of ZK. If
we want to roll this into just 0.96 we can assume singularity and say people
need to run at least zk-3.4.
> ZKUtil deleteRecursively should be a recoverable operation
> ----------------------------------------------------------
>
> Key: HBASE-5790
> URL: https://issues.apache.org/jira/browse/HBASE-5790
> Project: HBase
> Issue Type: Improvement
> Reporter: Jesse Yates
> Assignee: Jesse Yates
> Labels: zookeeper
> Fix For: 0.96.0, 0.94.1
>
> Attachments: java_HBASE-5790-v1.patch, java_HBASE-5790.patch
>
>
> As of 3.4.3 Zookeeper now has full, multi-operation transaction. This means
> we can wholesale delete chunks of the zk tree and ensure that we don't have
> any pesky recursive delete issues where we delete the children of a node, but
> then a child joins before deletion of the parent. Even without transactions,
> this should be the behavior, but it is possible to make it much cleaner now
> that we have this new feature in zk.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
