Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
ghx-label-10
Description
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.
Attachments
Issue Links
- is related to
-
IMPALA-11265 Iceberg tables have a large memory footprint in catalog cache
- Open