[
https://issues.apache.org/jira/browse/HIVE-6325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13901315#comment-13901315
]
Rajesh Balamohan commented on HIVE-6325:
----------------------------------------
>>>
if (!session.isDefault()) {
if
(existingConf.get("tez.queue.name").compareTo(conf.get("tez.queue.name")) != 0)
{
return false;
}
} else {
// this session should never be a default session unless something has
messed up.
throw new HiveException("Default queue should always be returned. Hence we
should not be here.");
}
>>>
There is a possibility of "existingConf.get("tez.queue.name")" throwing NPE
when HIVE_SERVER2_TEZ_INITIALIZE_DEFAULT_SESSIONS is not set.
"tez.queue.name" is set in the conf in startPool() which is internally called
by HS2 when we enable "HIVE_SERVER2_TEZ_INITIALIZE_DEFAULT_SESSIONS". If it is
not enabled, HS2 will not call startPool(); And apparently
"existingConf.get("tez.queue.name")" can throw NPE.
> Enable using multiple concurrent sessions in tez
> ------------------------------------------------
>
> Key: HIVE-6325
> URL: https://issues.apache.org/jira/browse/HIVE-6325
> Project: Hive
> Issue Type: Improvement
> Components: Tez
> Affects Versions: 0.13.0
> Reporter: Vikram Dixit K
> Assignee: Vikram Dixit K
> Attachments: HIVE-6325.1.patch, HIVE-6325.2.patch, HIVE-6325.3.patch,
> HIVE-6325.4.patch, HIVE-6325.5.patch
>
>
> We would like to enable multiple concurrent sessions in tez via hive server
> 2. This will enable users to make efficient use of the cluster when it has
> been partitioned using yarn queues.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
