[
https://issues.apache.org/jira/browse/MAPREDUCE-4932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13621357#comment-13621357
]
Alejandro Abdelnur commented on MAPREDUCE-4932:
-----------------------------------------------
Looking at Job.getTaskCompletionEvents(int) in Hadoop 1, it delegates to
JobClient.getTaskCompletionEvents(int) which caps the max number of event to
10. Unless I'm missing something we should be doing the same here, thus not
only providing API compat but behavior compat.
> mapreduce.job#getTaskCompletionEvents incompatible with MR1
> -----------------------------------------------------------
>
> 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
> Attachments: 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
