hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Harsh J (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-7659) fs -getmerge isn't guaranteed to work well over non-HDFS filesystems
Date Fri, 25 May 2012 12:48:24 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-7659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Harsh J updated HADOOP-7659:
----------------------------

          Resolution: Fixed
       Fix Version/s: 3.0.0
    Target Version/s:   (was: 3.0.0)
        Release Note: Documented that the "fs -getmerge" shell command may not work properly
over non HDFS-filesystem implementations due to platform-varying file list ordering.
              Status: Resolved  (was: Patch Available)

Committed revision 1342600 to trunk.
                
> fs -getmerge isn't guaranteed to work well over non-HDFS filesystems
> --------------------------------------------------------------------
>
>                 Key: HADOOP-7659
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7659
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: fs
>    Affects Versions: 0.20.204.0
>            Reporter: Harsh J
>            Assignee: Harsh J
>            Priority: Minor
>             Fix For: 3.0.0
>
>         Attachments: HADOOP-7659.patch
>
>
> When you use {{fs -getmerge}} with HDFS, you are guaranteed file list sorting (part-00000,
part-00001, onwards). When you use the same with other FSes we bundle, the ordering of listing
is not guaranteed at all. This is cause of http://download.oracle.com/javase/6/docs/api/java/io/File.html#list()
which we use internally for native file listing.
> This should either be documented as a known issue on -getmerge help pages/mans, or a
consistent ordering (similar to HDFS) must be applied atop the listing. I suspect the latter
only makes it worthy for what we include - while other FSes out there still have to deal with
this issue. Perhaps we need a recommendation doc note added to our API?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message