You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Daryn Sharp (Created) (JIRA)" <ji...@apache.org> on 2012/03/16 00:22:38 UTC
[jira] [Created] (HADOOP-8176) Disambiguate the destination of
FsShell copies
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
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