[
https://issues.apache.org/jira/browse/IMPALA-15309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18109007#comment-18109007
]
ASF subversion and git services commented on IMPALA-15309:
----------------------------------------------------------
Commit c8e5eec7ecb08a446418506c9b30e100ac7a6e60 in impala's branch
refs/heads/master from Aleksandr Efimov
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=c8e5eec7e ]
IMPALA-15309: Guard DML with table UUID
Carry the planning-time Iceberg table UUID through DML
finalization and verify it before CatalogD applies the operation.
This prevents a request planned for a dropped table from being
committed to a different table recreated with the same name.
Keep the field optional for rolling compatibility. CTAS and
Iceberg Table implementations without UUID support retain the
existing behavior.
Testing:
- IcebergCatalogOpExecutorTest
- IcebergDmlFinalizerTest
- Thrift parser; Java, impalad, catalogd and statestored builds
- Focused Iceberg DML, CTAS, cleanup and table-recreate race tests
Change-Id: I375a21a61e3ed588aab0590341b9c20469def6a9
Assisted-by: gpt-5.6-sol (OpenAI Codex)
Reviewed-on: http://gerrit.cloudera.org:8080/24735
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> Verify the Iceberg table UUID before applying a DML operation
> -------------------------------------------------------------
>
> Key: IMPALA-15309
> URL: https://issues.apache.org/jira/browse/IMPALA-15309
> Project: IMPALA
> Issue Type: Sub-task
> Components: Catalog, Frontend
> Reporter: Aleksandr Efimov
> Assignee: Aleksandr Efimov
> Priority: Major
> Labels: impala-iceberg
>
> A DML request identifies its target table by name. If the table is dropped
> and recreated under the same name between planning and finalization, the
> request is applied to the new table.
> Record the Iceberg table UUID during planning in TIcebergDmlFinalizeParams
> and compare it against the loaded table before the operation is applied. The
> field is optional, so a coordinator that does not send it keeps working
> during a rolling upgrade. CTAS targets have no Iceberg API table at planning
> time, and Table implementations that do not implement uuid() leave the field
> unset; both keep their current behavior.
> Prerequisite for INSERT INTO on REST catalog tables.
> Review: https://gerrit.cloudera.org/#/c/24735/
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
