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

Posted to issues@hive.apache.org by "Denys Kuzmenko (Jira)" <ji...@apache.org> on 2021/01/07 19:19:00 UTC

[jira] [Comment Edited] (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=17260747#comment-17260747 ] 

Denys Kuzmenko edited comment on HIVE-20726 at 1/7/21, 7:18 PM:
----------------------------------------------------------------

Pushed to master.
[~lpinter] thank you for review!


was (Author: dkuzmenko):
Pushed to master.
[~lpinter] thank you for the review!

> 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
>            Assignee: Denys Kuzmenko
>            Priority: Critical
>              Labels: pull-request-available
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> 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
(v8.3.4#803005)