[hotfix][runtime Preserve original failure during distributed schema evolution - #4556
Merged
Merged
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
3 participants
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.
What is the purpose of this pull request?
During distributed schema evolution, when a sink subtask fails while the coordinator is in the
EVOLVINGstate, the coordinator is left in an inconsistent state.This PR makes the distributed
SchemaCoordinatorpreserve the first failure observed during an in-progress schema evolution and re-throw that original cause.Verifying this change
Unit tests / IT cases are included.
Documentation
Was generative AI tooling used to co-author this PR?
Generated-by: OpenAI Codex (gpt-5.6-sol)