curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CURATOR-33) Recursive Node Cache
Date Thu, 24 Jul 2014 10:28:38 GMT


ASF GitHub Bot commented on CURATOR-33:

Github user dragonsinth commented on the pull request:
    Thanks guys, I was able to repro under 1.7 (I don't have 1.6 on OSX to test against).
 Interestingly, it looks like the order in which `event.getChildren()` names appear during
`CuratorEventType.CHILDREN` differs between JDK versions.  So now I'm sorting the names of
added children to increase test determinism.

> Recursive Node Cache
> --------------------
>                 Key: CURATOR-33
>                 URL:
>             Project: Apache Curator
>          Issue Type: Improvement
>          Components: Recipes
>            Reporter: John Vines
>             Fix For: awaiting-response
>         Attachments: CURATOR-33.2.patch, CURATOR-33.patch
> Currently the PathChildrenCache will trigger listen events for all children at the given
node. However, it would be useful to have a cache that would trigger listen events for the
entire hierarchy below the given node.

This message was sent by Atlassian JIRA

View raw message