Mailing-List: contact dev-help@curator.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@curator.incubator.apache.org
Date: Wed, 25 Sep 2013 03:17:02 +0000 (UTC)
From: "Jordan Zimmerman (JIRA)" <jira@apache.org>
To: dev@curator.incubator.apache.org
Message-ID: <JIRA.12670323.1380044775710.14302.1380079022440@arcas>
In-Reply-To: <JIRA.12670323.1380044775710@arcas>
References: <JIRA.12670323.1380044775710@arcas>
Subject: [jira] [Commented] (CURATOR-57) Event order lost with
 PathChildrenCache
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jordan Zimmerman commented on CURATOR-57:
-----------------------------------------

I don't see how this can be supported. A watcher is set for the parent node by calling getChildren(). When the watcher triggers, getChildren() is called. getChildren() returns a list of name - no ordering is provided. Unless a method of solving this can be suggested, I'll close this issue.
                
> Event order lost with PathChildrenCache
> ---------------------------------------
>
>                 Key: CURATOR-57
>                 URL: https://issues.apache.org/jira/browse/CURATOR-57
>             Project: Apache Curator
>          Issue Type: Bug
>          Components: Recipes
>    Affects Versions: 2.0.1-incubating
>         Environment: Ubuntu 10.10
>            Reporter: Benjamin Jaton
>         Attachments: Test.java
>
>
> I am attaching a simple test to demonstrate the problem:
> Single threaded 'for' loop that creates children 0 to N, the events are not received in order.

--
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