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

Posted to dev@phoenix.apache.org by "Kiran Kumar Maturi (Jira)" <ji...@apache.org> on 2021/07/30 07:34:00 UTC

[jira] [Updated] (PHOENIX-5974) QueryId for Phoenix Query

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

Kiran Kumar Maturi updated PHOENIX-5974:
----------------------------------------
    Summary: QueryId for Phoenix Query  (was: RequestId for Phoenix Query)

> QueryId for Phoenix Query
> -------------------------
>
>                 Key: PHOENIX-5974
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-5974
>             Project: Phoenix
>          Issue Type: New Feature
>            Reporter: Pranshu Khandelwal
>            Assignee: Kiran Kumar Maturi
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Add a TraceId corresponding to a Phoenix Query which translates further into an HBase mutationId. Using this TraceId one can log information about the bottlenecks in the Network and Trace out the flow of the SQL like Phoenix Query till it compiles as an Hbase mutation and ultimately into a Message to the RPC Layer.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)