[
https://issues.apache.org/jira/browse/HIVE-13286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15195987#comment-15195987
]
Aihua Xu commented on HIVE-13286:
---------------------------------
Actually what I need is the unique queryId. Think of the scenario that hive is
just one of the components in the pipeline. The client could have a queryId
(e.g., to trace the generation of the query) and then call hive. Then such
queryId can link them together and better for diagnosis. If we create other
ids, then seems to defeat that purpose.
If the user doesn't provide queryId, then Hive will take care of that. Is the
following the actual issue you see?
{nformat}
I think there is an issue there. confOverlay is passed from the client. Seems
we need to make a copy of that otherwise if the client reuses the same
confOverlay, then queryId is reused. Is that the issue? I will correct that.
{noformat}
> Query ID is being reused across queries
> ---------------------------------------
>
> Key: HIVE-13286
> URL: https://issues.apache.org/jira/browse/HIVE-13286
> Project: Hive
> Issue Type: Bug
> Components: Parser
> Affects Versions: 2.0.0
> Reporter: Vikram Dixit K
> Assignee: Aihua Xu
> Priority: Critical
>
> [~aihuaxu] I see this commit made via HIVE-11488. I see that query id is
> being reused across queries. This defeats the purpose of a query id. I am not
> sure what the purpose of the change in that jira is but it breaks the
> assumption about a query id being unique for each query. Please take a look
> into this at the earliest.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
