the pzxid from the users point of view is purely informational.
internally we use it to figure out if we need to trigger watches on
both the pzxid and the cversion are updated when adding or removing children.
On Tue, Oct 18, 2011 at 10:32 AM, Ted Dunning <[EMAIL PROTECTED]> wrote:
> Good question.
> One thought is that you can use the multi for this except that I don't know if the parent version changes when adding or removing a child. On the other hand you could also update the content of the parent in the same multi to free the version update.
> Sent from my iPhone
> On Oct 18, 2011, at 9:48, Dan Mihai Dumitriu <[EMAIL PROTECTED]> wrote:
>> That brings up a question I was asking myself. Why are there not
>> crate and delete methods which optionally require the parent's
>> children version? (i.e. optimistic concurrency control for the
>> creation and deletion of nodes)
>> On Sun, Oct 16, 2011 at 8:59 AM, Mahadev Konar <[EMAIL PROTECTED]> wrote:
>>> Hi Tassos,
>>> There is some documention in src/zookeeper.jute:
>>> long pzxid; // last modified children
>>> But, we should probably add some documentation in the programmer's
>>> guide. Can you please open a jira/upload a patch :)?
>>> On Sat, Oct 15, 2011 at 12:49 AM, Tassos Souris <[EMAIL PROTECTED]> wrote:
>>>> Hi! what's the pzxid field in the stat structure for? couldn't find any information in the programmer's guide...