[ https://issues.apache.org/jira/browse/HIVE-18238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16307857#comment-16307857 ]
Zoltan Haindrich commented on HIVE-18238: ----------------------------------------- [~stakiar], [~janulatha]: HIVE-18166 added a test which clearly checks that a "sideffect" is being exposed...this ticket is currently breaking that case because that change is under the isolation level...so I would be intrested in that there users expecting to have {{hive.query.string}} set to the last executed query - or adding the that test case was just the easiest to check that {{hive.query.string}} is not encoded > 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 > > > {{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)