hadoop-hdfs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tsz Wo (Nicholas), SZE (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (HDFS-643) Strange behavior with bin/hadoop dfs -mv
Date Tue, 22 Sep 2009 23:36:16 GMT

     [ https://issues.apache.org/jira/browse/HDFS-643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Tsz Wo (Nicholas), SZE resolved HDFS-643.
-----------------------------------------

    Resolution: Invalid

That's great, Bryan!  Let's close this.  Feel free to reopen if you see the problem 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.


Mime
View raw message