Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hadoop-dev@lucene.apache.org
Message-ID: <30442070.1169852989252.JavaMail.jira@brutus>
Date: Fri, 26 Jan 2007 15:09:49 -0800 (PST)
From: "Benjamin Reed (JIRA)" <jira@apache.org>
To: hadoop-dev@lucene.apache.org
Subject: [jira] Updated: (HADOOP-933) Application defined InputSplits do not
 work
In-Reply-To: <33356999.1169754469433.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-933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benjamin Reed updated HADOOP-933:
---------------------------------

    Attachment: JobInProgress.patch

> Application defined InputSplits do not work
> -------------------------------------------
>
>                 Key: HADOOP-933
>                 URL: https://issues.apache.org/jira/browse/HADOOP-933
>             Project: Hadoop
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.10.1
>            Reporter: Benjamin Reed
>             Fix For: 0.10.1
>
>         Attachments: JobInProgress.patch, MapTask.patch
>
>
> If an application defines its own InputSplit, the task tracker chokes when it cannot deserialize the InputSplit when it deserializes MapTasks it receives from the JobTracker. This is because the TaskTracker does not resolve classes from the job jar file. The attached patch delays resolution of the InputSplit until it is running in the context of the child process where it can resolve the InputSplit class.

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