[
https://issues.apache.org/jira/browse/HADOOP-8176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Joseph Evans updated HADOOP-8176:
----------------------------------------
Resolution: Fixed
Fix Version/s: 0.23.2
Target Version/s: 0.24.0, 0.23.2 (was: 0.23.2, 0.24.0)
Status: Resolved (was: Patch Available)
Thanks Daryn. I looked over the patch and it looks good +1. I just put this
into trunk, branch-0.23 and branch-0.23.2
> Disambiguate the destination of FsShell copies
> ----------------------------------------------
>
> Key: HADOOP-8176
> URL: https://issues.apache.org/jira/browse/HADOOP-8176
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs
> Affects Versions: 0.24.0, 0.23.2
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Fix For: 0.23.2
>
> Attachments: HADOOP-8176.patch
>
>
> The copy commands currently do not provide a way to disambiguate the expected
> destination of a copy. Ex.
> {{fs -put myfile path/mydir}}
> If "mydir" is an existing directory, then the copy produces
> {{path/mydir/file}}. If "mydir" does not exist at all, the copy produces
> {{path/mydir}}. The file has unexpectedly been renamed to what was expected
> to be a directory! It's standard unix shell behavior, but it lacks a special
> trait.
> Unix allows a user to disambiguate their intent by allowing {{path/mydir/}}
> or {{path/mydir/.}} to mean "mydir" is *always* be treated as a directory.
> If the copy succeeds, it will always be called {{path/mydir/myfile}}.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
