[
https://issues.apache.org/jira/browse/PHOENIX-1115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244688#comment-14244688
]
Jesse Yates commented on PHOENIX-1115:
--------------------------------------
So that was just using the standard HTrace trace allocation mechanism (or
allowing the client to specify the id via properties). Since the traceid is
part of the key, you just add a where clause for that id and get all the trace
info back. Or filter as you see fit on various properties
> 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: Jeffrey Zhong
> Attachments: 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)
