Return-Path: X-Original-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0C844C4C7 for ; Sat, 26 May 2012 11:43:28 +0000 (UTC) Received: (qmail 97359 invoked by uid 500); 26 May 2012 11:43:27 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 97119 invoked by uid 500); 26 May 2012 11:43:27 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-issues@hadoop.apache.org Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 97005 invoked by uid 99); 26 May 2012 11:43:24 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 26 May 2012 11:43:24 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id 141ED142837 for ; Sat, 26 May 2012 11:43:24 +0000 (UTC) Date: Sat, 26 May 2012 11:43:24 +0000 (UTC) From: "Hudson (JIRA)" To: common-issues@hadoop.apache.org Message-ID: <1835080540.5679.1338032604084.JavaMail.jiratomcat@issues-vm> In-Reply-To: <789359565.45091.1316502369073.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (HADOOP-7659) fs -getmerge isn't guaranteed to work well over non-HDFS filesystems MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HADOOP-7659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13283962#comment-13283962 ] Hudson commented on HADOOP-7659: -------------------------------- Integrated in Hadoop-Hdfs-trunk #1057 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/1057/]) HADOOP-7659. fs -getmerge isn't guaranteed to work well over non-HDFS filesystems (harsh) (Revision 1342600) Result = SUCCESS harsh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1342600 Files : * /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/fs/RawLocalFileSystem.java > 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