[HIVE-20726] The hive.server2.thrift.bind.host is not honored after changing in Hive 2.3.3

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Labels: pull-request-available

Environment

AWS Centos 7 machine with custom installed Hive 2.3.3/Hadoop 2.9.0 and Tez 0.8.5

• Assignee: Denys Kuzmenko
• Reporter: Vignesh Sankaran
• Created: 11/Oct/18 12:01
• Updated: 07/Jan/21 19:18
• Resolved: 07/Jan/21 19:15

Description

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.

Issue Links

• is broken by: HIVE-12568 Provide an option to specify network interface used by Spark remote client [Spark Branch]
• links to: GitHub Pull Request #1773