[
https://issues.apache.org/jira/browse/MAPREDUCE-3377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13188082#comment-13188082
]
Harsh J commented on MAPREDUCE-3377:
------------------------------------
This seems to affect only the new API. The way the stable API does this remains
consistent with how it used to be in 0.20.2.
Test case does fail without JC change. +1 for this patch, but we need a test
case for trunk too, and if it fails without changes, a fix as well.
On 0.22+, the area of change would be under JobSubmitter#checkSpecs(…).
> 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: 0.20.203.0, 1.0.0
> Environment: 0.20.203.0 standalone JDK 1.6 Linux
> Reporter: Jane Chen
> Assignee: Jane Chen
> Fix For: 1.1.0
>
> Attachments: mapreduce-3377-branch-1.patch, mapreduce-3377.patch,
> mapreduce-3377.patch
>
>
> 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
