[
https://issues.apache.org/jira/browse/MAPREDUCE-2612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon updated MAPREDUCE-2612:
-----------------------------------
Status: Open (was: Patch Available)
This patch doesn't seem like a good idea to me.
Counters are constructed on-demand. So, the non-existence of a counter is
indeed equivalent to the value 0. For example, if running a job where some
counters are incremented only in reducers, and the reducers haven't started
yet, we don't want to throw error messages if the user is trying to fetch those
counters.
> The result returned by the wrong usage of the command "job -counter<job-id>
> <group-name> <counter-name> "is not appropriate
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-2612
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2612
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Affects Versions: 0.23.0
> Reporter: XieXianshan
> Priority: Minor
> Fix For: 0.23.0
>
> Attachments: MAPREDUCE-2612-0627, Mapreduce_2612
>
>
> The result returned by Map/Reduce command "job -counter<job-id> <group-name>
> <counter-name> " is always zero ,when use this command with incorrect group
> name or counter name.
> It is very easy to be misunderstood if users just make a spelling mistake.
> So,for more comprehensible information, more detailed results should be
> displayed as the following:
> [Could not find group FileSystemCounters_err] <--incorrect group name
> or
> [Could not find counter FILE_BYTES_READ_err in the group FileSystemCounters]
> <--incorrect counter name
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
