hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chance Zibolski (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-20726) The hive.server2.thrift.bind.host is not honored after changing in Hive 2.3.3
Date Mon, 22 Jul 2019 22:59:00 GMT

    [ https://issues.apache.org/jira/browse/HIVE-20726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16890526#comment-16890526
] 

Chance Zibolski commented on HIVE-20726:
----------------------------------------

So that's introduced via HIVE-12568

> 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)

Mime
View raw message