Repository navigation
v8.5.7: clarify DM foreign key support for one-to-one routing (#23153) - #23183
Conversation
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Airton Lastori <alastori@gmail.com>
There was a problem hiding this comment.
Code Review
This pull request updates the DM documentation to detail the experimental support and limitations for replicating tables with foreign key constraints, including new static one-to-one table routing capabilities introduced in version 8.5.7. The review feedback correctly identifies style guide violations where the version is referred to as v8.5.7 instead of DM v8.5.7, and provides actionable suggestions to align with the repository's versioning notation rules.
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.
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: lilin90 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 |
3db150c
into
pingcap:feature/preview-v8.5.7
This is an automated cherry-pick of #23153
What is changed, added or deleted? (Required)
foreign_key_checks=1.compactandmultiple-rowsare not supported whenforeign_key_checks=1.foreign_key_checks=1andworker-count > 1.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?