hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ramesh Sekaran (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-5461) Incorrect exit code from "hadoop dfs -mv"
Date Fri, 13 Mar 2009 03:40:50 GMT

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

Ramesh Sekaran commented on HADOOP-5461:
----------------------------------------

Hi,
   Thanks for the clarification. You are right, the source path (with *) should have been
escaped.

    Then, I would like to request that the exit code for such command be non-zero  - to keep
the behavior consistent with respect to invalid source directory.   

thanks,
Ramesh

> Incorrect exit code from "hadoop dfs -mv"
> -----------------------------------------
>
>                 Key: HADOOP-5461
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5461
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: dfs
>    Affects Versions: 0.20.0
>            Reporter: Ramesh Sekaran
>            Priority: Minor
>
> In hadoop 0.17 & 0.18 the behavior of "hadoop dfs -mv <invalid src dir>/* <target
dir>" is as shown below.
> $  hadoop dfs -mv /user/dfsload/does-not-exist/* /user/dfsload/.Trash
> hadoop: No match.
> $ echo $?
> 1
> The same command when issued to hadoop 0.20 cluster, has a "0" exit code which is incorrect.
> $  hadoop dfs -mv /user/dfsload/does-not-exist/* /user/dfsload/.Trash
> $ echo $?
> 0
> The exit code must be non-zero in this case.

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


Mime
View raw message