You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Peter Rozsa (Jira)" <ji...@apache.org> on 2026/06/12 09:35:00 UTC

[jira] [Resolved] (IMPALA-15065) Incorrect partition identification when removing deletion vectors from void-partitioned Iceberg tables

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

Peter Rozsa resolved IMPALA-15065.
----------------------------------
    Fix Version/s: Impala 5.0.0
       Resolution: Fixed

>  Incorrect partition identification when removing deletion vectors from void-partitioned Iceberg tables
> -------------------------------------------------------------------------------------------------------
>
>                 Key: IMPALA-15065
>                 URL: https://issues.apache.org/jira/browse/IMPALA-15065
>             Project: IMPALA
>          Issue Type: Sub-task
>            Reporter: Peter Rozsa
>            Assignee: Peter Rozsa
>            Priority: Major
>              Labels: impala-iceberg
>             Fix For: Impala 5.0.0
>
>
> When Impala removes an old DV via rowDelta.removeDeletes(), it passes a DeleteFile reconstructed from the C++ flatbuffer using FileMetadata.Builder. For tables whose partition spec is just a void transform (partitioned to unpartitioned evolution), FileMetadata.Builder produces partition() = null. The manifest-resident entry for the same DV was written with a non-null (empty) PartitionData. Iceberg's ManifestFilterManager.canContainAny() then fails to match the manifest.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org