[
https://issues.apache.org/jira/browse/HIVE-22712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17015144#comment-17015144
]
Zoltan Haindrich commented on HIVE-22712:
-----------------------------------------
I never expected an [unset like
this|https://github.com/apache/hive/blob/1f541b52314519e206dcb0f1aa2ebceb8e44d7a6/ql/src/java/org/apache/hadoop/hive/ql/exec/tez/TezSessionState.java#L473-L481]
....fixing the immutabiliy of the HiveConf is longer term goal - and it's very
hard to achieve...
this quick fix will hold until we get to that...
+1
to make sure that we don't lose this fix: could you please add the following
test to 'retry_failure.q'?
{code}
-- HIVE-22712
set hive.fetch.task.conversion=none;
set tez.queue.name=default;
select assert_true(${hiveconf:zzz} > a),
assert_true("${hiveconf:tez.queue.name}" = 'default') from tx_n1;
{code}
> ReExec Driver execute submit the query in default queue irrespective of user
> defined queue
> ------------------------------------------------------------------------------------------
>
> Key: HIVE-22712
> URL: https://issues.apache.org/jira/browse/HIVE-22712
> Project: Hive
> Issue Type: Bug
> Components: Hive, HiveServer2
> Affects Versions: 3.1.2
> Environment: Hive-3
> Reporter: Rajkumar Singh
> Assignee: Rajkumar Singh
> Priority: Major
> Attachments: HIVE-22712.01.patch, HIVE-22712.02.patch,
> HIVE-22712.patch
>
>
> we unset the queue name intentionally in
> TezSessionState#startSessionAndContainers,
> as a result reexec create a new session in the default queue and create a
> problem, its a cumbersome to add reexec.overlay.tez.queue.name at session
> level.
> I could not find a better way of setting the queue name (I am open for the
> suggestion here) since it can create a conflict with the Global queue name
> vs user-defined queue that's why setting while initialization of
> ReExecutionOverlayPlugin.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
