deepakpanda93 commented on issue #15857: URL: https://github.com/apache/hudi/issues/15857#issuecomment-4892486558
This issue (and PR #8264, closed unmerged) asked to add a guard so that using multiple `update` actions in `MERGE INTO` cannot cause data-quality problems when the precombine/ordering field is not handled correctly (follow-up to PR #8133). Findings: that guard is present on current `master`. `MergeIntoHoodieTableCommand.checkUpdatingActions` validates that every update action sets the ordering (precombine) field when event-time ordering is enabled — throwing `MergeIntoFieldResolutionException` otherwise (`hudi-spark-datasource/hudi-spark3-common/.../command/MergeIntoHoodieTableCommand.scala`) — and warns when updates run without a precombine field. Earlier releases (0.14.0) already reject a merge whose precombine field cannot be resolved in the source table. Closing as fixed. If you can still trigger a data-quality issue with multiple update actions on a recent version, please reopen with a repro. -- 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]
