[
https://issues.apache.org/jira/browse/HADOOP-1041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475945
]
David Bowen commented on HADOOP-1041:
-------------------------------------
Good idea! Then the names can even be localized into other languages if anyone
wants to do that.
There is still the question of sorting. I guess I would tend to sort by the
displayed names. So if people want to get things grouped they would need to
include some context at the beginning of the display name. E.g.
org.apache.hadoop.examples.RandomWriter$Counters#BYTES_WRITTEN=Examples: Number
of bytes randomly written
I would have thought the ResourceBundle file name would be something like
HaddopCounterNames.properties, but perhaps you had in mind some things other
than counters that could usefully be included?
> 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
> Fix For: 0.12.0
>
>
> 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.
