[
https://issues.apache.org/jira/browse/MAPREDUCE-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12886668#action_12886668
]
Tom White commented on MAPREDUCE-1920:
--------------------------------------
Actually, I would do it the other way round. Users expect to be able to get
counters from jobs they have just run, as witnessed by Aaron's experience that
led to this bug (also
http://lucene.472066.n3.nabble.com/Hadoop-0-21-job-getCounters-returns-null-td947190.html).
I would rather have the default configuration work as expected, and advanced
users can turn off the job store if they don't want to use it. Does that sound
reasonable?
> Job.getCounters() returns null when using a cluster
> ---------------------------------------------------
>
> Key: MAPREDUCE-1920
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1920
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Affects Versions: 0.21.0
> Reporter: Aaron Kimball
> Assignee: Tom White
> Priority: Critical
> Attachments: MAPREDUCE-1920.patch
>
>
> Calling Job.getCounters() after the job has completed (successfully) returns
> null.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
