Vihang Karajgaonkar created IMPALA-9375:
-------------------------------------------
Summary: Remove DirectMetaProvider usage from CatalogMetaProvider
Key: IMPALA-9375
URL: https://issues.apache.org/jira/browse/IMPALA-9375
Project: IMPALA
Issue Type: Improvement
Reporter: Vihang Karajgaonkar
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.3.4#803005)
