curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CURATOR-145) TreeCache should implement maxDepth
Date Sat, 18 Oct 2014 19:48:33 GMT

    [ https://issues.apache.org/jira/browse/CURATOR-145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14176095#comment-14176095
] 

ASF GitHub Bot commented on CURATOR-145:
----------------------------------------

Github user jhump commented on a diff in the pull request:

    https://github.com/apache/curator/pull/42#discussion_r19055906
  
    --- Diff: curator-recipes/src/main/java/org/apache/curator/framework/recipes/cache/TreeCache.java
---
    @@ -179,24 +191,34 @@ public static Builder newBuilder(CuratorFramework client, String
path)
             final AtomicReference<Stat> stat = new AtomicReference<Stat>();
             final AtomicReference<byte[]> data = new AtomicReference<byte[]>();
             final AtomicReference<ConcurrentMap<String, TreeNode>> children =
new AtomicReference<ConcurrentMap<String, TreeNode>>();
    +        final int depth;
     
             TreeNode(String path, TreeNode parent)
             {
                 this.path = path;
                 this.parent = parent;
    +            this.depth = parent == null ? 0 : parent.depth + 1;
             }
     
             private void refresh() throws Exception
             {
    -            outstandingOps.addAndGet(2);
    -            doRefreshData();
    -            doRefreshChildren();
    +            if (depth < maxDepth)
    --- End diff --
    
    I know this wasn't the intent of this PR. But to *really* solve an even larger class of
problems, we can make this more flexible. What I'm thinking, instead of hard-coded criteria
by depth, is the ability to provide a `Predicate` for filtering parts of the sub-tree that
don't need to be cached.
    
    Ideally, the predicate would be applied in a different spot than here. That way we can
filter individual nodes out of the cache. (This approach only lets me say "yes, include all
of this node's children" or "no, none of its children".)


> TreeCache should implement maxDepth
> -----------------------------------
>
>                 Key: CURATOR-145
>                 URL: https://issues.apache.org/jira/browse/CURATOR-145
>             Project: Apache Curator
>          Issue Type: Improvement
>          Components: Recipes
>            Reporter: Scott Blum
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>




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

Mime
View raw message