You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Zoltán Borók-Nagy (Jira)" <ji...@apache.org> on 2022/11/14 16:12:00 UTC

[jira] [Created] (IMPALA-11723) Use separate cache in CatalogdMetaProvider for caching Iceberg table objects

Zoltán Borók-Nagy created IMPALA-11723:
------------------------------------------

             Summary: Use separate cache in CatalogdMetaProvider for caching Iceberg table objects
                 Key: IMPALA-11723
                 URL: https://issues.apache.org/jira/browse/IMPALA-11723
             Project: IMPALA
          Issue Type: Bug
          Components: Catalog, Frontend
            Reporter: Zoltán Borók-Nagy


Iceberg table objects can be very large. Currently they are being stored in the meta provider's cache with other metadata objects. We load them by the 
MetaProvider.loadIcebergApiTable() method.
Probably we should evict them more often, especially if the table is updated in CatalogD.

It would make sense to store them in a separate cache.



--
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