hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-933) Application defined InputSplits do not work
Date Sat, 10 Feb 2007 00:20:05 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471885
] 

Hadoop QA commented on HADOOP-933:
----------------------------------

-1, because 3 attempts failed to build and test the latest attachment (http://issues.apache.org/jira/secure/attachment/12350806/client-split.patch)
against trunk revision r505557. Please note that this message is automatically generated and
may represent a problem with the automation system and not the 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
>         Assigned To: Owen O'Malley
>             Fix For: 0.12.0
>
>         Attachments: client-split.patch, 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.


Mime
View raw message