Correct TiCDC Debezium DDL/WATERMARK support reference#23470
Conversation
|
Hi @copilot. Thanks for your PR. I'm waiting for a pingcap member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions 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. |
Co-authored-by: lilin90 <30922556+lilin90@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 |
First-time contributors' checklist
What is changed, added or deleted? (Required)
The TiCDC Debezium doc incorrectly stated that DDL and WATERMARK events are supported starting in
v9.0.0. This update replaces that version claim with an architecture-based reference that matches actual product behavior.Doc correction
/ticdc/ticdc-debezium.mdto remove the incorrectv9.0.0statement.Cross-reference cleanup
/ticdc/ticdc-architecture.mdso the support boundary is defined by architecture, not by an incorrect version marker.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)?
/ticdc/ticdc-debezium.md/ticdc/ticdc-architecture.mdAI agent involvement
Do your changes match any of the following descriptions?