Mailing-List: contact dev-help@zookeeper.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@zookeeper.apache.org
Date: Wed, 25 Sep 2013 06:00:07 +0000 (UTC)
From: "Rakesh R (JIRA)" <jira@apache.org>
To: dev@zookeeper.apache.org
Message-ID: <JIRA.12669937.1379890924471.14868.1380088807006@arcas>
In-Reply-To: <JIRA.12669937.1379890924471@arcas>
References: <JIRA.12669937.1379890924471@arcas>
Subject: [jira] [Commented] (ZOOKEEPER-1760) Provide an interface for check
 version of a node
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Rakesh R commented on ZOOKEEPER-1760:
-------------------------------------

Thanks [~fpj], [~breed] and [~marshall] for your time and comments. As you pointed out, I would be able to satisfy my usecase with the Stat object and will write myown utilities.
I agree with you all, its not good to tune the ZooKeeper apis to satisfy my use case:)

As a user a non-commiter, I'm reluctant in changing the issue status to closure. Please help me and mark this issue as per ZooKeeper jira processing.
                
> 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