[
https://issues.apache.org/jira/browse/PHOENIX-1115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14338221#comment-14338221
]
Rajeshbabu Chintaguntla commented on PHOENIX-1115:
--------------------------------------------------
[~ndimiduk]
bq. Why does TRACE ON return a traceId? I guess that's the root span of the
next query.
Yes, it's root span for next query.
bq. I would expect the trace table to be printed after the result table.
We can do this but to print trace table we need to use specific query which may
not always useful for the user and also some users can use visualizing tools
for analyzing the trace than analyzing the trace printed to file/console. Then
the user can directly run the query of his need using the trace id.
bq. Also, would be good if we could order the trace according to the
parent-child relationship, depth first perhaps.
We can do this using external tools and PHOENIX-1119 raised for that.
Thanks.
> Provide a SQL command to turn tracing on/off
> --------------------------------------------
>
> Key: PHOENIX-1115
> URL: https://issues.apache.org/jira/browse/PHOENIX-1115
> Project: Phoenix
> Issue Type: Sub-task
> Reporter: James Taylor
> Assignee: Rajeshbabu Chintaguntla
> Fix For: 5.0.0
>
> Attachments: PHOENIX-1115.patch, PHOENIX-1115_v2.patch,
> PHOENIX-1115_v3.patch, PHOENIX-1115_v4.patch, Screen Shot 2014-11-21 at
> 3.41.41 PM.png, tracing_in_different_rdbms.pdf
>
>
> Provide a SQL command that turns tracing on and off. For example, Oracle has
> this:
> {code}
> ALTER SESSION SET sql_trace = true;
> ALTER SESSION SET sql_trace = false;
> {code}
> We might consider allowing the sampling rate to be set as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
