[
https://issues.apache.org/jira/browse/PHOENIX-1115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14316603#comment-14316603
]
Jeffrey Zhong commented on PHOENIX-1115:
----------------------------------------
RDBMS does trace in their own ways. In MySQL case, a user can either dump the
trace info into a file or console. In this case, we dump the trace info to
console is a useful way when using SQLLine for debugging or quickly examine
some queries. We could introduce a connection setting so that a user can choose
where to write trace info like TraceOutput=[NONE|CONSOLE|<trace file path>].
> 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)
