hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daryn Sharp (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-8131) FsShell put doesn't correctly handle a non-existent dir
Date Mon, 26 Mar 2012 18:30:27 GMT

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

Daryn Sharp commented on HADOOP-8131:
-------------------------------------

Just to confirm: you mean a real conf key, not a cmdline flag, right?  In either case it will
be a "change now or change later" scenario.  I'm curious when would you anticipate a good
time to remove a new & deprecated conf?  Would it live all the way through 23?  As Eli
pointed out, an alpha may be the best time to remove the behavior.  Thoughts?
                
> FsShell put doesn't correctly handle a non-existent dir
> -------------------------------------------------------
>
>                 Key: HADOOP-8131
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8131
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 0.23.0
>            Reporter: Daryn Sharp
>            Assignee: Daryn Sharp
>            Priority: Critical
>             Fix For: 0.23.2
>
>         Attachments: HADOOP-8131.patch, HADOOP-8131.patch, HADOOP-8131.patch, HADOOP-8131.patch
>
>
> {noformat}
> $ hadoop fs -ls
> ls: `.': No such file or directory
> $ hadoop fs -put file
> $ hadoop fs -ls
> Found 1 items
> -rw-r--r--   1 kihwal supergroup       2076 2011-11-04 10:37 .._COPYING_
> {noformat}

--
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

        

Mime
View raw message