-
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] Use copyOnlyForQuery instead of deepCopy to avoid time costs in mv refresh's collectBaseTableSnapshotInfos #48256
Merged
LiShuMing
merged 2 commits into
StarRocks:main
from
LiShuMing:fix/main/fix_deep_copy_mv_refresh
Jul 12, 2024
Merged
[BugFix] Use copyOnlyForQuery instead of deepCopy to avoid time costs in mv refresh's collectBaseTableSnapshotInfos #48256
LiShuMing
merged 2 commits into
StarRocks:main
from
LiShuMing:fix/main/fix_deep_copy_mv_refresh
Jul 12, 2024
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
…fresh's collectBaseTableSnapshotInfos Signed-off-by: shuming.li <ming.moriarty@gmail.com>
fe/fe-core/src/main/java/com/starrocks/scheduler/PartitionBasedMvRefreshProcessor.java
Show resolved
Hide resolved
LiShuMing
force-pushed
the
fix/main/fix_deep_copy_mv_refresh
branch
from
July 12, 2024 03:05
6f79cca
to
ae70112
Compare
Quality Gate passedIssues Measures |
[FE Incremental Coverage Report]✅ pass : 14 / 14 (100.00%) file detail
|
[BE Incremental Coverage Report]✅ pass : 0 / 0 (0%) |
LiShuMing
changed the title
[UT] Use copyOnlyForQuery instead of deepCopy to avoid time costs in mv refresh's collectBaseTableSnapshotInfos
[BugFix] Use copyOnlyForQuery instead of deepCopy to avoid time costs in mv refresh's collectBaseTableSnapshotInfos
Jul 12, 2024
Seaven
approved these changes
Jul 12, 2024
satanson
approved these changes
Jul 12, 2024
HangyuanLiu
approved these changes
Jul 12, 2024
@Mergifyio backport branch-3.3 |
@Mergifyio backport branch-3.2 |
@Mergifyio backport branch-3.1 |
✅ Backports have been created
|
✅ Backports have been created
|
✅ Backports have been created
|
mergify bot
pushed a commit
that referenced
this pull request
Jul 12, 2024
… in mv refresh's collectBaseTableSnapshotInfos (#48256) Signed-off-by: shuming.li <ming.moriarty@gmail.com> (cherry picked from commit af19cfb) # Conflicts: # fe/fe-core/src/main/java/com/starrocks/catalog/OlapTable.java # fe/fe-core/src/main/java/com/starrocks/scheduler/PartitionBasedMvRefreshProcessor.java
42 tasks
mergify bot
pushed a commit
that referenced
this pull request
Jul 12, 2024
… in mv refresh's collectBaseTableSnapshotInfos (#48256) Signed-off-by: shuming.li <ming.moriarty@gmail.com> (cherry picked from commit af19cfb) # Conflicts: # fe/fe-core/src/main/java/com/starrocks/catalog/OlapTable.java # fe/fe-core/src/main/java/com/starrocks/scheduler/PartitionBasedMvRefreshProcessor.java # fe/fe-core/src/main/java/com/starrocks/scheduler/TableSnapshotInfo.java
mergify bot
pushed a commit
that referenced
this pull request
Jul 12, 2024
… in mv refresh's collectBaseTableSnapshotInfos (#48256) Signed-off-by: shuming.li <ming.moriarty@gmail.com> (cherry picked from commit af19cfb) # Conflicts: # fe/fe-core/src/main/java/com/starrocks/catalog/OlapTable.java # fe/fe-core/src/main/java/com/starrocks/scheduler/PartitionBasedMvRefreshProcessor.java # fe/fe-core/src/main/java/com/starrocks/scheduler/TableSnapshotInfo.java
This was referenced Jul 12, 2024
smartlxh
pushed a commit
to smartlxh/starrocks
that referenced
this pull request
Oct 16, 2024
…time costs in mv refresh's collectBaseTableSnapshotInfos (backport StarRocks#48256) (StarRocks#48270) Link: https://code.alibaba-inc.com/soe/starrocks/codereview/17914626 Signed-off-by: shuming.li <ming.moriarty@gmail.com> Co-authored-by: shuming.li <ming.moriarty@gmail.com>
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:
copyOnlyForQuery
to reduce the cost.What I'm doing:
Fixes #issue
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: