Repository navigation
[core] Commit independent Data Evolution compaction tasks on conflict - #10882
Draft
XiaoHongbo-Hope wants to merge 2 commits into
Draft
XiaoHongbo-Hope wants to merge 2 commits into
XiaoHongbo-Hope wants to merge 2 commits into
Conversation
This file contains hidden or 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
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.
Concurrent column updates can make one Data Evolution compaction task conflict and fail the entire batch. With
data-evolution.compaction.discard-conflicting-tasks=true(defaultfalse), the commit drops each conflicting task's complete input deletions and output additions, rechecks conflicts, and commits independent tasks. If all tasks conflict, it records an empty Compact snapshot for commit deduplication. Skipped inputs remain live; unreferenced outputs use the existing orphan-file cleanup path.This applies only to independent normal-data compaction tasks without index/changelog changes or row-ID validation baselines. Other conflicts retain the existing failure behavior.
Validation: 62 focused tests passed with standard Maven Checkstyle, Spotless, and Enforcer checks. Tests cover real compaction commits, concurrent updates, retries, shared inputs, row-ID reassignment, and exception serialization.