hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Foley (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-3377) Compatibility issue with 0.20.203.
Date Wed, 02 May 2012 22:34:51 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-3377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266972#comment-13266972

Matt Foley commented on MAPREDUCE-3377:

The merge to branch-1.0 included, apparently by accident, changes to build.xml that broke
the native builds of task-controller and jsvc.  I've reverted the build.xml change only. 
This error only affected branch-1.0, not branch-1 nor the other branches.
> Compatibility issue with 0.20.203.
> ----------------------------------
>                 Key: MAPREDUCE-3377
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3377
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>    Affects Versions:
>         Environment: standalone JDK 1.6 Linux
>            Reporter: Jane Chen
>            Assignee: Jane Chen
>             Fix For: 1.0.3, 2.0.0
>         Attachments: err-after, err-before, mapreduce-3377-branch-1.patch, mapreduce-3377-branch-1.patch,
mapreduce-3377.patch, mapreduce-3377.patch, mapreduce-3377.patch, mapreduce-3377.patch, out-after,
> I have an OutputFormat which implements Configurable.  I set new config entries to a
job configuration during checkOutputSpec() so that the tasks will get the config entries through
the job configuration.  This works fine in 0.20.2, but stopped working starting from 0.20.203.
 With 0.20.203, my OutputFormat still has the configuration set, but the copy a task gets
does not have the new entries that are set as part of checkOutputSpec().  
> I believe that the problem is with JobClient.  The job configuration needs to wait till
checkOutputSpec() is returned before being cloned and submitted.

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


View raw message