[
https://issues.apache.org/jira/browse/HUDI-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Danny Chen updated HUDI-2170:
-----------------------------
Description:
Now in {{OverwriteWithLatestAvroPayload.preCombine}}, we still choose the old
record when the new record has the same preCombine field with the old one,
actually it is more natural to keep the new incoming record instead. The
{{DefaultHoodieRecordPayload.combineAndGetUpdateValue}} method already did that.
See issue: https://github.com/apache/hudi/issues/3266.
was:Now in {{OverwriteWithLatestAvroPayload.preCombine}}, we still choose the
old record when the new record has the same preCombine field with the old one,
actually it is more natural to keep the new incoming record instead. The
{{DefaultHoodieRecordPayload.combineAndGetUpdateValue}} method already did that.
> Always choose the latest record for HoodieRecordPayload
> -------------------------------------------------------
>
> Key: HUDI-2170
> URL: https://issues.apache.org/jira/browse/HUDI-2170
> Project: Apache Hudi
> Issue Type: Improvement
> Components: Common Core
> Reporter: Danny Chen
> Assignee: Danny Chen
> Priority: Major
> Fix For: 0.9.0
>
>
> Now in {{OverwriteWithLatestAvroPayload.preCombine}}, we still choose the old
> record when the new record has the same preCombine field with the old one,
> actually it is more natural to keep the new incoming record instead. The
> {{DefaultHoodieRecordPayload.combineAndGetUpdateValue}} method already did
> that.
> See issue: https://github.com/apache/hudi/issues/3266.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
