[fix](schema-change) Use actual schema change alter version in cloud capture#62506
Open
Hastyshell wants to merge 2 commits intoapache:masterfrom
Open
[fix](schema-change) Use actual schema change alter version in cloud capture#62506Hastyshell wants to merge 2 commits intoapache:masterfrom
Hastyshell wants to merge 2 commits intoapache:masterfrom
Conversation
### What problem does this PR solve? Issue Number: None Related PR: None Problem Summary: Cloud schema change may register an alter_version greater than the FE task's original visible version. When the task is created at version 1 but starts after new versions arrive, BE can skip capturing historical rowsets and later commit an empty schema change output. ### Release note None ### Check List (For Author) - Test: No need to test (small condition fix; not run in this session) - Behavior changed: Yes (cloud schema change now captures historical rowsets using the registered alter_version to avoid empty output on schema change races) - Does this need documentation: No
Contributor
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
Hastyshell
changed the title
gavinchou
previously approved these changes
Apr 15, 2026
Contributor
|
PR approved by at least one committer and no changes requested. |
github-actions
bot
added
the
approved
Contributor
|
PR approved by anyone and no changes requested. |
### What problem does this PR solve? Issue Number: None Related PR: None Problem Summary: Add a cloud regression test for the inverted index schema change race where FE creates the alter task at version 1 but BE registers a later alter_version after new data is published. Also document why cloud schema change must use the meta-service alter_version when deciding whether to capture historical rowsets. ### Release note None ### Check List (For Author) - Test: No need to test (regression case added but not run in this session) - Behavior changed: No - Does this need documentation: No
Collaborator
Author
|
run buildall |
github-actions
bot
removed
the
approved
Contributor
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
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
4 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 problem does this PR solve?
Issue Number: None
Related PR: None
Problem Summary:
Cloud schema change in BE decides whether to capture historical rowsets using the original FE task alter version, but later executes and commits using the alter version registered in meta service. When the FE task is created at version 1 and the registered schema change job uses a later alter version, BE can skip capturing historical rowsets and then commit an empty schema change output.
This change uses the registered schema change alter version consistently when deciding whether historical rowsets need to be captured.
Release note
None
Check List (For Author)
Test
- Small conditional fix in cloud schema change capture logic only; no test was run in this session.
Behavior changed:
- Cloud schema change now decides whether to capture historical rowsets using the alter version registered in meta service, avoiding empty schema change output in the version-1 to later-version race.
Does this need documentation?
Check List (For Reviewer who merge this PR)