You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Gabor Kaszab (Jira)" <ji...@apache.org> on 2025/04/28 13:12:00 UTC

[jira] [Closed] (IMPALA-13673) Optimize JVM memory footprint of Iceberg tables in coordinator cache

     [ https://issues.apache.org/jira/browse/IMPALA-13673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gabor Kaszab closed IMPALA-13673.
---------------------------------
    Fix Version/s: Not Applicable
       Resolution: Duplicate

Taken care of by https://issues.apache.org/jira/browse/IMPALA-13737

> Optimize JVM memory footprint of Iceberg tables in coordinator cache
> --------------------------------------------------------------------
>
>                 Key: IMPALA-13673
>                 URL: https://issues.apache.org/jira/browse/IMPALA-13673
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Frontend
>            Reporter: Gabor Kaszab
>            Assignee: Gabor Kaszab
>            Priority: Major
>              Labels: impala-iceberg
>             Fix For: Not Applicable
>
>
> https://issues.apache.org/jira/browse/IMPALA-11265 takes care of the same for catalogd.
> In coordinator it seems that for Iceberg tables the file descriptors are cached twice. Once for the related HDFS table and once for the Iceberg table. As a solution, for the Iceberg table we should only take care of the Iceberg related part of the file descriptors, and when doing a fromThrift() conversion take the other part of the file descriptor from the Hdfs table.
> Ongoing PR for this: https://gerrit.cloudera.org/#/c/22216



--
This message was sent by Atlassian Jira
(v8.20.10#820010)