[
https://issues.apache.org/jira/browse/HADOOP-5461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12681158#action_12681158
]
Ramesh Sekaran commented on HADOOP-5461:
----------------------------------------
Can you try with a "*" added to the <src>? The "mv" command is issued for files
under a (non-existent) directory.
i.e. What is the behavior of this command?
./bin/hadoop dfs -mv /user/a/* b
The hadoop version that i encountered this behavior is
$ hadoop version
Hadoop 0.20.0-030909A
Subversion -r
Compiled by hadoopqa on Mon Mar 9 21:25:10 UTC 2009
> 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.
