Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hadoop-dev@lucene.apache.org
Message-ID: <14894955.1182211346335.JavaMail.jira@brutus>
Date: Mon, 18 Jun 2007 17:02:26 -0700 (PDT)
From: "Senthil Subramanian (JIRA)" <jira@apache.org>
To: hadoop-dev@lucene.apache.org
Subject: [jira] Updated: (HADOOP-1441) Splittability of input should be
 controllable by application
In-Reply-To: <9555375.1180480097432.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Senthil Subramanian updated HADOOP-1441:
----------------------------------------

    Attachment: HADOOP-1441_1.patch

Added a configuration variable mapred.input.issplitable (default: true) which can be used to tell the framework not to split input files even if the underlying InputFormat is splittable.

> Splittability of input should be controllable by application
> ------------------------------------------------------------
>
>                 Key: HADOOP-1441
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1441
>             Project: Hadoop
>          Issue Type: Improvement
>          Components: mapred
>    Affects Versions: 0.12.3
>         Environment: ALL
>            Reporter: Milind Bhandarkar
>            Assignee: Milind Bhandarkar
>             Fix For: 0.14.0
>
>         Attachments: HADOOP-1441_1.patch
>
>
> Currently, isSplittable method of FileInputFormat always returns true. For some applications, it becomes necessary that the map task process entire file, rather than a block. Therefore, splittability of input (i.e. block-level split vs file-level-split) should be controllable by user via a configuration variable. The default could be block-level split, as is.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.