[
https://issues.apache.org/jira/browse/HADOOP-3970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amar Kamat updated HADOOP-3970:
-------------------------------
Description: Counters that are written to the JobHistory are stringified
using {{Counters.makeCompactString()}}. The format in which this api converts
the counter into a string is _groupname.countername:value_. The problem is that
_groupname_ and _countername_ can contain a '.' and hence recovering the
counter becomes difficult. Since JobHistory can be used for various purposes,
reconstructing the counter object back might be useful. One such usecase is
HADOOP-3245. There should be some way to recover the counter object back from
its string representation and also to keep the string version readable. (was:
Counters that are written to the history are stringified using
{{Counters.getCompactString()}}. The format in which this api converts the
counter into a string is _groupname.countername:value_. The problem is that the
groupname and the countername can contain '.' and hence recovering the counter
back becomes difficult. Since jobhistory can be used for various purposes,
reconstructing the counter object back might be useful. One such usecase is
HADOOP-3245. There should be some way to recover the counter object back from
the string representation and also to keep the stringified version readable.)
> Counters written to the job history cannot be recovered back
> ------------------------------------------------------------
>
> Key: HADOOP-3970
> URL: https://issues.apache.org/jira/browse/HADOOP-3970
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Reporter: Amar Kamat
>
> Counters that are written to the JobHistory are stringified using
> {{Counters.makeCompactString()}}. The format in which this api converts the
> counter into a string is _groupname.countername:value_. The problem is that
> _groupname_ and _countername_ can contain a '.' and hence recovering the
> counter becomes difficult. Since JobHistory can be used for various purposes,
> reconstructing the counter object back might be useful. One such usecase is
> HADOOP-3245. There should be some way to recover the counter object back from
> its string representation and also to keep the string version readable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.