[
https://issues.apache.org/jira/browse/HADOOP-10663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14029634#comment-14029634
]
Chris Douglas commented on HADOOP-10663:
----------------------------------------
I'm confused. This was the change:
{noformat}
Path mapOutput = mapOutputFile.getOutputFile();
- FileSystem localFS = FileSystem.getLocal(conf);
- return localFS.getFileStatus(mapOutput).getLen();
+ FileSystem fs = mapOutput.getFileSystem(conf);
+ return fs.getFileStatus(mapOutput).getLen();
{noformat}
That code should work if {{mapOutput}} is a fully qualified {{Path}}, right?
> Path.getFileSystem should identify Windows drive (c:) like files and return
> the localFS
> ---------------------------------------------------------------------------------------
>
> Key: HADOOP-10663
> URL: https://issues.apache.org/jira/browse/HADOOP-10663
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 3.0.0
> Reporter: Remus Rusanu
> Assignee: Remus Rusanu
> Attachments: HADOOP-10663.1.patch
>
>
> While investigating the problem with MAPREDUCE-5912 I considered that the
> fact that asking a Windows specific Path to get its file system should not
> return the default FS, but the localFS. Specifically, I believe that
> Path.initialize should identify such names as belonging to the 'file://'
> scheme (when null) and so create appropriate URIs.
> I do not have the know-how to evaluate the bigger impact of such a change.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
