[ 
https://issues.apache.org/jira/browse/IMPALA-9375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17803299#comment-17803299
 ] 

ASF subversion and git services commented on IMPALA-9375:
---------------------------------------------------------

Commit 142ae261e319c3b602128deb1329713d5253637d in impala's branch 
refs/heads/master from Venu Reddy
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=142ae261e ]

IMPALA-9375: Remove DirectMetaProvider usage from CatalogMetaProvider

This commit removes the CatalogMetaProvider dependence on
DirectMetaProvider. CatalogMetaProvider depends on DirectMetaProvider
for 2 APIs. Implemented the APIs on catalog server and used them
instead. DirectMetaProvider is not referenced anywhere now. But it is
retained for future use.

Testing:
- Manually tested and CatalogdMetaProviderTest covers the tests.

Change-Id: I096c1b1d1a52e979c8b2d8173dae9ca2cc6c36d2
Reviewed-on: http://gerrit.cloudera.org:8080/20791
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>


> 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to