[
https://issues.apache.org/jira/browse/PHOENIX-5974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kiran Kumar Maturi updated PHOENIX-5974:
----------------------------------------
Description: Add a QueryId corresponding to a Phoenix Query which can be
used to uniquely identify the query. Propagate this QueryId further to HBase.
Hbase supports
[identifier](https://hbase.apache.org/apidocs/org/apache/hadoop/hbase/client/OperationWithAttributes.html#getId--)
for request . Hbase logs the identifier when request timesout or has a slow
response. This information is very useful in associating client and server side
information. Phoenix QueryId will help in analyzing client side logs also.
(was: 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.)
> 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 QueryId corresponding to a Phoenix Query which can be used to uniquely
> identify the query. Propagate this QueryId further to HBase. Hbase supports
> [identifier](https://hbase.apache.org/apidocs/org/apache/hadoop/hbase/client/OperationWithAttributes.html#getId--)
> for request . Hbase logs the identifier when request timesout or has a slow
> response. This information is very useful in associating client and server
> side information. Phoenix QueryId will help in analyzing client side logs
> also.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
