-
Notifications
You must be signed in to change notification settings - Fork 687
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
system-variables: update from generated source #6838
system-variables: update from generated source #6838
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 are a lot of broken external links which seem unrelated to this PR, and are causing the CI check to fail. |
|
|
||
### wait_timeout | ||
|
||
- Scope: SESSION | GLOBAL | ||
- Default value: `0` | ||
- Default value: `28800` |
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.
We always treat the default value change with extra care. From which version this default value is changed? If it is changed from v5.3.0, shall we let the QA team @seiya-annie know and add it to v5.3.0 release notes?
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.
I took a look at the PR, and it's not cherry picked: pingcap/tidb#29569
So it is master only right now.
It might be worth docs having a script to detect defaults changes. I am not specifically changing the default here - it has already been changed.
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.
Translated into Chinese in pingcap/docs-cn#8076
You can ignore the external link checker. It only serves as a reference and does not block merge. It might be inaccurate. |
I've unchecked 5.3 although it applies except the default for Can we merge this soon? There are already a few more updates, and I would like to create a new PR to follow on, so we can track system variables changes as they are made. |
@@ -845,14 +846,14 @@ Query OK, 0 rows affected (0.09 sec) | |||
- Default value: `ON` | |||
- This variable is used to dynamically control whether the telemetry collection in TiDB is enabled. By setting the value to `OFF`, the telemetry collection is disabled. If the [`enable-telemetry`](/tidb-configuration-file.md#enable-telemetry-new-in-v402) TiDB configuration item is set to `false` on all TiDB instances, the telemetry collection is always disabled and this system variable will not take effect. See [Telemetry](/telemetry.md) for details. | |||
|
|||
### tidb_enable_tso_follower_proxy <span class="version-mark">New in v5.3</span> | |||
### tidb_enable_tso_follower_proxy <span class="version-mark">New in v5.3.0</span> |
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.
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.
Fixed :-)
…into fix-sv-from-generated-source
/merge |
This pull request has been accepted and is ready to merge. Commit hash: 00ee361
|
What is changed, added or deleted? (Required)
This updates system variables, and is generated against the tidb source code. It is similar to previous PRs such as #6665
The changes are very minor and mainly improve consistency:
version_compile_os
andversion_compile_machine
were alphabetically in the wrong order.wait_timeout
has changed defaulttimestamp
has changed default (it now works correctly)Which TiDB version(s) do your changes apply to? (Required)
Tips for choosing the affected version(s):
By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.
For details, see tips for choosing the affected versions.
What is the related PR or file link(s)?
Do your changes match any of the following descriptions?