[
https://issues.apache.org/jira/browse/HUDI-7612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17903464#comment-17903464
]
Lin Liu commented on HUDI-7612:
-------------------------------
I revisited the logic. The most delete records do not have ordering field. In
this case, we fall back to natural ordering, i.e., t he ordering field is 0. In
his case, we can compare delete records, with non-delete records. When we
compare delete and delete records, we still need to fall back to
COMMIT_TiME_ORDERING.
This should be the most natural way to handle delete now.
> HoodieSparkRecordMerger does not handle deletes based on the
> preCombine/ordering field
> --------------------------------------------------------------------------------------
>
> Key: HUDI-7612
> URL: https://issues.apache.org/jira/browse/HUDI-7612
> Project: Apache Hudi
> Issue Type: Bug
> Components: spark
> Reporter: Jonathan Vexler
> Assignee: Lin Liu
> Priority: Blocker
> Fix For: 1.0.1
>
>
> The merger handles deletes based off of overwrite with latest. But the rest
> of the logic is like default payload
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
