[
https://issues.apache.org/jira/browse/MAPREDUCE-3377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13241239#comment-13241239
]
Hudson commented on MAPREDUCE-3377:
-----------------------------------
Integrated in Hadoop-Hdfs-trunk #999 (See
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/999/])
MAPREDUCE-3377. Added a unit test to ensure
OutputCommitter.checkOutputSpecs is called prior to copying job.xml.
Contributed by Jane Chen. (Revision 1306736)
Result = FAILURE
acmurthy :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1306736
Files :
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/test/java/org/apache/hadoop/mapreduce/TestMROutputFormat.java
> 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
> Environment: 0.20.203.0 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, out-before
>
>
> 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
