[
https://issues.apache.org/jira/browse/MAPREDUCE-740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12731668#action_12731668
]
Nigel Daley commented on MAPREDUCE-740:
---------------------------------------
-1. No unit test or justification.
Should logJobSummary(...) have a null check on job so we don't get NPEs? Ditto
on meterTaskAttempt(..)?
If you disagree on null check, can you document that input parameters must not
be null OR document @throws NullPointerException if input parameter is null.
> Provide summary information per job once a job is finished.
> -----------------------------------------------------------
>
> Key: MAPREDUCE-740
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-740
> Project: Hadoop Map/Reduce
> Issue Type: New Feature
> Components: jobtracker
> Reporter: Hong Tang
> Assignee: Arun C Murthy
> Fix For: 0.21.0
>
> Attachments: MAPREDUCE-740_0_20090709.patch,
> MAPREDUCE-740_0_20090713.patch, MAPREDUCE-740_0_20090713_yhadoop20.patch
>
>
> It would be nice if JobTracker can output a one line summary information per
> job once a job is finished. Otherwise, users or system administrators would
> end up scraping individual job history logs.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
