Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hadoop-dev@lucene.apache.org
Message-ID: <18279071.1181865689549.JavaMail.jira@brutus>
Date: Thu, 14 Jun 2007 17:01:29 -0700 (PDT)
From: "Tsz Wo (Nicholas), SZE (JIRA)" <jira@apache.org>
To: hadoop-dev@lucene.apache.org
Subject: [jira] Updated: (HADOOP-1207) hdfs -rm should NOT fail if one of
 the files to remove is missing
In-Reply-To: <8570581.1175733812265.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Tsz Wo (Nicholas), SZE updated HADOOP-1207:
-------------------------------------------

    Attachment: HADOOP-1207_20070614.patch

added a class DelayedExceptionThrowing for handling IOExceptions for the commands rm and cat

> hdfs -rm should NOT fail if one of the files to remove is missing
> -----------------------------------------------------------------
>
>                 Key: HADOOP-1207
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1207
>             Project: Hadoop
>          Issue Type: Bug
>          Components: dfs
>            Reporter: arkady borkovsky
>            Priority: Minor
>         Attachments: HADOOP-1207_20070614.patch
>
>
> It looks like hdfs -rm with wild card argument first builds the list of
> files to delete, and then deletes them one by one.
> (This is OK so far).
> If one of the files on the list gets deleted by someone else before the
> command reaches it, the command fails.
> This seems a wrong behavior to me. I'd expect the command report the problem
> and continue deleting the rest of the files.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.