Return-Path: Delivered-To: apmail-hadoop-core-dev-archive@www.apache.org Received: (qmail 10294 invoked from network); 28 Nov 2008 16:46:36 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 28 Nov 2008 16:46:36 -0000 Received: (qmail 23500 invoked by uid 500); 28 Nov 2008 16:46:46 -0000 Delivered-To: apmail-hadoop-core-dev-archive@hadoop.apache.org Received: (qmail 23470 invoked by uid 500); 28 Nov 2008 16:46:46 -0000 Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: core-dev@hadoop.apache.org Delivered-To: mailing list core-dev@hadoop.apache.org Received: (qmail 23451 invoked by uid 99); 28 Nov 2008 16:46:46 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Nov 2008 08:46:46 -0800 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Nov 2008 16:45:27 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 81009234C2A8 for ; Fri, 28 Nov 2008 08:45:44 -0800 (PST) Message-ID: <1973731873.1227890744527.JavaMail.jira@brutus> Date: Fri, 28 Nov 2008 08:45:44 -0800 (PST) From: "Enis Soztutar (JIRA)" To: core-dev@hadoop.apache.org Subject: [jira] Commented: (HADOOP-4565) MultiFileInputSplit can use data locality information to create splits In-Reply-To: <525654219.1225490984230.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HADOOP-4565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12651600#action_12651600 ] Enis Soztutar commented on HADOOP-4565: --------------------------------------- I agree with Joydeep that if this inputFormat is intended for handling large number of files, then the changes should be done in the MultiFileInputFormat itself, rather than introducing a new class. However a quick glance to the patch indicates that this inputformat works for files having more than one block. I guess we should better introduce the file[] -> blocks[] -> {hosts[], racks[]} -> splits[] logic in FileInputFormat and use this logic both in FileInputFormat and MultiFileInputFormat. I have opened an issue for a concrete MultiFileInputFormat implementation (HADOOP-4741), and attached a patch which I developed some time ago. HADOOP-4741 depends on this issue. > MultiFileInputSplit can use data locality information to create splits > ---------------------------------------------------------------------- > > Key: HADOOP-4565 > URL: https://issues.apache.org/jira/browse/HADOOP-4565 > Project: Hadoop Core > Issue Type: Improvement > Components: mapred > Reporter: dhruba borthakur > Assignee: dhruba borthakur > Attachments: CombineMultiFile.patch, CombineMultiFile2.patch, CombineMultiFile3.patch > > > The MultiFileInputFormat takes a set of paths and creates splits based on file sizes. Each splits contains a few files an each split are roughly equal in size. It would be efficient if we can extend this InputFormat to create splits such each all the blocks in one split and either node-local or rack-local. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.