[
https://issues.apache.org/jira/browse/MAPREDUCE-2492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13037231#comment-13037231
]
Chris Douglas commented on MAPREDUCE-2492:
------------------------------------------
Adding progress to {{TaskAttemptContext}} makes sense. Minor points on the
tests:
* Please use JUnit4 annotations instead of extending {{TestCase}} for new tests
* Using {{@BeforeClass}} instead of an instance initializer block would be
easier to read and would fail appropriately
* Deleting "test.build.data" (defaulting to "/tmp") recursively when the test
runs could have bad side-effects. Please use a subdir of {{rootTestDir}} instead
* Cleaning up after the test would also be a good idea ({{@AfterClass}}). Right
now, many of the tests will not delete output when the test fails.
> [MAPREDUCE] The new MapReduce API should make available task's progress to
> the task
> -----------------------------------------------------------------------------------
>
> Key: MAPREDUCE-2492
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2492
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: task
> Affects Versions: 0.23.0
> Reporter: Amar Kamat
> Assignee: Amar Kamat
> Attachments: MAPREDUCE-2492-v1.3.patch
>
>
> There is no way to get the task's current progress in the new MapReduce API.
> It would be nice to make it available so that the task (map/reduce) can use
> it.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
