release-8.5: v8.5.7 doc changes#23225
Conversation
There was a problem hiding this comment.
Code Review
This pull request updates the TiDB documentation for the v8.5.7 release, introducing several new features and improvements, including LATERAL derived tables syntax parsing, partial indexes, CPU-aware hot Region scheduling, TiCDC table routing, GCP KMS encryption with WIF, and the max_user_connections attribute. It also documents new system variables like performance_schema_session_connect_attrs_size and tidb_enable_batch_query_region, updates default values for auto-analyze concurrency and index merge fix controls, and removes references to the deprecated TiDB Lightning Web Interface. The reviewer's feedback focuses on aligning the text with the style guide by converting passive voice to active voice, addressing the user directly in the second person, correcting capitalization (e.g., 'CPU'), ensuring consistent terminology (e.g., 'logical I/O'), and using the present tense for updated behaviors.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
[LGTM Timeline notifier]Timeline:
|
|
/approve |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: qiancai The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What is changed, added or deleted? (Required)
This PR consolidates all changes made in the feature/preview-8.5.7 branch.
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?