[
https://issues.apache.org/jira/browse/HADOOP-1783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12524239
]
Ahad Rana commented on HADOOP-1783:
-----------------------------------
On a broader note, I believe it would be a good thing to make it a rule that
all FileSystem implementations return fully qualified (scheme and host
specified) paths in all cases. Since the system uses Path objects everywhere,
and in most cases does a late, on demand, resolution from Path to FileSystem
object and then Input / OutputStream, an improperly qualified path combined
with the use of more than one FileSystem for an Input / Output source, is bound
to cause unpredictable behavior elsewhere in the code as well.
Just a suggestion.
Thanks,
Ahad.
> keyToPath in Jets3tFileSystemStore needs to return absolute path
> ----------------------------------------------------------------
>
> Key: HADOOP-1783
> URL: https://issues.apache.org/jira/browse/HADOOP-1783
> Project: Hadoop
> Issue Type: Bug
> Components: fs/s3
> Affects Versions: 0.1.0, 0.1.1, 0.2.0, 0.2.1, 0.3.0, 0.3.1, 0.3.2, 0.4.0,
> 0.5.0, 0.6.0, 0.6.1, 0.6.2, 0.7.0, 0.7.1, 0.7.2, 0.8.0, 0.9.0, 0.9.1, 0.9.2,
> 0.10.0, 0.10.1, 0.11.0, 0.11.1, 0.11.2, 0.12.0, 0.12.1, 0.12.2, 0.12.3,
> 0.13.0, 0.13.1, 0.14.0
> Environment: hadoop 0.14.0 running under ec2 with s3 filesystem
> Reporter: Ahad Rana
>
> The keyToPath method probably needs to:
> 1. take the bucket identifier as a parameter.
> 2. set the returned Path object's protocol plus authority (bucket).
> Currently, APIs such as <i>listSubPaths</i> return relative paths (for a
> directory listing). This in turn breaks map reduce operations if the default
> file system is set to be something other than S3 (via fs.default.name, for
> example).
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
