zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mahadev konar (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ZOOKEEPER-839) deleteRecursive does not belong to the other methods
Date Tue, 02 Aug 2011 06:12:28 GMT

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

Mahadev konar updated ZOOKEEPER-839:
------------------------------------

    Attachment: ZOOKEEPER-839.patch

patch attached moves the methods to ZKUtil.java. 

> 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
>          Components: java client
>    Affects Versions: 3.3.1
>            Reporter: Patrick Datko
>            Assignee: Mahadev konar
>            Priority: Blocker
>             Fix For: 3.4.0
>
>         Attachments: ZOOKEEPER-839.patch
>
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message