rangareddy commented on issue #17286: URL: https://github.com/apache/hudi/issues/17286#issuecomment-5365814356
This issue was reviewed as part of the JIRA-migrated backlog triage (HUDI-8424). **Findings: no such tool or config exists on `master`.** The only way to change merge configuration on an existing table today is the generic `table update-configs` CLI command (`hudi-cli/src/main/java/org/apache/hudi/cli/commands/TableCommand.java:226`), which calls `HoodieTableConfig.update()` - a raw property upsert. It performs no reconciliation and no validation, so it will not recompute `hoodie.record.merge.strategy.id` for the new payload class or merge mode (tracked separately as #17336 / HUDI-8702) and will not reject an incoherent combination. **Worth resolving a tension across tickets before this is built.** Two sibling issues ask for the opposite of this one: - #17295 (HUDI-8418) - throw an error if record-merge table configs are about to change - #17339 (HUDI-8731) - forbid merge mode change in table config This ticket asks for a sanctioned way to make precisely the change those want blocked. The coherent design is probably "blocked on the ordinary write path, permitted only through this migration tool, which validates the target combination and rewrites every derived config together" - but that needs stating explicitly, otherwise whichever ticket is implemented first will make the other look wrong. Keeping this open. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
