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

Posted to issues@hive.apache.org by "Prasanth Jayachandran (Jira)" <ji...@apache.org> on 2022/01/19 21:28:00 UTC

[jira] [Resolved] (HIVE-25646) Thrift metastore URI reverse resolution could fail in some environments

     [ https://issues.apache.org/jira/browse/HIVE-25646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Prasanth Jayachandran resolved HIVE-25646.
------------------------------------------
    Fix Version/s: 3.2.0
                   4.0.0
       Resolution: Fixed

> Thrift metastore URI reverse resolution could fail in some environments
> -----------------------------------------------------------------------
>
>                 Key: HIVE-25646
>                 URL: https://issues.apache.org/jira/browse/HIVE-25646
>             Project: Hive
>          Issue Type: Bug
>          Components: Metastore
>    Affects Versions: 3.1.2, 4.0.0
>            Reporter: Prasanth Jayachandran
>            Assignee: Prasanth Jayachandran
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.2.0, 4.0.0
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> When custom URI resolver is not specified, the default thrift metastore URI goes through DNS reverse resolution (getCanonicalHostname) which is unlikely to resolve correctly when the HMS is sitting behind LBs and proxies. This is a change in behaviour from hive 2.x branch which isn't required. If reverse resolution is required, custom URI resolver can be implemented.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)