apache / apache/hudi

Correctly set the merge strategy id table config if payload class or merge mode is updated

Open
#17,336 1 comment 0 reactions 1 assignee Claimed by @nsivabalan View on GitHub
from-jira priority:critical type:devtask
Dominant language
Java
Stars
6.2k
Forks
2.5k
Avg merge
2d 8h
Merged PRs (30d)
111

Description

# Create a table, such as the one in quickstart, with default configurations. The table config will have DefaultHoodieRecordPayload as payload class and EVENT_TIME_ORDERING as merge mode, and merge strategy id is DEFAULT_MERGE_STRATEGY_UUID
# Then use hudi-cli to update the merge mode to COMMIT_TIME_ORDERING and payload class to OverwriteWithLatestPayload using `table update-configs` command. This will set the thw two configs but not update the merge strategy id. Given that merge strategy id is an internal implementation detail, it should be set automatically depending on merge mode and payload class.

## JIRA info

- Link: https://issues.apache.org/jira/browse/HUDI-8702
- Type: Sub-task
- Parent: https://issues.apache.org/jira/browse/HUDI-9106
- Fix version(s):
- 1.1.0

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.