[
https://issues.apache.org/jira/browse/IMPALA-11723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Boglarka Egyed updated IMPALA-11723:
------------------------------------
Priority: Minor (was: Major)
> 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
> Priority: Minor
> Labels: impala-iceberg, ramp-up
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
