[
https://issues.apache.org/jira/browse/HTRACE-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15056380#comment-15056380
]
Colin Patrick McCabe commented on HTRACE-329:
---------------------------------------------
I sort of get what you're saying, but I feel like the kind of people who are
going to be looking at raw JSON are probably also people who won't mind short
labels. We have all these GUIs and tools-- shouldn't we be using them to view
traces? Google's tracing system for Chrome also uses JSON with very short
labels-- two letters in their case, but the idea is the same. The short JSON
labels aren't even a problem in our Javascript, since we have Backbone objects
to wrap them and give more friendly labels. I guess I haven't thought about it
much, though...
> JSON labels are opaque and so confound
> --------------------------------------
>
> Key: HTRACE-329
> URL: https://issues.apache.org/jira/browse/HTRACE-329
> Project: HTrace
> Issue Type: Improvement
> Reporter: stack
>
> Debugging, I get this in the log:
> {code}
> 2015-12-09 21:56:21,293 ERROR [localhost:61345.activeMasterManager]
> core.Tracer: Can't close TraceScope for
> {"a":"b45638d30b8c6e1dbdc001c6e7f1dd8f","b":1449726980426,"d":"get","r":"hconnection-0x6a38397","p":["b45638d30b8c6e1dbd33cf6dc5ce5206"]}
> because it is not the current TraceScope in thread
> localhost:61345.activeMasterManager
> {code}
> I could go consult a dictionary if such a thing existed on the htrace website
> (currently it does not) or go read up on some source code... but this is JSON
> so a.) perf is not a consideration so why bother shortening the labels in the
> name of 'perf' benefits and b.) JSON is ".. easy for humans to read and
> write." (second sentence on the website) yet here were are frustrating the
> first half of this sentence.
> Suggest more readable labels.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
