[
https://issues.apache.org/jira/browse/HIVE-10093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Szehon Ho updated HIVE-10093:
-----------------------------
Description:
When the HiveAuthFactory is constructed in HS2, it initializes a HMSHandler
unnecessarily right before the call to:
HadoopThriftAuthBridge.startDelegationTokenSecretManager(). If the
DelegationTokenStore is configured to be a memoryTokenStore, this step is not
needed.
Side effect is creation of useless derby database file on HiveServer2 in secure
clusters, causing confusion. This could potentially be skipped if
MemoryTokenStore is used.
was:
When the HiveAuthFactory is constructed in HS2, it initializes a HMSHandler
unnecessarily right before the call to:
HadoopThriftAuthBridge.startDelegationTokenSecretManager(). If the
DelegationTokenStore is configured to be a memoryTokenStore, this step is not
needed.
Side effect is creation of useless derby database file on HS2, causing
confusion. This could potentially be skipped if MemoryTokenStore is used.
> Unnecessary HMSHandler initialization for default MemoryTokenStore on HS2
> -------------------------------------------------------------------------
>
> Key: HIVE-10093
> URL: https://issues.apache.org/jira/browse/HIVE-10093
> Project: Hive
> Issue Type: Bug
> Reporter: Szehon Ho
> Priority: Minor
>
> When the HiveAuthFactory is constructed in HS2, it initializes a HMSHandler
> unnecessarily right before the call to:
> HadoopThriftAuthBridge.startDelegationTokenSecretManager(). If the
> DelegationTokenStore is configured to be a memoryTokenStore, this step is not
> needed.
> Side effect is creation of useless derby database file on HiveServer2 in
> secure clusters, causing confusion. This could potentially be skipped if
> MemoryTokenStore is used.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
