Return-Path: X-Original-To: apmail-hadoop-mapreduce-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-mapreduce-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7E72499D6 for ; Thu, 29 Mar 2012 08:06:13 +0000 (UTC) Received: (qmail 79133 invoked by uid 500); 29 Mar 2012 08:06:13 -0000 Delivered-To: apmail-hadoop-mapreduce-issues-archive@hadoop.apache.org Received: (qmail 79095 invoked by uid 500); 29 Mar 2012 08:06:13 -0000 Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: mapreduce-issues@hadoop.apache.org Delivered-To: mailing list mapreduce-issues@hadoop.apache.org Received: (qmail 79084 invoked by uid 99); 29 Mar 2012 08:06:13 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 29 Mar 2012 08:06:13 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 29 Mar 2012 08:06:12 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id B403A34CC84 for ; Thu, 29 Mar 2012 08:05:51 +0000 (UTC) Date: Thu, 29 Mar 2012 08:05:51 +0000 (UTC) From: "Hudson (Commented) (JIRA)" To: mapreduce-issues@hadoop.apache.org Message-ID: <1897188695.31743.1333008351738.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <1194629361.11804.1320781671787.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (MAPREDUCE-3377) Compatibility issue with 0.20.203. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/MAPREDUCE-3377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13241067#comment-13241067 ] Hudson commented on MAPREDUCE-3377: ----------------------------------- Integrated in Hadoop-Common-trunk-Commit #1946 (See [https://builds.apache.org/job/Hadoop-Common-trunk-Commit/1946/]) MAPREDUCE-3377. Added a unit test to ensure OutputCommitter.checkOutputSpecs is called prior to copying job.xml. Contributed by Jane Chen. (Revision 1306736) Result = SUCCESS 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