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-33) Recursive Node Cache
Date Fri, 18 Jul 2014 07:09:04 GMT

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

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

GitHub user dragonsinth opened a pull request:

    https://github.com/apache/curator/pull/17

    CURATOR-33 recursive TreeCache recipe

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/dragonsinth/curator CURATOR-33

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/curator/pull/17.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #17
    
----
commit 547a7e23eb48fece49420bbcfdc84e763bf74461
Author: Scott Blum <scottb@squareup.com>
Date:   2014-07-15T00:38:07Z

    CURATOR-33 recursive TreeCache recipe

----


> 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
>             Fix For: awaiting-response
>
>         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)

Mime
View raw message