curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jordan Zimmerman (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CURATOR-288) Provide a mechanism to limit tree traversal in TreeCache + Return old values in NODE_REMOVED event
Date Fri, 15 Jan 2016 17:20:39 GMT

     [ https://issues.apache.org/jira/browse/CURATOR-288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jordan Zimmerman updated CURATOR-288:
-------------------------------------
    Summary: Provide a mechanism to limit tree traversal in TreeCache + Return old values
in NODE_REMOVED event  (was: Provide a mechanism to limit tree traversal in TreeCache)

> 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: 3.0.1, 2.9.2
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message