hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amareshwari Sriramadasu (JIRA)" <j...@apache.org>
Subject [jira] Commented: (MAPREDUCE-1905) Context.setStatus() and progress() api are ignored
Date Fri, 06 Aug 2010 10:37:16 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-1905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12896014#action_12896014

Amareshwari Sriramadasu commented on MAPREDUCE-1905:

I agree with Vinod on the above comment that TaskAttemptContextImpl should know about reporter.

Also, reporter methods in TaskInputOutputContext i.e getCounter() methods should be moved
to TaskAttemptContext interface. Currently, {Input/Output}Format cannot increment counters.
Though there is a hack used in LineRecordReader : type cast TaskAttemptContext to MapContext
for accessing counter, which is ugly. 


> Context.setStatus() and progress() api are ignored
> --------------------------------------------------
>                 Key: MAPREDUCE-1905
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1905
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: task
>    Affects Versions: 0.21.0
>            Reporter: Amareshwari Sriramadasu
>            Assignee: Amareshwari Sriramadasu
>            Priority: Blocker
>         Attachments: patch-1905.txt
> TaskAttemptContext.setStatus() and progress() were overriden in TaskInputOutputContext,
inbranch 0.20, to call the underlying reporter apis. But the methods are no more over-riden
in TaskInputOutputContextImpl after MAPREDUCE-954.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message