[
https://issues.apache.org/jira/browse/HIVE-20726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16890521#comment-16890521
]
Chance Zibolski commented on HIVE-20726:
----------------------------------------
I've diagnosed the issue to
[https://github.com/apache/hive/blob/rel/release-2.3.5/service/src/java/org/apache/hive/service/cli/thrift/ThriftCLIService.java#L168]
The problem is this declaration of hiveHost shadows the class variable hiveHost.
Additionally, I believe i found a potential problem in
[https://github.com/apache/hive/blob/rel/release-2.3.5/service/src/java/org/apache/hive/service/server/HiveServer2.java#L145]
because this overrides the bind host value. It seems this only exists to
enable zookeeper discovery, but a better approach would be to have a second
option for the hostname to publish, rather than using bindhost for it.
> The hive.server2.thrift.bind.host is not honored after changing in Hive 2.3.3
> -----------------------------------------------------------------------------
>
> Key: HIVE-20726
> URL: https://issues.apache.org/jira/browse/HIVE-20726
> Project: Hive
> Issue Type: Bug
> Environment: AWS Centos 7 machine with custom installed Hive
> 2.3.3/Hadoop 2.9.0 and Tez 0.8.5
> Reporter: Vignesh Sankaran
> Priority: Critical
>
> The hive.server2.thrift.bind.host property was set to a custom IP where Hive
> 2.3.3 is setup and also the hive.server2.transport.mode=binary was set. The
> change is not at all being honored and the server starts to listen on
> 0.0.0.0:10002.
>
> I am unable to connect to the remote because of this using the JDBC client
> DBeaver.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
