hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daryn Sharp (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-9289) FsShell rm -f fails for non-matching globs
Date Wed, 06 Feb 2013 20:11:14 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-9289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13572769#comment-13572769

Daryn Sharp commented on HADOOP-9289:

The FsShell rm usage states:
-f     If the file does not exist, do not display a diagnostic
       message or modify the exit status to reflect an error.

How do you think the text should be updated?
> FsShell rm -f fails for non-matching globs
> ------------------------------------------
>                 Key: HADOOP-9289
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9289
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: fs
>    Affects Versions: 0.23.0, 2.0.0-alpha, 3.0.0
>            Reporter: Daryn Sharp
>            Assignee: Daryn Sharp
>            Priority: Blocker
>             Fix For: 2.0.3-alpha, 0.23.7
>         Attachments: HADOOP-9289.branch-23.patch, HADOOP-9289.patch
> Rm -f isn't supposed to error for paths that don't exist.  It works as expected for exact
paths, but fails for non-matching globs.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message