[jira] [Resolved] (IMPALA-11784) Don't call Iceberg's planFiles redundantly during table load

["Zoltán Borók-Nagy (Jira)" <ji...@apache.org>]

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

Zoltán Borók-Nagy resolved IMPALA-11784.
----------------------------------------
    Fix Version/s: Impala 4.3.0
       Resolution: Fixed

> Don't call Iceberg's planFiles redundantly during table load
> ------------------------------------------------------------
>
>                 Key: IMPALA-11784
>                 URL: https://issues.apache.org/jira/browse/IMPALA-11784
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Catalog
>            Reporter: Zoltán Borók-Nagy
>            Assignee: Zoltán Borók-Nagy
>            Priority: Major
>              Labels: impala-iceberg
>             Fix For: Impala 4.3.0
>
>
> Iceberg's planFiles() API is very expensive because it involves reading the Avro manifest files. It's especially expensive on object stores, though manifest caching can help here.
> Currently we invoke this API two times during table loading (via IcebergUtil.getIcebergFiles()), once in loadAllPartition() and once in loadPartitionStats().
> We should just invoke IcebergUtil.getIcebergFiles() once, then pass the result object to loadAllPartition() and loadPartitionStats().



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