[
https://issues.apache.org/jira/browse/MAPREDUCE-4932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13635743#comment-13635743
]
Hudson commented on MAPREDUCE-4932:
-----------------------------------
Integrated in Hadoop-trunk-Commit #3631 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/3631/])
MAPREDUCE-4932. mapreduce.job#getTaskCompletionEvents incompatible with
Hadoop 1. (rkanter via tucu) (Revision 1469587)
Result = SUCCESS
tucu : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1469587
Files :
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapreduce/Job.java
> mapreduce.job#getTaskCompletionEvents incompatible with Hadoop 1
> ----------------------------------------------------------------
>
> Key: MAPREDUCE-4932
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4932
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 2.0.2-alpha
> Reporter: Robert Kanter
> Assignee: Robert Kanter
> Fix For: 2.0.5-beta
>
> Attachments: MAPREDUCE-4932.patch, MAPREDUCE-4932.patch,
> MAPREDUCE-4932.patch
>
>
> In MR1, {{org.apache.hadoop.mapreduce.Job#getTaskCompletionEvents}} takes one
> argument: {{int startFrom}}. In MR2, it now takes an additional argument:
> {{int numEvents}} (which is the max number of events to get). This makes
> them incompatible.
> I propose we add a second {{getTaskCompletionEvents}} method that simply
> calls the other one with {{numEvents}} set to {{Integer.MAX_VALUE}} to
> replicate the behavior of the MR1 version.
--
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
