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

Posted to issues@impala.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2019/06/07 06:42:00 UTC

[jira] [Created] (IMPALA-8635) Kudu HMS integration check should not fetch metastore URIs configuration from metastore

Todd Lipcon created IMPALA-8635:
-----------------------------------

             Summary: Kudu HMS integration check should not fetch metastore URIs configuration from metastore
                 Key: IMPALA-8635
                 URL: https://issues.apache.org/jira/browse/IMPALA-8635
             Project: IMPALA
          Issue Type: Bug
          Components: Catalog
    Affects Versions: Impala 3.3.0
            Reporter: Todd Lipcon
            Assignee: Todd Lipcon


The patch for IMPALA-8504 (part 2) (6bb404dc359) checks to see if Impala and Kudu are configured against the same metastore to determine if the HMS integration is enabled. However, instead of using its own metastore URI config, it uses the configuration stored on the remote HMS. This is error prone because it's not common for the HMS configuration to store its own URI. Instead, we should use our own config, and our fallback should conservatively assume the legacy behavior.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)