[
https://issues.apache.org/jira/browse/HADOOP-3970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12628557#action_12628557
]
Amar Kamat commented on HADOOP-3970:
------------------------------------
bq. equals and hashCode implementation: Since the counter's value can change
over time, I am thinking that these methods should not depend on the value of
the counter. ....
The code to check content equality of counters is moved to the test case as
only the test case requires it for now.
bq. getBlock: We expect a start and end. If there's no start or no end, should
we fail fast ?
Now {{getBlock()}} throws ParseException if the string is malformed and returns
null is no block found
> 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
> Attachments: HADOOP-3970-v1.patch, HADOOP-3970-v2.patch,
> HADOOP-3970-v3.patch, HADOOP-3970-v4.patch
>
>
> 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.
