[HUDI-8413] Change the default merge mode to COMMIT_TIME_ORDERING #12600
+172
−92
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
danny0405
reviewed
Jan 8, 2025
| @@ -198,7 +198,8 @@ public class HoodieTableConfig extends HoodieConfig { | |||
|
|
|||
| public static final ConfigProperty<RecordMergeMode> RECORD_MERGE_MODE = ConfigProperty | |||
| .key("hoodie.record.merge.mode") | |||
| .defaultValue(RecordMergeMode.EVENT_TIME_ORDERING) | |||
| .defaultValue((RecordMergeMode) null, | |||
| "COMMIT_TIME_ORDERING if precombine is not set; EVENT_TIME_ORDERING if precombine is set") | |||
There was a problem hiding this comment.
Can we simplify the logic in HoodieTableConfig.inferCorrectMergingBehavior ? It looks way too complicated.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Change Logs
Describe context and summary for this change. Highlight if any code was copied.
Impact
Describe any public API or user-facing feature change or any performance impact.
Risk level (write none, low medium or high below)
If medium or high, explain what verification was done to mitigate the risks.
Documentation Update
Describe any necessary documentation update if there is any new feature, config, or user-facing change. If not, put "none".
ticket number here and follow the instruction to make
changes to the website.
Contributor's checklist