You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Vikram Dixit K (JIRA)" <ji...@apache.org> on 2016/03/15 02:13:33 UTC
[jira] [Commented] (HIVE-13286) Query ID is being reused across
queries
[ https://issues.apache.org/jira/browse/HIVE-13286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15194509#comment-15194509 ]
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.
{code}
+ 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);
+ }
{code}
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: 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)