[
https://issues.apache.org/jira/browse/CURATOR-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14081224#comment-14081224
]
ASF GitHub Bot commented on CURATOR-33:
---------------------------------------
Github user Randgalt commented on the pull request:
https://github.com/apache/curator/pull/17#issuecomment-50797741
There is a tiny potential for a race with outstandingOps for
refreshData()'s background result to succeed before refreshChildren() resulting
in a false INITIALIZED event. I was able to simulate this by forcing
refreshChildren() to block indefinitely.
> Recursive Node Cache
> --------------------
>
> Key: CURATOR-33
> URL: https://issues.apache.org/jira/browse/CURATOR-33
> Project: Apache Curator
> Issue Type: Improvement
> Components: Recipes
> Reporter: John Vines
> Assignee: Jordan Zimmerman
> Fix For: TBD
>
> 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
(v6.2#6252)
