[ https://issues.apache.org/jira/browse/HIVE-20726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16890524#comment-16890524 ]
Chance Zibolski commented on HIVE-20726: ---------------------------------------- Seems that the change was introduced in [https://github.com/apache/hive/commit/9f57569b0f648bb5596df60e0a62db06930778ea], so apparently all the back in 2015. > 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)