hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Kanter (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-4932) mapreduce.job#getTaskCompletionEvents incompatible with MR1
Date Tue, 15 Jan 2013 18:08:13 GMT

     [ https://issues.apache.org/jira/browse/MAPREDUCE-4932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Robert Kanter updated MAPREDUCE-4932:

    Attachment: MAPREDUCE-4932.patch

In the second patch, {{getTaskCompletionEvents}} no longer throws an {{InterruptedException}}
> 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

View raw message