-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BugFix] fix enable sync publish when clone #37398
Merged
Merged
Conversation
This file contains 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
luohaha
force-pushed
the
fix-sync-publish
branch
from
December 19, 2023 22:17
7caff6b
to
1c8708e
Compare
luohaha
changed the title
[Bugfix] fix enable sync publish when clone
[BugFix] fix enable sync publish when clone
Dec 19, 2023
sevev
previously approved these changes
Dec 20, 2023
decster
previously approved these changes
Dec 20, 2023
luohaha
force-pushed
the
fix-sync-publish
branch
from
December 20, 2023 04:13
1c8708e
to
c71eb9a
Compare
luohaha
force-pushed
the
fix-sync-publish
branch
from
December 20, 2023 18:24
c8447e3
to
f458678
Compare
Signed-off-by: luohaha <[email protected]>
luohaha
force-pushed
the
fix-sync-publish
branch
from
December 20, 2023 23:32
f458678
to
c97c2ca
Compare
sevev
previously approved these changes
Dec 21, 2023
Signed-off-by: luohaha <[email protected]>
luohaha
force-pushed
the
fix-sync-publish
branch
from
December 21, 2023 02:27
fef577a
to
6331fba
Compare
Quality Gate passedKudos, no new issues were introduced! 0 New issues |
[FE Incremental Coverage Report]✅ pass : 4 / 4 (100.00%) file detail
|
[BE Incremental Coverage Report]✅ pass : 0 / 0 (0%) |
sevev
approved these changes
Dec 21, 2023
decster
approved these changes
Dec 21, 2023
@Mergifyio backport branch-3.2 |
@Mergifyio backport branch-3.0 |
✅ Backports have been created
|
✅ Backports have been created
|
@Mergifyio backport branch-2.5 |
✅ Backports have been created
|
✅ Backports have been created
|
mergify bot
pushed a commit
that referenced
this pull request
Dec 21, 2023
Why I'm doing: In previous PR #27055 , we add config enable_sync_publish. When it is true, BE will return publish version request success until all version is queryable. But when clone happen, BE report both version and max_readable_version to FE in finish clone request, and FE will use version instead of max_readable_version to update replica version, so it will broken the rule that enable_sync_publish define, because version may not queryable yet. What I'm doing: Using max_readable_version instead of version to update replica version when clone finish. Signed-off-by: luohaha <[email protected]> (cherry picked from commit 575e644)
mergify bot
pushed a commit
that referenced
this pull request
Dec 21, 2023
Why I'm doing: In previous PR #27055 , we add config enable_sync_publish. When it is true, BE will return publish version request success until all version is queryable. But when clone happen, BE report both version and max_readable_version to FE in finish clone request, and FE will use version instead of max_readable_version to update replica version, so it will broken the rule that enable_sync_publish define, because version may not queryable yet. What I'm doing: Using max_readable_version instead of version to update replica version when clone finish. Signed-off-by: luohaha <[email protected]> (cherry picked from commit 575e644)
This was referenced Dec 21, 2023
mergify bot
pushed a commit
that referenced
this pull request
Dec 21, 2023
Why I'm doing: In previous PR #27055 , we add config enable_sync_publish. When it is true, BE will return publish version request success until all version is queryable. But when clone happen, BE report both version and max_readable_version to FE in finish clone request, and FE will use version instead of max_readable_version to update replica version, so it will broken the rule that enable_sync_publish define, because version may not queryable yet. What I'm doing: Using max_readable_version instead of version to update replica version when clone finish. Signed-off-by: luohaha <[email protected]> (cherry picked from commit 575e644)
mergify bot
pushed a commit
that referenced
this pull request
Dec 21, 2023
Why I'm doing: In previous PR #27055 , we add config enable_sync_publish. When it is true, BE will return publish version request success until all version is queryable. But when clone happen, BE report both version and max_readable_version to FE in finish clone request, and FE will use version instead of max_readable_version to update replica version, so it will broken the rule that enable_sync_publish define, because version may not queryable yet. What I'm doing: Using max_readable_version instead of version to update replica version when clone finish. Signed-off-by: luohaha <[email protected]> (cherry picked from commit 575e644)
This was referenced Dec 21, 2023
@mergify backport branch-2.5-bx |
✅ Backports have been created
|
mergify bot
pushed a commit
that referenced
this pull request
Dec 21, 2023
Why I'm doing: In previous PR #27055 , we add config enable_sync_publish. When it is true, BE will return publish version request success until all version is queryable. But when clone happen, BE report both version and max_readable_version to FE in finish clone request, and FE will use version instead of max_readable_version to update replica version, so it will broken the rule that enable_sync_publish define, because version may not queryable yet. What I'm doing: Using max_readable_version instead of version to update replica version when clone finish. Signed-off-by: luohaha <[email protected]> (cherry picked from commit 575e644)
sevev
pushed a commit
that referenced
this pull request
Dec 21, 2023
Co-authored-by: Yixin Luo <[email protected]>
luohaha
added a commit
that referenced
this pull request
Dec 21, 2023
Co-authored-by: Yixin Luo <[email protected]>
wanpengfei-git
pushed a commit
that referenced
this pull request
Dec 21, 2023
Co-authored-by: Yixin Luo <[email protected]>
wanpengfei-git
pushed a commit
that referenced
this pull request
Dec 21, 2023
Co-authored-by: Yixin Luo <[email protected]>
wanpengfei-git
pushed a commit
that referenced
this pull request
Dec 21, 2023
Co-authored-by: Yixin Luo <[email protected]>
Zhangg7723
pushed a commit
to Zhangg7723/starrocks
that referenced
this pull request
Dec 26, 2023
Why I'm doing: In previous PR StarRocks#27055 , we add config enable_sync_publish. When it is true, BE will return publish version request success until all version is queryable. But when clone happen, BE report both version and max_readable_version to FE in finish clone request, and FE will use version instead of max_readable_version to update replica version, so it will broken the rule that enable_sync_publish define, because version may not queryable yet. What I'm doing: Using max_readable_version instead of version to update replica version when clone finish. Signed-off-by: luohaha <[email protected]> Signed-off-by: 张敢 <[email protected]>
mergify bot
added a commit
that referenced
this pull request
Jan 2, 2024
Co-authored-by: Yixin Luo <[email protected]> (cherry picked from commit 401dea6)
andyziye
pushed a commit
that referenced
this pull request
Jan 3, 2024
#37512) (#38282) Signed-off-by: Yixin Luo <[email protected]>
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.
Why I'm doing:
In previous PR #27055 , we add config
enable_sync_publish
. When it is true, BE will return publish version request success until all version is queryable.But when clone happen, BE report both
version
andmax_readable_version
to FE in finish clone request, and FE will useversion
instead ofmax_readable_version
to update replica version, so it will broken the rule thatenable_sync_publish
define, becauseversion
may not queryable yet.What I'm doing:
Using
max_readable_version
instead ofversion
to update replica version when clone finish.What type of PR is this:
Does this PR entail a change in behavior?
If yes, please specify the type of change:
Checklist:
Bugfix cherry-pick branch check: