From 16c121affd99a13f4d7525f46000a85dd2af1b2a Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Fri, 7 Aug 2026 09:18:06 +0000 Subject: [PATCH 1/3] Initial plan From e959428c646113d441e8050e01bfdb48f77630ee Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Fri, 7 Aug 2026 09:22:24 +0000 Subject: [PATCH 2/3] Fix TiCDC Debezium architecture reference Co-authored-by: lilin90 <30922556+lilin90@users.noreply.github.com> --- ticdc/ticdc-debezium.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ticdc/ticdc-debezium.md b/ticdc/ticdc-debezium.md index 05a580652e11b..5e9f06ac6a7ae 100644 --- a/ticdc/ticdc-debezium.md +++ b/ticdc/ticdc-debezium.md @@ -5,7 +5,7 @@ summary: Learn the concept of the TiCDC Debezium Protocol and how to use it. # TiCDC Debezium Protocol -[Debezium](https://debezium.io/) is a tool for capturing database changes. It converts each captured database change into a message called an "event" and sends these events to Kafka. Starting from v8.0.0, TiCDC supports sending TiDB changes to Kafka using a Debezium style output format, simplifying migration from MySQL databases for users who had previously been using Debezium's MySQL integration. Starting from v9.0.0, TiCDC supports DDL events and WATERMARK events. +[Debezium](https://debezium.io/) is a tool for capturing database changes. It converts each captured database change into a message called an "event" and sends these events to Kafka. Starting from v8.0.0, TiCDC supports sending TiDB changes to Kafka using a Debezium style output format, simplifying migration from MySQL databases for users who had previously been using Debezium's MySQL integration. In the [TiCDC new architecture](/ticdc/ticdc-architecture.md), TiCDC supports DDL events and WATERMARK events. ## Use the Debezium message format From 641424131cc7557897541e6431a1d55820de71bd Mon Sep 17 00:00:00 2001 From: Lilian Lee Date: Fri, 7 Aug 2026 17:32:44 +0800 Subject: [PATCH 3/3] Apply suggestions from code review --- ticdc/ticdc-debezium.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ticdc/ticdc-debezium.md b/ticdc/ticdc-debezium.md index 5e9f06ac6a7ae..e7c15885d8f41 100644 --- a/ticdc/ticdc-debezium.md +++ b/ticdc/ticdc-debezium.md @@ -5,7 +5,7 @@ summary: Learn the concept of the TiCDC Debezium Protocol and how to use it. # TiCDC Debezium Protocol -[Debezium](https://debezium.io/) is a tool for capturing database changes. It converts each captured database change into a message called an "event" and sends these events to Kafka. Starting from v8.0.0, TiCDC supports sending TiDB changes to Kafka using a Debezium style output format, simplifying migration from MySQL databases for users who had previously been using Debezium's MySQL integration. In the [TiCDC new architecture](/ticdc/ticdc-architecture.md), TiCDC supports DDL events and WATERMARK events. +[Debezium](https://debezium.io/) is a tool for capturing database changes. It converts each captured database change into a message called an "event" and sends these events to Kafka. Starting from v8.0.0, TiCDC supports sending TiDB changes to Kafka using a Debezium style output format, simplifying migration from MySQL databases for users who had previously been using Debezium's MySQL integration. Starting from [TiCDC v8.5.4-release.1](https://github.com/pingcap/ticdc/releases/tag/v8.5.4-release.1) ([TiCDC new architecture](/ticdc/ticdc-architecture.md)) and v9.0.0, TiCDC supports DDL events and WATERMARK events. ## Use the Debezium message format