You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "zuotingbing (Jira)" <ji...@apache.org> on 2020/02/26 07:00:01 UTC
[jira] [Updated] (HIVE-21410) find out the actual port number when
hive.server2.thrift.port=0
[ https://issues.apache.org/jira/browse/HIVE-21410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
zuotingbing updated HIVE-21410:
-------------------------------
Description:
Currently, if we set *hive.server2.thrift.port=0*, it hard to find out the actual port number which one we should use when using beeline to connect. Log the actual port number would help us to better get the correct connect uri.
before fixed:
!2019-03-08_163705.png!
after fixed:
!2019-03-08_163747.png!
was:
before fixed:
!2019-03-08_163705.png!
after fixed:
!2019-03-08_163747.png!
> find out the actual port number when hive.server2.thrift.port=0
> ---------------------------------------------------------------
>
> Key: HIVE-21410
> URL: https://issues.apache.org/jira/browse/HIVE-21410
> Project: Hive
> Issue Type: Improvement
> Reporter: zuotingbing
> Assignee: zuotingbing
> Priority: Minor
> Attachments: 2019-03-08_163705.png, 2019-03-08_163747.png, HIVE-21410.patch
>
>
> Currently, if we set *hive.server2.thrift.port=0*, it hard to find out the actual port number which one we should use when using beeline to connect. Log the actual port number would help us to better get the correct connect uri.
>
> before fixed:
> !2019-03-08_163705.png!
> after fixed:
> !2019-03-08_163747.png!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)