[
https://issues.apache.org/jira/browse/HUDI-7612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17911261#comment-17911261
]
Lin Liu commented on HUDI-7612:
-------------------------------
In HUDI-8840, we have made the delete behavior consistent across different
mergers/payloads, and fg reader. Therefore, this ticket is not needed anymore.
> 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: Sub-task
> Components: spark
> Reporter: Jonathan Vexler
> Assignee: Lin Liu
> Priority: Blocker
> Labels: pull-request-available
> 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)