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-145) TreeCache should implement maxDepth
Date Mon, 20 Oct 2014 19:59:33 GMT


ASF GitHub Bot commented on CURATOR-145:

Github user dragonsinth commented on the pull request:
    I'm inclined to want to go with what we have and reserve Predicate as a future feature.
 I don't think anything here so far would make it harder / preclude adding it later.
    I have 2 main concerns over adding general Predicates that make me want to consider this
much more carefully.
    1) Running the predicate means passing control to user code on cache's event callback
/ mutation threads.
    2) An inconsistent predicate would be super weird and possibly corrupt internal state.
 What would happen if a predicate's behavior changed on the fly, or gave inconsistent answers
for the same node?
    The idea definitely has merit I'm just not really ready to take it on right now.

> TreeCache should implement maxDepth
> -----------------------------------
>                 Key: CURATOR-145
>                 URL:
>             Project: Apache Curator
>          Issue Type: Improvement
>          Components: Recipes
>            Reporter: Scott Blum
>   Original Estimate: 48h
>  Remaining Estimate: 48h

This message was sent by Atlassian JIRA

View raw message