[
https://issues.apache.org/jira/browse/HADOOP-10965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15131728#comment-15131728
]
Andrew Wang commented on HADOOP-10965:
--------------------------------------
It comes down to relative and absolute paths. In your first example, you
provided a relative path, so it prints a relative path in the error message. In
the second, "~/x/y" is an absolute path that expands to "/home/yzhang/x/y" so
that absolute path is printed.
In this reported case, it's your first example rather than the second. The cwd
of the hadoop shell happens to be the user's home dir, but the user is
specifying a relative path as the argument. Basically this:
{noformat}
# cd ~
# ls does/not/exist
{noformat}
> Incorrect error message by fs -copyFromLocal
> --------------------------------------------
>
> Key: HADOOP-10965
> URL: https://issues.apache.org/jira/browse/HADOOP-10965
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 2.4.1
> Reporter: André Kelpe
> Assignee: John Zhuge
> Priority: Minor
> Labels: supportability
> Attachments: HADOOP-10965.001.patch
>
>
> Whenever I try to copy data from local to a cluster, but forget to create the
> parent directory first, I get a very confusing error message:
> {code}
> $ whoami
> fs111
> $ hadoop fs -ls /user
> Found 2 items
> drwxr-xr-x - fs111 supergroup 0 2014-08-11 20:17 /user/hive
> drwxr-xr-x - vagrant supergroup 0 2014-08-11 19:15 /user/vagrant
> $ hadoop fs -copyFromLocal data data
> copyFromLocal: `data': No such file or directory
> {code}
> From the error message, you would say that the local "data" directory is not
> existing, but that is not the case. What is missing is the "/user/fs111"
> directory on HDFS. After I created it, the copyFromLocal command works fine.
> I believe the error message is confusing and should at least be fixed. What
> would be even better, if hadoop could restore the old behaviour in 1.x, where
> copyFromLocal would just create the directories, if they are missing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
