ticdc: add scheduler.region-count-per-span in v8.5.4 release notes#22688
ticdc: add scheduler.region-count-per-span in v8.5.4 release notes#22688hfxsd wants to merge 3 commits intopingcap:masterfrom
scheduler.region-count-per-span in v8.5.4 release notes#22688Conversation
ti-chi-bot
bot
added
missing-translation-status
hfxsd
added
translation/doing
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates the release notes for version 8.5.4 by adding a new configuration parameter for TiCDC, scheduler.region-count-per-span. Review feedback identified an incorrect documentation URL and suggested improvements to the description to avoid passive voice and redundancy. Additionally, a stray line of text was found and should be removed.
Synced from: pingcap/docs#22688 Target PR: pingcap#21508 AI Provider: gemini Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
ti-chi-bot
bot
added
the
size/XS
hfxsd
added
translation/done
[LGTM Timeline notifier]Timeline:
|
|
@hongyunyan: adding LGTM is restricted to approvers and reviewers in OWNERS files. DetailsIn response to this: 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-sigs/prow repository. |
3 participants
First-time contributors' checklist
What is changed, added or deleted? (Required)
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?