hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-8176) Disambiguate the destination of FsShell copies
Date Fri, 16 Mar 2012 01:06:37 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-8176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13230796#comment-13230796

Hadoop QA commented on HADOOP-8176:

+1 overall.  Here are the results of testing the latest attachment 
  against trunk revision .

    +1 @author.  The patch does not contain any @author tags.

    +1 tests included.  The patch appears to include 3 new or modified tests.

    +1 javadoc.  The javadoc tool did not generate any warning messages.

    +1 javac.  The applied patch does not increase the total number of javac compiler warnings.

    +1 eclipse:eclipse.  The patch built with eclipse:eclipse.

    +1 findbugs.  The patch does not introduce any new Findbugs (version 1.3.9) warnings.

    +1 release audit.  The applied patch does not increase the total number of release audit

    +1 core tests.  The patch passed unit tests in .

    +1 contrib tests.  The patch passed contrib unit tests.

Test results: https://builds.apache.org/job/PreCommit-HADOOP-Build/717//testReport/
Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/717//console

This message is automatically generated.
> 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
>         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


View raw message