You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Attila Magyar (Jira)" <ji...@apache.org> on 2019/10/15 14:03:00 UTC
[jira] [Resolved] (AMBARI-22863) Hive should handle a customized
Zookeeper service principal name
[ https://issues.apache.org/jira/browse/AMBARI-22863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Attila Magyar resolved AMBARI-22863.
------------------------------------
Resolution: Fixed
> Hive should handle a customized Zookeeper service principal name
> ----------------------------------------------------------------
>
> Key: AMBARI-22863
> URL: https://issues.apache.org/jira/browse/AMBARI-22863
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
> Affects Versions: 2.0.0
> Reporter: Sandor Molnar
> Assignee: Attila Magyar
> Priority: Critical
> Labels: kerberos, pull-request-available
> Fix For: 3.0.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Hive should handle a customized Zookeeper service principal name.
> Currently this is not supported due to hardcoded and implicit values expecting the Zookeeper service principal name to be {{zookeeper/_HOST}} as opposed to something like {{zookeeper-mycluster/_HOST}}.
> The following changes need to be made:
> * {{-Dzookeeper.sasl.client.username=<ZOOKEEPER_PRINCPAL_NAME>}} should be added to {{HIVE_OPTS}}
> * Other changes may be needed to handle Hive-related tool and JDBC/ODBC implementations
--
This message was sent by Atlassian Jira
(v8.3.4#803005)