[
https://issues.apache.org/jira/browse/HADOOP-5086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Douglas updated HADOOP-5086:
----------------------------------
Resolution: Fixed
Fix Version/s: (was: 0.21.0)
0.19.1
Hadoop Flags: [Reviewed] (was: [Incompatible change])
Status: Resolved (was: Patch Available)
bq. We could, in theory, merge a fix to the 0.19 [0.18?] and 0.19 branches too,
if we wanted.
Soright. I'll hold off on 0.18, since the vote for that has already been called.
I committed this.
> Trash URI semantics can be relaxed
> ----------------------------------
>
> Key: HADOOP-5086
> URL: https://issues.apache.org/jira/browse/HADOOP-5086
> Project: Hadoop Core
> Issue Type: Improvement
> Components: fs
> Affects Versions: 0.18.0
> Reporter: Chris Douglas
> Assignee: Chris Douglas
> Priority: Minor
> Fix For: 0.19.1
>
> Attachments: 5086-0.patch, 5086-1.patch
>
>
> When using fully qualified URIs with FsShell, the authority element of the
> URI must match the default filesystem exactly, or else one may get an error
> message when the trash is enabled:
> {noformat}
> $ hadoop fs -rmr hdfs://namenode1/user/foo/bar
> rmr: Wrong FS: hdfs://namenode1/user/foo/bar, expected:
> hdfs://namenode1.foobar.com
> Usage: java FsShell [-rmr <path>]
> $ hadoop fs -rmr hdfs://namenode1.foobar.com/user/foo/bar
> $
> {noformat}
> It should be possible to use the FileSystem for the Path provided rather than
> the default FileSystem. 0.17 was less particular about this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
