Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Mon, 28 Mar 2016 21:47:25 +0000 (UTC)
From: "Hudson (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.12733733.1407927128000.69605.1459201645652@Atlassian.JIRA>
In-Reply-To: <JIRA.12733733.1407927128000@Atlassian.JIRA>
References: <JIRA.12733733.1407927128000@Atlassian.JIRA>
 <JIRA.12733733.1407927128128@arcas>
Subject: [jira] [Commented] (HADOOP-10965) Print fully qualified path in
 CommandWithDestination error messages
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/HADOOP-10965?page=3Dcom.atlassi=
an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D15=
214950#comment-15214950 ]=20

Hudson commented on HADOOP-10965:
---------------------------------

FAILURE: Integrated in Hadoop-trunk-Commit #9514 (See [https://builds.apach=
e.org/job/Hadoop-trunk-Commit/9514/])
HADOOP-10965. Print fully qualified path in CommandWithDestination error (w=
ang: rev 8bfaa80037365c0790083313a905d1e7d88b0682)
* hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/fs/Pa=
thIOException.java
* hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/fs/Te=
stFsShellTouch.java
* hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/fs/sh=
ell/CommandWithDestination.java
* hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/fs/sh=
ell/Touch.java
* hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/fs/Te=
stFsShellCopy.java


> Print fully qualified path in CommandWithDestination error messages
> -------------------------------------------------------------------
>
>                 Key: HADOOP-10965
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10965
>             Project: Hadoop Common
>          Issue Type: Improvement
>    Affects Versions: 2.4.1
>            Reporter: Andr=C3=A9 Kelpe
>            Assignee: John Zhuge
>            Priority: Minor
>              Labels: supportability
>             Fix For: 2.8.0
>
>         Attachments: HADOOP-10965.001.patch, HADOOP-10965.002.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/vagra=
nt
> $ 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 fi=
ne.
> I believe the error message is confusing and should at least be fixed. Wh=
at 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)