You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Chris Douglas (JIRA)" <ji...@apache.org> on 2009/01/21 03:07:59 UTC
[jira] Updated: (HADOOP-5086) Trash URI semantics can be relaxed
[ https://issues.apache.org/jira/browse/HADOOP-5086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Douglas updated HADOOP-5086:
----------------------------------
Attachment: 5086-0.patch
Attaching patch shuffling cstr params around, added a unit test (shouldn't the unit test be in o.a.h.fs? If it were moved, this could use Trash::getCurrentTrashDir instead of hard-coding its params).
> 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
> Priority: Minor
> Attachments: 5086-0.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.