You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Boris Shkolnik (JIRA)" <ji...@apache.org> on 2011/04/19 19:28:05 UTC
[jira] [Resolved] (HADOOP-5749) FsShell forces creation of default
filesystem object and incorrectly uses default filesystem in some places
[ https://issues.apache.org/jira/browse/HADOOP-5749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Boris Shkolnik resolved HADOOP-5749.
------------------------------------
Resolution: Duplicate
this issue is fixed in HADOOP-7207
> FsShell forces creation of default filesystem object and incorrectly uses default filesystem in some places
> ------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-5749
> URL: https://issues.apache.org/jira/browse/HADOOP-5749
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs
> Reporter: Joydeep Sen Sarma
> Assignee: Joydeep Sen Sarma
> Attachments: hadoop-5749.1.patch, hadoop-5749.2.patch
>
>
> i was trying do fs -ls operations on s3n filesystem uris (which was not configured as my default filesystem - the default filesystem was not bought up). these operations failed since they always tried to open the default filesystem (error: ""Bad connection to FS. command aborted."). but the default filesystem is not required in these cases at all.
> the code also shows that the default filesystem is used in certain places (instead of the filesystem of the uri). for instance:
> copy(String argv[], ...) { ...
> Path dst = new Path(dest);
> if (!fs.isDirectory(dst)) {
> there are some other places as well.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira