Is your patch applicable on TRUNK ?
If so, why not prepare a patch for TRUNK ?
Hadoop QA always runs patch against TRUNK.
On Tue, Jan 17, 2012 at 1:34 PM, Jane Chen <[EMAIL PROTECTED]> wrote:
> I created and submitted a patch on branch 1. Apparently the patch was
> attempted to be applied on trunk and failed. What do I need to do to make
> the patch applied on branch 1?
> -----Original Message-----
> From: Hadoop QA (Commented) (JIRA) [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, January 17, 2012 11:26 AM
> To: Jane Chen
> Subject: [jira] [Commented] (MAPREDUCE-3377) Compatibility issue with
> Hadoop QA commented on MAPREDUCE-3377:
> -1 overall. Here are the results of testing the latest attachment
> against trunk revision .
> +1 @author. The patch does not contain any @author tags.
> +1 tests included. The patch appears to include 3 new or modified
> -1 patch. The patch command could not apply the patch.
> Console output:
> This message is automatically generated.
> > Compatibility issue with 0.20.203.
> > ----------------------------------
> > Key: MAPREDUCE-3377
> > URL:
> > 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
> This message is automatically generated by JIRA.
> If you think it was sent incorrectly, please contact your JIRA
> For more information on JIRA, see: http://www.atlassian.com/software/jira