[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Patrick Datko updated ZOOKEEPER-839:
------------------------------------

                 Tags: atomic operations
    Affects Version/s: 3.3.1
          Description: 
DeleteRecursive has been committed to trunk already as a method to the 
zookeeper class. So in the API it has the same level as the atomic operations 
create, delete, getData, setData, etc. The user must get the false impression, 
that deleteRecursive is also an atomic operation.
It would be better to have deleteRecursive in some helper class but not that 
deep in zookeeper's core code. Maybe I'd like to have another policy on how to 
react if deleteRecursive fails in the middle of its work?

> deleteRecursive does not belong to the other methods
> ----------------------------------------------------
>
>                 Key: ZOOKEEPER-839
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-839
>             Project: Zookeeper
>          Issue Type: Sub-task
>    Affects Versions: 3.3.1
>            Reporter: Patrick Datko
>
> DeleteRecursive has been committed to trunk already as a method to the 
> zookeeper class. So in the API it has the same level as the atomic operations 
> create, delete, getData, setData, etc. The user must get the false 
> impression, 
> that deleteRecursive is also an atomic operation.
> It would be better to have deleteRecursive in some helper class but not that 
> deep in zookeeper's core code. Maybe I'd like to have another policy on how 
> to 
> react if deleteRecursive fails in the middle of its work?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to