[
https://issues.apache.org/jira/browse/ZOOKEEPER-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13777135#comment-13777135
]
Marshall McMullen commented on ZOOKEEPER-1760:
----------------------------------------------
I agree with Flavio and Benjamin as well. The Multi requires a check to be able
to detect race conditions between related paths in an atomic way. You can't do
that at all without a multi so the use case doesn't make sense to me. And as
others already said, you can get what you want with Stat. In our own local
wrapper we have sitting on top of ZooKeeper client, we've added all sorts of
convenience methods like this, e.g. a GetVersion, GetNumChildren, etc., which
are all implemented via a call to stat.
> Provide an interface for check version of a node
> ------------------------------------------------
>
> Key: ZOOKEEPER-1760
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1760
> Project: ZooKeeper
> Issue Type: New Feature
> Components: java client
> Reporter: Rakesh R
> Assignee: Rakesh R
> Fix For: 3.5.0
>
>
> The idea of this JIRA is to discuss the check version interface which is used
> to see the existence of a node for the specified version. Presently only
> multi transaction api has this interface, this umbrella JIRA is to make
> 'check version' api part of ZooKeeper# main apis and cli command.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
