[
https://issues.apache.org/jira/browse/PHOENIX-1121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14243583#comment-14243583
]
James Taylor commented on PHOENIX-1121:
---------------------------------------
My initial take on the priorities of this are:
# PHOENIX-1197 Measure the performance impact of enabling tracing. If tracing
puts too high a load on a cluster, that determines whether or not we can keep
in on in production.
# PHOENIX-1519 Determine the usefulness of tracing. Are we capturing enough
information to be useful? Is it structured in a such a way to lend itself to
analysis?
# PHOENIX-1433, PHOENIX-1191, PHOENIX-1518, PHOENIX-1115 Provide a SQL command
to turn tracing on/off. These would get us to the point where we could enable
tracing for a single connection. If tracing produces information about other
queries running, perhaps that's ok if a) the load is low enough, and b) it's
easy to query the tracing table to get the information you're after.
# PHOENIX-1241 Add typing to trace annotations. This allows the information
captured in the tracing table to be "typed". Without this, doing any reasonable
querying over the data (i.e. analysis) will be difficult.
# PHOENIX-1120 Provide additional metrics beyond wall clock time. What
additional information should we attempt to capture with tracing?
> Improve tracing in Phoenix
> --------------------------
>
> Key: PHOENIX-1121
> URL: https://issues.apache.org/jira/browse/PHOENIX-1121
> Project: Phoenix
> Issue Type: Improvement
> Reporter: James Taylor
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
