-
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
*: add support for -initialize-sql-file on first bootstrap (#35625) #41530
*: add support for -initialize-sql-file on first bootstrap (#35625) #41530
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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/retest |
/merge |
This pull request has been accepted and is ready to merge. Commit hash: d18f498
|
This is an automated cherry-pick of #35625
What problem does this PR solve?
Issue Number: close #35624
Problem Summary:
Because tidb persists global variables to the cluster, setting configuration requires first waiting for TiDB to listen and then a mysql client to connect and set initial values of the variables. This requires some clumsy automation scripts. It's much easier if the server can accept a SQL file with which to specify a set of SQL commands to execute on first bootstrap only.
What is changed and how it works?
A new option
-initialize-sql-file
is added to the tidb-server binary.Check List
Tests
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.