-
Notifications
You must be signed in to change notification settings - Fork 5.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
br: use the RestrictedSQLExecutor to exec the internal SQL. #29802
Conversation
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by submitting an approval review. |
commit 2ec8cea Author: joccau <[email protected]> Date: Tue Nov 16 17:37:19 2021 +0800 add test case for mysql.stats_meta after restore Signed-off-by: joccau <[email protected]>
/run-integration-br-test |
@winoros: The following test failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
@winoros: The following test failed, say
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
What problem does this PR solve?
Issue Number: to #29749
Problem Summary:
When we are using the SQL use trigger the br. It would store the current session for its own usage.
If we use its
ExecuteInternal
to execute the SQL. The session will execute two statement at the same time, this would cause bug.What is changed and how it works?
Check List
Tests
Release note