[
https://issues.apache.org/jira/browse/IMPALA-14892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18074202#comment-18074202
]
Zoltán Borók-Nagy commented on IMPALA-14892:
--------------------------------------------
Can we assume that all MetaProvider have their own TableMetaRefImpl? That way
MetaProviders can reject other TableMetaRefs.
> MultiMetaProvider abstraction looks wrong for table loaders
> -----------------------------------------------------------
>
> Key: IMPALA-14892
> URL: https://issues.apache.org/jira/browse/IMPALA-14892
> Project: IMPALA
> Issue Type: Improvement
> Components: Catalog, Frontend
> Reporter: Csaba Ringhofer
> Priority: Major
>
> MultiMetaProvider iterates through a list of MetaProviders in each function
> until one returns the requested object. This is ok for db/table discovery but
> not when loading a part of a table, e.g. a partition, which should always
> come from the same MetaProvider as the root of the table.
> Example:
> https://github.com/apache/impala/blob/49ddba704f1eec308d276f9568e7564918677258/fe/src/main/java/org/apache/impala/catalog/local/MultiMetaProvider.java#L205
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
