[
https://issues.apache.org/jira/browse/MAPREDUCE-5529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13778434#comment-13778434
]
Zhijie Shen commented on MAPREDUCE-5529:
----------------------------------------
[~vinodkv], we've checked this type of binary incompatibility before.
Unfortunately, this one has been missed.
Anyway, since it's four almost four month before when we checked the
incompatibility, IMHO, it's good to check it again in case we missed some thing
in the last round, and have some more which was broken afterwards.
> Binary incompatibilities in mapred.lib.TotalOrderPartitioner between branch-1
> and branch-2
> ------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-5529
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5529
> Project: Hadoop Map/Reduce
> Issue Type: Sub-task
> Components: mrv1, mrv2
> Affects Versions: 2.1.1-beta
> Reporter: Robert Kanter
> Assignee: Robert Kanter
> Priority: Blocker
> Attachments: MAPREDUCE-5529.patch, MAPREDUCE-5529.patch
>
>
> {{mapred.lib.TotalOrderPartitioner}} in branch-1 has these two methods:
> {code:java}
> public static String getPartitionFile(JobConf job)
> public static void setPartitionFile(JobConf job, Path p)
> {code}
> In branch-2, {{mapred.lib.TotalOrderPartitioner}} is now a subclass of
> {{mapred.lib.TotalOrderPartitioner}}, from which it inherits the similar
> methods:
> {code:java}
> public static String getPartitionFile(Configuration conf)
> public static void setPartitionFile(Configuration conf, Path p)
> {code}
> This means that any code that does either of the following:
> {code:java}
> TotalOrderPartitioner.setPartitionFile(new JobConf(), new Path("/"));
> String str = TotalOrderPartitioner.getPartitionFile(new JobConf());
> {code}
> will not be binary compatible (that is, if compiled against branch-1, it will
> throw a {{NoSuchMethodError}} if run against branch-2).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
