curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ioannis Canellos (JIRA)" <>
Subject [jira] [Commented] (CURATOR-30) Recursive delete
Date Mon, 08 Jul 2013 07:49:48 GMT


Ioannis Canellos commented on CURATOR-30:

I don't think that's really needed to update ZkPaths method to not use the raw ZooKeeper handle.
I think that any retriable exception that will happen there will be propagated and get retried
(at least this is what I understand).

The same applied to guaranteed. If the guranteed flag is used, the whole operation will be
retried in the background, even if the error occurs while deleting children nodes.

So unless, there is value (which I fail to see) in having the guaranteed behaviour only for
the parent node, or only for the children nodes, I don't think that there is anything more
to be done in this patch.

> Recursive delete
> ----------------
>                 Key: CURATOR-30
>                 URL:
>             Project: Apache Curator
>          Issue Type: Improvement
>          Components: Client, Framework
>            Reporter: John Vines
>         Attachments: CURATOR-30.patch
> Currently there is the ability to recursive create parent znodes when you create a node.
However, there is no ability to recursively delete a hierarchy. Zookeeper already provides
this in their package, but it seems like a very curator-ish thing to perform as
well. There is the potential difficulty involved with the guarantee() functionality, but it
should be workable.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message