You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@phoenix.apache.org by "James Taylor (JIRA)" <ji...@apache.org> on 2016/02/20 23:11:18 UTC

[jira] [Updated] (PHOENIX-1518) Scope tracing per connection

     [ https://issues.apache.org/jira/browse/PHOENIX-1518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James Taylor updated PHOENIX-1518:
----------------------------------
    Issue Type: Bug  (was: Sub-task)
        Parent:     (was: PHOENIX-1121)

> Scope tracing per connection
> ----------------------------
>
>                 Key: PHOENIX-1518
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-1518
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: James Taylor
>            Assignee: Samarth Jain
>
> Typically, an RDBMS has a tracing facility that's turned on for a connection. This then traces queries made through that connection, but not for other connections. Currently, if tracing is turned on for the client, the server will begin to trace *all* things Phoenix. We should scope tracing to a connection instead.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)