-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
[Enhancement] Optimize partition retention condition compensation rewrite performance in force_mv mode #54072
Open
LiShuMing
wants to merge
2
commits into
StarRocks:main
Choose a base branch
from
LiShuMing:refactor_mv_compensation
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+549
−83
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
LiShuMing
changed the title
[Refactor] [WIP] Refactor mv compensation
[UT] [Refactor] [WIP] Refactor mv compensation
Dec 18, 2024
LiShuMing
changed the title
[UT] [Refactor] [WIP] Refactor mv compensation
[Refactor] [WIP] Refactor mv compensation
Dec 19, 2024
LiShuMing
force-pushed
the
refactor_mv_compensation
branch
from
December 19, 2024 08:54
060ad01
to
ad39d68
Compare
LiShuMing
force-pushed
the
refactor_mv_compensation
branch
2 times, most recently
from
December 19, 2024 09:00
eb49de3
to
1751598
Compare
LiShuMing
changed the title
[Refactor] [WIP] Refactor mv compensation
[Refactor] Refactor mv partition compensation
Dec 19, 2024
LiShuMing
changed the title
[Refactor] Refactor mv partition compensation
[UT] [Refactor] Refactor mv partition compensation
Dec 19, 2024
LiShuMing
force-pushed
the
refactor_mv_compensation
branch
3 times, most recently
from
December 23, 2024 06:10
f0e6119
to
8f59671
Compare
LiShuMing
changed the title
[UT] [Refactor] Refactor mv partition compensation
[Refactor] [WIP] Refactor mv partition compensation
Dec 24, 2024
@mergify rebase |
✅ Branch has been successfully rebased |
LiShuMing
force-pushed
the
refactor_mv_compensation
branch
from
December 24, 2024 04:45
df49bc0
to
40179c8
Compare
LiShuMing
changed the title
[Refactor] [WIP] Refactor mv partition compensation
[UT] [Refactor] [WIP] Refactor mv partition compensation
Dec 25, 2024
LiShuMing
changed the title
[UT] [Refactor] [WIP] Refactor mv partition compensation
[UT] [Enhancement] [WIP] Support partition retention condition compensation in force_mv rewrite mode
Dec 26, 2024
LiShuMing
force-pushed
the
refactor_mv_compensation
branch
from
December 26, 2024 08:39
e9f58a0
to
8b5d3d7
Compare
LiShuMing
changed the title
[UT] [Enhancement] [WIP] Support partition retention condition compensation in force_mv rewrite mode
[Enhancement] [WIP] Support partition retention condition compensation in force_mv rewrite mode
Dec 27, 2024
24 tasks
LiShuMing
force-pushed
the
refactor_mv_compensation
branch
from
January 2, 2025 07:11
8b5d3d7
to
48381e0
Compare
LiShuMing
changed the title
[Enhancement] [WIP] Support partition retention condition compensation in force_mv rewrite mode
[Enhancement] Support partition retention condition compensation in force_mv rewrite mode
Jan 2, 2025
LiShuMing
changed the title
[Enhancement] Support partition retention condition compensation in force_mv rewrite mode
[Enhancement] Optimize partition retention condition compensation rewrite performance in force_mv mode
Jan 3, 2025
LiShuMing
force-pushed
the
refactor_mv_compensation
branch
from
January 3, 2025 10:00
ac0c138
to
6ae689a
Compare
…ce in force_mv mode Signed-off-by: shuming.li <[email protected]>
LiShuMing
force-pushed
the
refactor_mv_compensation
branch
from
January 3, 2025 10:13
6ae689a
to
9b66a1f
Compare
Signed-off-by: shuming.li <[email protected]>
Quality Gate failedFailed conditions See analysis details on SonarQube Cloud Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE |
[Java-Extensions Incremental Coverage Report]✅ pass : 0 / 0 (0%) |
[FE Incremental Coverage Report]✅ pass : 196 / 239 (82.01%) file detail
|
[BE Incremental Coverage Report]✅ pass : 0 / 0 (0%) |
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:
What I'm doing:
Fixes #53117
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: