Uploaded image for project: 'IMPALA'
  1. IMPALA
  2. IMPALA-11723

Use separate cache in CatalogdMetaProvider for caching Iceberg table objects

    XMLWordPrintableJSON

Details

    • 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

          Improvement - An improvement or enhancement to an existing feature or task. IMPALA-11265 Iceberg tables have a large memory footprint in catalog cache

          • Major - Major loss of function.
          • Open

          Activity

            People

              Unassigned Unassigned
              boroknagyz Zoltán Borók-Nagy
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated: