[
https://issues.apache.org/jira/browse/IMPALA-13932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17943442#comment-17943442
]
ASF subversion and git services commented on IMPALA-13932:
----------------------------------------------------------
Commit 2849708b8701485637478ab6201b0780e80570ca in impala's branch
refs/heads/master from Zoltan Borok-Nagy
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=2849708b8 ]
IMPALA-13932: (addendum) Adds e2e test for IMPALA-13932
This patch adds e2e test for IMPALA-13932.
Change-Id: I07537b31717d568422ea042ad2aeef906b3cab2e
Reviewed-on: http://gerrit.cloudera.org:8080/22767
Reviewed-by: Peter Rozsa <[email protected]>
Reviewed-by: Daniel Becker <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> 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
> Fix For: Impala 5.0.0
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
