-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
[fix](Nereids) insert lock all target tables #47033
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
we get target table twice, lock them all
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
run buildall |
TPC-H: Total hot run time: 32191 ms
|
TPC-DS: Total hot run time: 187954 ms
|
ClickBench: Total hot run time: 30.05 s
|
run p0 |
starocean999
approved these changes
Jan 16, 2025
PR approved by at least one committer and no changes requested. |
PR approved by anyone and no changes requested. |
Jibing-Li
approved these changes
Jan 16, 2025
morrySnow
added a commit
to morrySnow/incubator-doris
that referenced
this pull request
Jan 17, 2025
pick from master apache#47033 Related PR: apache#45045 Problem Summary: we get target table twice, lock them all
github-actions bot
pushed a commit
that referenced
this pull request
Jan 17, 2025
### What problem does this PR solve? Related PR: #45045 Problem Summary: we get target table twice, lock them all
morrySnow
added a commit
that referenced
this pull request
Jan 17, 2025
morrySnow
added a commit
to morrySnow/incubator-doris
that referenced
this pull request
Jan 20, 2025
dataroaring
pushed a commit
that referenced
this pull request
Jan 21, 2025
16 tasks
morrySnow
added a commit
that referenced
this pull request
Jan 24, 2025
…the original target table (#47337) ### What problem does this PR solve? Related PR: #47033 #45045 Problem Summary: because schema change does not involve recreating the table object, but rather rebuilding the full schema. So, we should use the schema saved during planning as the schema of the original target table.
github-actions bot
pushed a commit
that referenced
this pull request
Jan 24, 2025
…the original target table (#47337) ### What problem does this PR solve? Related PR: #47033 #45045 Problem Summary: because schema change does not involve recreating the table object, but rather rebuilding the full schema. So, we should use the schema saved during planning as the schema of the original target table.
morrySnow
added a commit
that referenced
this pull request
Feb 11, 2025
…e schema of the original target table #47337 pick from master #47337 Related PR: #47033 #45045 Problem Summary: because schema change does not involve recreating the table object, but rather rebuilding the full schema. So, we should use the schema saved during planning as the schema of the original target table.
lzyy2024
pushed a commit
to lzyy2024/doris
that referenced
this pull request
Feb 21, 2025
### What problem does this PR solve? Related PR: apache#45045 Problem Summary: we get target table twice, lock them all
lzyy2024
pushed a commit
to lzyy2024/doris
that referenced
this pull request
Feb 21, 2025
…the original target table (apache#47337) ### What problem does this PR solve? Related PR: apache#47033 apache#45045 Problem Summary: because schema change does not involve recreating the table object, but rather rebuilding the full schema. So, we should use the schema saved during planning as the schema of the original target table.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
approved
Indicates a PR has been approved by one committer.
dev/2.1.8-merged
dev/3.0.4-merged
reviewed
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?
Related PR: #45045
Problem Summary:
we get target table twice, lock them all
Release note
None
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)