cdc: add table routing feature #23211
Conversation
|
Note Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported. |
Synced from: pingcap/docs-cn#21723 Target PR: pingcap#23211 AI Provider: azure Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
|
Auto-sync completed successfully Source PR: pingcap/docs-cn#21723 English documentation has been updated based on Chinese documentation changes. |
|
/gemini review |
There was a problem hiding this comment.
Code Review
This pull request adds a new documentation page for TiCDC Table Routing, updates the table of contents, and revises the changefeed configuration documentation to reflect this new feature. The reviewer's feedback is highly constructive, focusing on style guide compliance such as converting passive voice to active voice, replacing "synchronize" with "replicate", correcting localized Chinese anchor links, and ensuring consistent casing for technical terms.
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>
|
@3AceShowHand: 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. |
|
[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 |
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 (in Chinese).
What is the related PR or file link(s)?
Do your changes match any of the following descriptions?