hive-issues mailing list archives

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


Vikram Dixit K commented on HIVE-13286:

I think it primarily comes down to this: the hive conf object once modified with a generated
query id, never resets the query id for a subsequent query.

+    String queryId = confOverlay.get(HiveConf.ConfVars.HIVEQUERYID.varname);
+    if (queryId == null || queryId.isEmpty()) {
+      queryId = QueryPlan.makeQueryId();
+      confOverlay.put(HiveConf.ConfVars.HIVEQUERYID.varname, queryId);
+      sessionState.getConf().setVar(HiveConf.ConfVars.HIVEQUERYID, queryId);
+    }

Once the query id has been set by a previous query, it never changes. This is incorrect behavior.
I am not sure about what the change was trying to do but this needs to get fixed. Thanks!

> 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