[jira] [Updated] (IMPALA-9375) Remove DirectMetaProvider usage from CatalogMetaProvider

["Daniel Becker (Jira)" <ji...@apache.org>]

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

Daniel Becker updated IMPALA-9375:
----------------------------------
    Target Version: Impala 4.3.0  (was: Impala 4.2.0)

> Remove DirectMetaProvider usage from CatalogMetaProvider
> --------------------------------------------------------
>
>                 Key: IMPALA-9375
>                 URL: https://issues.apache.org/jira/browse/IMPALA-9375
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Catalog
>    Affects Versions: Impala 3.4.0
>            Reporter: Vihang Karajgaonkar
>            Assignee: Vihang Karajgaonkar
>            Priority: Critical
>
> I see that CatalogMetaProvider uses {{DirectMetaProvider}} here https://github.com/apache/impala/blob/master/fe/src/main/java/org/apache/impala/catalog/local/CatalogdMetaProvider.java#L239
> There are only a couple of places where it is used within CatalogMetaProvider. We should implement those remaining APIs in catalog-v2 mode and remove the usage of DirectMetaProvider from CatalogMetaProvider. 
> DirectMetaProvider starts by default a MetastoreClientPool (with 10 connections). This is unnecessary given that catalog already makes the connections to HMS at its startup. It also slows down the coordinator startup time if there are HMS connection issues.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org