[
https://issues.apache.org/jira/browse/IMPALA-8635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon resolved IMPALA-8635.
---------------------------------
Resolution: Fixed
Fix Version/s: Impala 3.3.0
> 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
> Priority: Blocker
> Fix For: Impala 3.3.0
>
>
> 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)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
