[
https://issues.apache.org/jira/browse/IMPALA-14496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18030163#comment-18030163
]
ASF subversion and git services commented on IMPALA-14496:
----------------------------------------------------------
Commit bfae4d0b32dfb035495831f003f30b2d336d1ec6 in impala's branch
refs/heads/master from Zoltan Borok-Nagy
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=bfae4d0b3 ]
IMPALA-14496: Impala crashes when it writes multiple delete files per partition
in a single DELETE operation
Impala crashes when it needs to write multiple delete files per
partition in a single DELETE operation. It is because
IcebergBufferedDeleteSink has its own DmlExecState object, but
sometimes the methods in TableSinkBase use the RuntimeState's
DmlExecState object. I.e. it can happen that we add a partition
to the IcebergBufferedDeleteSink's DmlExecState, but later we
expect to find it in the RuntimeState's DmlExecState.
This patch adds new methods to TableSinkBase that are specific
for writing delete files, and they always take a DmlExecState
object as a parameter. They are now used by IcebergBufferedDeleteSink.
Testing
* added e2e tests
Change-Id: I46266007a6356e9ff3b63369dd855aff1396bb72
Reviewed-on: http://gerrit.cloudera.org:8080/23537
Reviewed-by: Mihaly Szjatinya <[email protected]>
Reviewed-by: Michael Smith <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> Impala crashes when it writes multiple delete files per partition in a single
> DELETE operation
> ----------------------------------------------------------------------------------------------
>
> Key: IMPALA-14496
> URL: https://issues.apache.org/jira/browse/IMPALA-14496
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
> Affects Versions: Impala 4.4.0
> Reporter: Zoltán Borók-Nagy
> Assignee: Zoltán Borók-Nagy
> Priority: Major
> Labels: impala-iceberg
> Fix For: Impala 5.0.0
>
>
> Impala crashes when it needs to write multiple delete files per partition in
> a single DELETE operation.
> It is because IcebergBufferedDeleteSink has its own DmlExecState object, but
> sometimes the methods in TableSinkBase use the RuntimeState's DmlExecState
> object.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]