[jira] [Commented] (CURATOR-319) NodeCache recreates deleted parents of the node being cached

["Jordan Zimmerman (JIRA)" <ji...@apache.org>]

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

Jordan Zimmerman commented on CURATOR-319:
------------------------------------------

This is a larger issue in Curator. Nearly all of the recipes attempt to create parents as needed. I'm not sure what the right thing to do is.

> NodeCache recreates deleted parents of the node being cached
> ------------------------------------------------------------
>
>                 Key: CURATOR-319
>                 URL: https://issues.apache.org/jira/browse/CURATOR-319
>             Project: Apache Curator
>          Issue Type: Bug
>          Components: Recipes
>    Affects Versions: 2.10.0
>            Reporter: Tommy Becker
>
> Starting with Curator 2.10.0, the NodeCache will spontaneously re-create parents of the node being cached if one of them is deleted.  As an example, if there is a NodeCache watching node /a/b/c and node b is deleted, the cache will immediately recreate node b (but not c) when the change is processed. This seems to stem from this commit: https://github.com/apache/curator/commit/f02fb225d531506444b54cdf5effb0529a35cdb0
> This was not the behavior prior to 2.10.0, and seems pretty unexpected.



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