[
https://issues.apache.org/jira/browse/CURATOR-430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16126941#comment-16126941
]
ASF GitHub Bot commented on CURATOR-430:
----------------------------------------
Github user Randgalt commented on the issue:
https://github.com/apache/curator/pull/235
Please include a test (something like the code you posted in the issue) for
this. A good place to put the test is TestFrameworkEdges.java.
> deletingChildrenIfNeeded maybe cannot delete children completely when
> multi-client delete concurrently
> ------------------------------------------------------------------------------------------------------
>
> Key: CURATOR-430
> URL: https://issues.apache.org/jira/browse/CURATOR-430
> Project: Apache Curator
> Issue Type: Bug
> Components: Client
> Reporter: hebelala
>
> use curatorFramework.delete().deletingChildrenIfNeeded().forPath(path), this
> sync api doesn't ignore the NoNodeException, causes the rest of children
> nodes will not be deleted perhaps.
> zookeeper.getChildren(path, null) maybe throw NoNodeException, if the path
> doesn't exist.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
