[
https://issues.apache.org/jira/browse/HDFS-643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12758484#action_12758484
]
Tsz Wo (Nicholas), SZE commented on HDFS-643:
---------------------------------------------
Tried the following:
{noformat}
-bash-3.1$ hadoop fs -lsr foo
drwx------ - tsz users 0 2009-09-22 23:18 /user/tsz/foo/1
drwx------ - tsz users 0 2009-09-22 23:18 /user/tsz/foo/2
drwx------ - tsz users 0 2009-09-22 23:18 /user/tsz/foo/3
-bash-3.1$ hadoop dfs -mv foo/1 foo/2 foo/3
-bash-3.1$ hadoop fs -lsr foo
drwx------ - tsz users 0 2009-09-22 23:19 /user/tsz/foo/3
drwx------ - tsz users 0 2009-09-22 23:18 /user/tsz/foo/3/1
drwx------ - tsz users 0 2009-09-22 23:18 /user/tsz/foo/3/2
{noformat}
Could you check again?
> Strange behavior with bin/hadoop dfs -mv
> ----------------------------------------
>
> Key: HDFS-643
> URL: https://issues.apache.org/jira/browse/HDFS-643
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 0.20.1
> Reporter: Bryan Duxbury
>
> I had a very strange experience today with the bin/hadoop dfs -mv command. I
> accidentally passed 3 parameters, like so:
> {code}
> bin/hadoop dfs -mv /1 /2 /3
> {code}
> My intent was to mv /1 to /3, but mis-pasted some stuff. However, to my
> surprise, the result I got was that /1 had been moved to /2, and /2 had then
> been moved to /3! This seems like totally confusing semantics - I would have
> expected a 3-parameter move to either ignore the 3rd parameter or error out
> altogether. Needless to say, a solid 10 minutes of confused scrambling
> commenced.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
