[
https://issues.apache.org/jira/browse/HUDI-9708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Danny Chen updated HUDI-9708:
-----------------------------
Description:
MIT is upsert semantics overall, it should always use `UPSERT` operation.
related fix that seems not right:
https://issues.apache.org/jira/browse/HUDI-4946
> I think merge into for the same table need has consistent behavior.
This is corrent but the fix does not make sense, it does not duplicate when
there is no matched row, MIT should always use `UPSERT` operation, the incoming
data set should always be dedupped, that is how to keep consistent with MIT
that has matched rows.
was:MIT is upsert semantics overall, it should always use `UPSERT` operation.
related fix that seems not right:
https://issues.apache.org/jira/browse/HUDI-4946
> Fix MIT to deduplicate for incoming records when ordering field is missing
> --------------------------------------------------------------------------
>
> Key: HUDI-9708
> URL: https://issues.apache.org/jira/browse/HUDI-9708
> Project: Apache Hudi
> Issue Type: Improvement
> Components: writer-core
> Reporter: Danny Chen
> Priority: Major
>
> MIT is upsert semantics overall, it should always use `UPSERT` operation.
> related fix that seems not right:
> https://issues.apache.org/jira/browse/HUDI-4946
> > I think merge into for the same table need has consistent behavior.
> This is corrent but the fix does not make sense, it does not duplicate when
> there is no matched row, MIT should always use `UPSERT` operation, the
> incoming data set should always be dedupped, that is how to keep consistent
> with MIT that has matched rows.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
