Details

    • Type: Sub-task Sub-task
    • Status: Closed
    • Priority: Blocker Blocker
    • Resolution: Fixed
    • Affects Version/s: 3.3.1
    • Fix Version/s: 3.4.0
    • Component/s: java client
    • Labels:
      None
    • Hadoop Flags:
      Reviewed
    • Tags:
      atomic operations

      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?

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            Mahadev konar
            Reporter:
            Patrick Datko
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development