[
https://issues.apache.org/jira/browse/HADOOP-8131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13238677#comment-13238677
]
Todd Lipcon commented on HADOOP-8131:
-------------------------------------
bq. Just to confirm: you mean a real conf key, not a cmdline flag, right?
Yep - something that could be set system-wide in core-site.xml. When users
upgrade, they expect they may have to tweak some confs for the new version, but
it's harder to ask them to change all of their shell scripts.
bq. In either case it will be a "change now or change later" scenario
Right. The idea is that they would have some warning (a full major version)
before their code stops working. Our general policy is to only make the
breaking change after having the deprecated support for a full major version --
in which case it would go away in 0.24.0.
bq. Would this bring back the issue of left out _temporary dirs?
(MAPREDUCE-1272)
I would think the MR task would be using the new non-deprecated API which
doesn't recursively create parents.
> 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
