You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "Ravi Phulari (JIRA)" <ji...@apache.org> on 2009/07/11 04:31:14 UTC
[jira] Resolved: (HDFS-182) Incorrect exit code from "hadoop dfs
-mv"
[ https://issues.apache.org/jira/browse/HDFS-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ravi Phulari resolved HDFS-182.
-------------------------------
Resolution: Duplicate
Release Note: Closing as duplicate of HADOOP-6143
> Incorrect exit code from "hadoop dfs -mv"
> -----------------------------------------
>
> Key: HDFS-182
> URL: https://issues.apache.org/jira/browse/HDFS-182
> Project: Hadoop HDFS
> Issue Type: Bug
> 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.