hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aihua Xu (JIRA)" <>
Subject [jira] [Commented] (HIVE-13286) Query ID is being reused across queries
Date Tue, 15 Mar 2016 19:05:33 GMT


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?
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.

> Query ID is being reused across queries
> ---------------------------------------
>                 Key: HIVE-13286
>                 URL:
>             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

View raw message