You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Chance Zibolski (JIRA)" <ji...@apache.org> on 2019/07/10 21:14:00 UTC
[jira] [Commented] (HIVE-20726) The hive.server2.thrift.bind.host
is not honored after changing in Hive 2.3.3
[ https://issues.apache.org/jira/browse/HIVE-20726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16882453#comment-16882453 ]
Chance Zibolski commented on HIVE-20726:
----------------------------------------
I'm also seeing this. Setting the property in hive-site.xml, and setting the HIVE_SERVER2_THRIFT_BIND_HOST env var, neither work.
> 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.3#76005)