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 2025/04/10 12:03:00 UTC

[jira] [Work started] (IMPALA-13932) MERGE duplicate check reports false-positive if the incoming row batch's memory is reused

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

Work on IMPALA-13932 started by Peter Rozsa.
--------------------------------------------
> MERGE duplicate check reports false-positive if the incoming row batch's memory is reused
> -----------------------------------------------------------------------------------------
>
>                 Key: IMPALA-13932
>                 URL: https://issues.apache.org/jira/browse/IMPALA-13932
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Backend
>    Affects Versions: Impala 4.5.0
>            Reporter: Peter Rozsa
>            Assignee: Peter Rozsa
>            Priority: Critical
>              Labels: impala-iceberg
>
> The Iceberg merge node uses a duplicate check mechanism that compares the actual target row's pointer with the previous target row's pointer. If a new row batch's first target table's tuple points to the same region as the previous row, then we report a duplicate row erroneously.
> The duplicate check should be aware whether the merge join's probe batch is ended, and this case, resetting the incoming row batch would solve the problem.
>  



--
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