[
https://issues.apache.org/jira/browse/HIVE-29815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18113395#comment-18113395
]
Ayush Saxena commented on HIVE-29815:
-------------------------------------
Committed to master.
Thanx [~Aggarwal_Raghav] for the contribution, [~kokila19] & [~tanishqchugh]
for the reviews!!!
> Iceberg: [V3] Support ROW LINEAGE in Copy-On-Write DELETE operations
> --------------------------------------------------------------------
>
> Key: HIVE-29815
> URL: https://issues.apache.org/jira/browse/HIVE-29815
> Project: Hive
> Issue Type: Improvement
> Reporter: Raghav Aggarwal
> Assignee: Raghav Aggarwal
> Priority: Major
> Labels: pull-request-available
>
> In HIVE-29445, support for Iceberg V3 Row Lineage (ROW_{_}LINEAGE{_}{_}ID and
> LAST__{_}{_}UPDATED__{_}{_}SEQUENCE{_}__NUMBER) was introduced to track CDC
> mutations across INSERT, UPDATE, and MERGE operations.
> However, support was missed for *DELETE* operations when the table is
> explicitly configured with _'write.delete.mode'='copy-on-write'_
>
> *This completely breaks CDC downstream. When a single row is deleted using
> Copy-On-Write, Iceberg rewrites the entire file to remove that row. Because
> the lineage IDs of the surviving rows are not preserved during this rewrite,
> they are all assigned brand new lineage IDs and new sequence numbers.*
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
