You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hive.apache.org by "Vignesh Sankaran (JIRA)" <ji...@apache.org> on 2018/10/11 12:02:00 UTC

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

Vignesh Sankaran created HIVE-20726:
---------------------------------------

             Summary: 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


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.3#76005)