Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 13 Apr 2012 05:55:17 +0000 (UTC)
From: "Hudson (Commented) (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <1900645519.20724.1334296517559.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <896663734.18635.1334256798264.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HBASE-5775) ZKUtil doesn't handle
 deleteRecurisively cleanly
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HBASE-5775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13253139#comment-13253139 ] 

Hudson commented on HBASE-5775:
-------------------------------

Integrated in HBase-TRUNK-security #169 (See [https://builds.apache.org/job/HBase-TRUNK-security/169/])
    HBASE-5775 ZKUtil doesn't handle deleteRecurisively cleanly (Jesse Yates) (Revision 1325540)

     Result = FAILURE
larsh : 
Files : 
* /hbase/trunk/src/main/java/org/apache/hadoop/hbase/zookeeper/ZKUtil.java
* /hbase/trunk/src/test/java/org/apache/hadoop/hbase/TestZooKeeper.java

                
> ZKUtil doesn't handle deleteRecurisively cleanly
> ------------------------------------------------
>
>                 Key: HBASE-5775
>                 URL: https://issues.apache.org/jira/browse/HBASE-5775
>             Project: HBase
>          Issue Type: Improvement
>    Affects Versions: 0.94.0
>            Reporter: Jesse Yates
>            Assignee: Jesse Yates
>             Fix For: 0.94.0, 0.96.0
>
>         Attachments: java_HBASE-5775.patch
>
>
> ZKUtil.deleteNodeRecursively()'s contract says that it handles deletion of the node and all its children. However, nothing is mentioned as to what happens if the node you are attempting to delete doesn't actually exist. Turns out, it throws a null pointer exception. I
> 'm proposing that we change the code s.t. it handles the case where the parent is already gone and exits cleanly, rather than failing horribly.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira