[fix](cloud) Fix roll-backed cumulative point of new tablet when doing schema change #53402
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
Contributor
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
gavinchou
force-pushed
the
gavin-fix-new-tablet-compaction
branch
from
ec23295 to
8c40ce1
Compare
Contributor
Author
|
run buildall |
gavinchou
force-pushed
the
gavin-fix-new-tablet-compaction
branch
from
8c40ce1 to
7ab5e53
Compare
Contributor
Author
|
run buildall |
Contributor
|
PR approved by anyone and no changes requested. |
Cloud UT Coverage ReportIncrement line coverage Increment coverage report
|
Yukang-Lian
approved these changes
Jul 16, 2025
w41ter
approved these changes
Jul 17, 2025
github-actions
bot
added
the
approved
Contributor
|
PR approved by at least one committer and no changes requested. |
github-actions bot
pushed a commit
that referenced
this pull request
Jul 17, 2025
…g schema change (#53402) cumu point in job is from base tablet which may be fetched long time ago since the new tablet may have done cumu compactions with alter_version as initial cumu point current cumu point of new tablet may be larger than job.alter_version we need to keep the larger one in case of cumu point roll-back to break the basic assumptions of non-decreasing cumu point
github-actions bot
pushed a commit
that referenced
this pull request
Jul 17, 2025
…g schema change (#53402) cumu point in job is from base tablet which may be fetched long time ago since the new tablet may have done cumu compactions with alter_version as initial cumu point current cumu point of new tablet may be larger than job.alter_version we need to keep the larger one in case of cumu point roll-back to break the basic assumptions of non-decreasing cumu point
Hastyshell
pushed a commit
to Hastyshell/doris
that referenced
this pull request
Jul 21, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
8 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.
cumu point in job is from base tablet which may be fetched long time ago
since the new tablet may have done cumu compactions with alter_version as initial cumu point
current cumu point of new tablet may be larger than job.alter_version
we need to keep the larger one in case of cumu point roll-back to
break the basic assumptions of non-decreasing cumu point