[
https://issues.apache.org/jira/browse/HIVE-18238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16310180#comment-16310180
]
Sahil Takiar commented on HIVE-18238:
-------------------------------------
[~kgyrtkirk] I think there are some users who are expecting
{{hive.query.string}} to be set to the last executed query. Although, that gets
a bit murky when there are queries being run in the same session in parallel.
https://www.quora.com/How-do-I-get-the-Hive-query-statement-that-I-have-executed-in-Yarn
https://mail-archives.apache.org/mod_mbox/hive-user/201312.mbox/%3c068f8f823eee4b379e6346a919d05...@blupr08mb296.namprd08.prod.outlook.com%3E
> Driver execution may not have configuration changing sideeffects
> -----------------------------------------------------------------
>
> Key: HIVE-18238
> URL: https://issues.apache.org/jira/browse/HIVE-18238
> Project: Hive
> Issue Type: Sub-task
> Components: Logical Optimizer
> Reporter: Zoltan Haindrich
> Assignee: Zoltan Haindrich
> Attachments: HIVE-18238.01wip01.patch, HIVE-18238.02.patch,
> HIVE-18238.03.patch
>
>
> {{Driver}} executes sql statements which use "hiveconf" settings;
> but the {{Driver}} itself may *not* change the configuration...
> I've found an example; which shows how hazardous this is...
> {code}
> set hive.mapred.mode=strict;
> select "${hiveconf:hive.mapred.mode}";
> create table t (a int);
> analyze table t compute statistics;
> select "${hiveconf:hive.mapred.mode}";
> {code}
> currently; the last select returns {{nonstrict}} because of
> [this|https://github.com/apache/hive/blob/7ddd915bf82a68c8ab73b0c4ca409f1a6d43d227/ql/src/java/org/apache/hadoop/hive/ql/parse/SemanticAnalyzer.java#L1696]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
