accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (ACCUMULO-2727) version argument of ZooUtil.recursiveDelete is ignored
Date Fri, 31 Oct 2014 17:47:34 GMT

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

Josh Elser resolved ACCUMULO-2727.
----------------------------------
    Resolution: Fixed

Gah, put the duplicate issue's ID instead of this one

{noformat}

    Commit 69d665cb4c387afd64f5f0b56e6f52eec2b188a4 in accumulo's branch refs/heads/1.5 from
[~elserj]
    [ https://git-wip-us.apache.org/repos/asf?p=accumulo.git;h=69d665c ]

    ACCUMULO-3279 Remove version argument from recursiveDelete

    `recursiveDelete` is much like a big hammer: get rid of
    all of the nodes beneath this parent. As such, it doesn't
    make sense to pass in a version, nor does it make sense to
    provide a specific version to delete. We can pass in a version
    of '-1' which should eliminate the need for any special handling
    around BadVersionExceptions.
{noformat}

> version argument of ZooUtil.recursiveDelete is ignored
> ------------------------------------------------------
>
>                 Key: ACCUMULO-2727
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2727
>             Project: Accumulo
>          Issue Type: Bug
>          Components: fate
>    Affects Versions: 1.5.1, 1.6.0
>            Reporter: Mike Drob
>            Assignee: Josh Elser
>             Fix For: 1.5.3, 1.6.2, 1.7.0
>
>
> The {{version}} argument of recursiveDelete is ignored. We should either use it, or remove
it, instead of giving the illusion that we respect it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message