[
https://issues.apache.org/jira/browse/HUDI-8876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lin Liu updated HUDI-8876:
--------------------------
Description:
{{`HoodieRecordUtil.createRecordMerger`}} falls back to
`{{{}HoodieAvroRecordMerger`{}}} without considering merger mode. However,
`{{{}HoodieTableConfig.inferCorrectMergingBehavior`{}}} behaviors differently.
That is, if the merge strategy id is given, it could use `{{{}Commit time
based`{}}} payload class, which may contradict with the merger selection logic
of `{{{}HoodieRecordUtil`{}}} . What is why sometimes we see there are
inconsistent merging behavior. Since the behavior of
`{{{}HoodieRecordUtil.createRecordMerger`{}}} affects MDT behavior, we need to
update the `{{{}HoodieTableConfig.inferCorrectMergingBehavior`{}}} accordingly.
This issue may not impact broadly since this is a corner case.
was:{{`HoodieRecordUtil.createRecordMerger`}} falls back to
`{{{}HoodieAvroRecordMerger`{}}} without considering merger mode. However,
`{{{}HoodieTableConfig.inferCorrectMergingBehavior`{}}} behaviors differently.
That is, if the merge strategy id is given, it could use `{{{}Commit time
based`{}}} payload class, which may contradict with the merger selection logic
of `{{{}HoodieRecordUtil`{}}} . What is why sometimes we see there are
inconsistent merging behavior. Since the behavior of
`{{{}HoodieRecordUtil.createRecordMerger`{}}} affects MDT behavior, we need to
update the `{{{}HoodieTableConfig.inferCorrectMergingBehavior`{}}} accordingly.
> Make merger and payload class be consisent
> ------------------------------------------
>
> Key: HUDI-8876
> URL: https://issues.apache.org/jira/browse/HUDI-8876
> Project: Apache Hudi
> Issue Type: Bug
> Affects Versions: 1.2.0
> Reporter: Lin Liu
> Assignee: Lin Liu
> Priority: Major
>
> {{`HoodieRecordUtil.createRecordMerger`}} falls back to
> `{{{}HoodieAvroRecordMerger`{}}} without considering merger mode. However,
> `{{{}HoodieTableConfig.inferCorrectMergingBehavior`{}}} behaviors
> differently. That is, if the merge strategy id is given, it could use
> `{{{}Commit time based`{}}} payload class, which may contradict with the
> merger selection logic of `{{{}HoodieRecordUtil`{}}} . What is why sometimes
> we see there are inconsistent merging behavior. Since the behavior of
> `{{{}HoodieRecordUtil.createRecordMerger`{}}} affects MDT behavior, we need
> to update the `{{{}HoodieTableConfig.inferCorrectMergingBehavior`{}}}
> accordingly.
>
> This issue may not impact broadly since this is a corner case.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
