-
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
[Enhancement] Support transaction_read_only compatible with mysql #37249
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
Signed-off-by: Astralidea <[email protected]>
imay
reviewed
Dec 18, 2023
Signed-off-by: Astralidea <[email protected]>
Quality Gate passedKudos, no new issues were introduced! 0 New issues |
[FE Incremental Coverage Report]✅ pass : 1 / 1 (100.00%) file detail
|
[BE Incremental Coverage Report]✅ pass : 0 / 0 (0%) |
chaoyli
approved these changes
Dec 18, 2023
gengjun-git
approved these changes
Dec 19, 2023
@Mergifyio backport branch-3.2 |
@Mergifyio backport branch-3.1 |
@Mergifyio backport branch-3.0 |
@Mergifyio backport branch-2.5 |
✅ Backports have been created
|
✅ Backports have been created
|
✅ Backports have been created
|
✅ Backports have been created
|
mergify bot
pushed a commit
that referenced
this pull request
Dec 19, 2023
…7249) Signed-off-by: Astralidea <[email protected]> (cherry picked from commit 64ecbc5)
mergify bot
pushed a commit
that referenced
this pull request
Dec 19, 2023
…7249) Signed-off-by: Astralidea <[email protected]> (cherry picked from commit 64ecbc5)
This was referenced Dec 19, 2023
mergify bot
pushed a commit
that referenced
this pull request
Dec 19, 2023
…7249) Signed-off-by: Astralidea <[email protected]> (cherry picked from commit 64ecbc5)
18 tasks
mergify bot
pushed a commit
that referenced
this pull request
Dec 19, 2023
…7249) Signed-off-by: Astralidea <[email protected]> (cherry picked from commit 64ecbc5)
18 tasks
wanpengfei-git
pushed a commit
that referenced
this pull request
Dec 19, 2023
…ckport #37249) (#37291) Co-authored-by: Felix Li <[email protected]>
wanpengfei-git
pushed a commit
that referenced
this pull request
Dec 19, 2023
…ckport #37249) (#37290) Co-authored-by: Felix Li <[email protected]>
wanpengfei-git
pushed a commit
that referenced
this pull request
Dec 19, 2023
…ckport #37249) (#37289) Co-authored-by: Felix Li <[email protected]>
Astralidea
added a commit
that referenced
this pull request
Dec 21, 2023
…ckport #37249) (#37288) Co-authored-by: Felix Li <[email protected]>
Zhangg7723
pushed a commit
to Zhangg7723/starrocks
that referenced
this pull request
Dec 26, 2023
…arRocks#37249) Signed-off-by: Astralidea <[email protected]> Signed-off-by: 张敢 <[email protected]>
chaoyli
pushed a commit
to chaoyli/starrocks
that referenced
this pull request
Feb 22, 2024
…ckport StarRocks#37249) (StarRocks#37288) Co-authored-by: Felix Li <[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:
The transaction_read_only parameter was introduced in mysql version 5.7.20. When users set mysql to a higher version, some BI may report an error.
What I'm doing:
add transaction_read_only and tx_read_only.
Fixes #37243
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: