[
https://issues.apache.org/jira/browse/HADOOP-1041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12477426
]
Hadoop QA commented on HADOOP-1041:
-----------------------------------
-1, because 3 attempts failed to build and test the latest attachment
http://issues.apache.org/jira/secure/attachment/12352356/1041_1.patch against
trunk revision unknown. Please note that this message is automatically
generated and may represent a problem with the automation system and not the
patch. Results are at
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch
> Counter names are ugly
> ----------------------
>
> Key: HADOOP-1041
> URL: https://issues.apache.org/jira/browse/HADOOP-1041
> Project: Hadoop
> Issue Type: Improvement
> Components: mapred
> Affects Versions: 0.12.0
> Reporter: Owen O'Malley
> Assigned To: David Bowen
> Fix For: 0.12.0
>
> Attachments: 1041.patch, 1041_1.patch
>
>
> Having the complete class name in the counter names makes them unique, but
> they are ugly to present to non-developers. It would be nice to have some way
> to have a nicer string presented to the user. Currently, the Enum is
> converted to a name like:
> key.getDeclaringClass().getName() + "#" + key.toString()
> which gives counter names like
> "org.apache.hadoop.examples.RandomWriter$Counters#BYTES_WRITTEN"
> which is unique, but not very user friendly. Perhaps, we should strip off the
> class name for presenting to the users, which would allow them to make nice
> names. In particular, you could define an enum type that overloaded toString
> to print a nice user friendly string.
> Thoughts?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
