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 "ASF subversion and git services (Jira)" <ji...@apache.org> on 2025/01/21 08:48:00 UTC
[jira] [Commented] (IMPALA-13674) MERGE statement targeting Iceberg tables with equality deletes runs on DCHECK
[ https://issues.apache.org/jira/browse/IMPALA-13674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17914896#comment-17914896 ]
ASF subversion and git services commented on IMPALA-13674:
----------------------------------------------------------
Commit d1a0c2ac14ae65263691f277be839ef23bf33bf7 in impala's branch refs/heads/master from Peter Rozsa
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=d1a0c2ac1 ]
IMPALA-13205: Do not include Iceberg position fields for MERGE statements with INSERT merge clauses
This patch makes the Iceberg position field inclusion conditional by
including them only if there are UPDATE or DELETE merge clauses that are
listed in a MERGE statement or the target table has existing delete
files. These fields can be omitted when there's no delete file creation
at the sink of the MERGE statement and the table has no existing delete
files.
Additionally, this change disables MERGE for Iceberg target tables
that contain equality delete files, see IMPALA-13674.
Tests:
- iceberg-merge-insert-only planner test added
Change-Id: Ib62c78dab557625fa86988559b3732591755106f
Reviewed-on: http://gerrit.cloudera.org:8080/21931
Reviewed-by: Noemi Pap-Takacs <np...@cloudera.com>
Reviewed-by: Daniel Becker <da...@cloudera.com>
Tested-by: Impala Public Jenkins <im...@cloudera.com>
> MERGE statement targeting Iceberg tables with equality deletes runs on DCHECK
> -----------------------------------------------------------------------------
>
> Key: IMPALA-13674
> URL: https://issues.apache.org/jira/browse/IMPALA-13674
> Project: IMPALA
> Issue Type: Bug
> Reporter: Peter Rozsa
> Assignee: Peter Rozsa
> Priority: Major
>
> Iceberg tables with equality deletes include one additional field implicitly (data sequence number), this causes invalid materialization in the MergeNode, as its tuple descriptor's size mismatches the size of the evaluators.
--
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