[
https://issues.apache.org/jira/browse/PHOENIX-1115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14315549#comment-14315549
]
James Taylor commented on PHOENIX-1115:
---------------------------------------
Would you mind writing up a short design doc first, [~rajeshbabu]? It would be
good to see how other RDBMS surface this. Not sure how much utility there is in
printing to stdout. Even dumping to a file isn't particularly useful unless
it's in a format that other tools can digest. Might be best to keep this patch
simple and just provide a way of turning tracing on/off as [~samarthjain]
described. How do various database system enable this (i.e. Postgres, Oracle,
MySQL)? I think getting the structure of the data in the trace table is more
important so it can be queried (PHOENIX-1241). Providing a way of visualizing
the trace may be better left to a different tool, as UI is outside of the scope
of Phoenix IMO. A simple webapp that does charting by issuing querying against
the trace table would be sufficient for us, I think. [~mujtabachohan] has done
a lot of that - he could probably whip something up as a demo once the trace
information is structured the way we need it to be.
> 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
> Affects Versions: 5.0.0, 4.1
> Reporter: James Taylor
> Assignee: Rajeshbabu Chintaguntla
> Attachments: PHOENIX-1115.patch, PHOENIX-1115_v2.patch, Screen Shot
> 2014-11-21 at 3.41.41 PM.png
>
>
> 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)
