Return-Path: Delivered-To: apmail-hadoop-mapreduce-issues-archive@minotaur.apache.org Received: (qmail 4507 invoked from network); 5 Mar 2010 03:20:01 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 5 Mar 2010 03:20:01 -0000 Received: (qmail 5682 invoked by uid 500); 5 Mar 2010 03:19:48 -0000 Delivered-To: apmail-hadoop-mapreduce-issues-archive@hadoop.apache.org Received: (qmail 5603 invoked by uid 500); 5 Mar 2010 03:19:48 -0000 Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: mapreduce-issues@hadoop.apache.org Delivered-To: mailing list mapreduce-issues@hadoop.apache.org Received: (qmail 5589 invoked by uid 99); 5 Mar 2010 03:19:48 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Mar 2010 03:19:48 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Mar 2010 03:19:47 +0000 Received: from brutus.apache.org (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 464BA234C4CC for ; Fri, 5 Mar 2010 03:19:27 +0000 (UTC) Message-ID: <2010590584.88371267759167287.JavaMail.jira@brutus.apache.org> Date: Fri, 5 Mar 2010 03:19:27 +0000 (UTC) From: "Hadoop QA (JIRA)" To: mapreduce-issues@hadoop.apache.org Subject: [jira] Commented: (MAPREDUCE-1518) On contrib/raid, the RaidNode currently runs the deletion check for parity files on directories too. It would be better if it didn't. In-Reply-To: <1990090526.423691266797128175.JavaMail.jira@brutus.apache.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/MAPREDUCE-1518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12841677#action_12841677 ] Hadoop QA commented on MAPREDUCE-1518: -------------------------------------- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12437948/MAPREDUCE-1518.0.patch against trunk revision 919173. +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 3 new or modified tests. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 findbugs. The patch does not introduce any new Findbugs warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed core unit tests. +1 contrib tests. The patch passed contrib unit tests. Test results: http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h4.grid.sp2.yahoo.net/20/testReport/ Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h4.grid.sp2.yahoo.net/20/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Checkstyle results: http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h4.grid.sp2.yahoo.net/20/artifact/trunk/build/test/checkstyle-errors.html Console output: http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h4.grid.sp2.yahoo.net/20/console This message is automatically generated. > On contrib/raid, the RaidNode currently runs the deletion check for parity files on directories too. It would be better if it didn't. > ------------------------------------------------------------------------------------------------------------------------------------- > > Key: MAPREDUCE-1518 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1518 > Project: Hadoop Map/Reduce > Issue Type: Improvement > Components: contrib/raid > Environment: On contrib/raid, the RaidNode currently runs the deletion check for parity files on directories too. It runs okay because the directory is not empty and trying to delete it non-recursively fails, but such failure messages only polute the log file. > My proposal is the following: > If recursePurge is checking a directory, it should call itself recursively. > If it's checking a file, it should do the deletion check. > Reporter: Rodrigo Schmidt > Assignee: Rodrigo Schmidt > Attachments: MAPREDUCE-1518.0.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.