Uh oh!
There was an error while loading. Please reload this page.
PHOENIX-5974 add queryId for phoenix queries and propagate to hbase - #1250
PHOENIX-5974 add queryId for phoenix queries and propagate to hbase#1250kiran-maturi wants to merge 2 commits into
Conversation
stoty
commented
Jun 17, 2021
💔 -1 overall
This message was automatically generated. |
stoty
commented
Jun 17, 2021
💔 -1 overall
This message was automatically generated. |
stoty
commented
Jun 24, 2021
💔 -1 overall
This message was automatically generated. |
abhishek-chouhan
commented
Jul 20, 2021
Have we looked at the scanId that we already have in BaseResultIterators? Seems to be scarcely used. However, we would want to have a single notion of a queryId, unless needed otherwise. It also looks like the clients need to set this explicitly? Ideally we would not want the clients going through the internal implementations of phoenix (PhoenixStatement and their derivates in this case). Having phoenix generate the queryId implicitly makes more sense IMO. The notion also seems useful not only for tracing but also for debugging. At the moment, logging in phoenix is scattered and hard to correlate with the actual query. @ArkenKiran |
Merge latest 4.16
No description provided.