[
https://issues.apache.org/jira/browse/CURATOR-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15159447#comment-15159447
]
Scott Blum commented on CURATOR-288:
------------------------------------
Isn't this done now, with TreeCacheSelector?
> Provide a mechanism to limit tree traversal in TreeCache + Return old values
> in NODE_REMOVED event
> --------------------------------------------------------------------------------------------------
>
> Key: CURATOR-288
> URL: https://issues.apache.org/jira/browse/CURATOR-288
> Project: Apache Curator
> Issue Type: New Feature
> Components: Recipes
> Affects Versions: 3.0.0, 2.9.1
> Reporter: Jordan Zimmerman
> Assignee: Jordan Zimmerman
> Priority: Minor
> Fix For: 2.10.1, 3.1.1
>
>
> 1. Currently, the only way to limit TreeCache's traversal is with maxDepth.
> It would be nice to also have a functional way of doing this. i.e. an policy
> object that is called to determine if a node should be traversed.
> 2. NODE_REMOVED should return the old values of the node
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
