wip

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.
+[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 v8.6, TiCDC supports DDL events and watermark events.
 
 ## Use the Debezium message format
 
@@ -27,11 +27,13 @@ In addition, the original Debezium format does not include important fields such
 
 This section describes the format definition of the DML event output in the Debezium format.
 
+### DDL event
+
 ### DML event
 
 TiCDC encodes a DML event into a Kafka message, with both the key and value encoded in the Debezium format.
 
-### Key format
+#### Key format
 
 ```json
 {
@@ -164,6 +166,9 @@ The key fields of the preceding JSON data are explained as follows:
 | schema.optional| Boolean | Indicates whether the field is optional. When it is `true`, the field is optional.  |
 | schema.type    | String  | The data type of the field.                                      |
 
+### WATERMARK
+
+
 ### Data type mapping
 
 The data format mapping in the TiCDC Debezium message basically follows the [Debezium data type mapping rules](https://debezium.io/documentation/reference/2.4/connectors/mysql.html#mysql-data-types), which is generally consistent with the native message of the Debezium Connector for MySQL. However, for some data types, the following differences exist between TiCDC Debezium and Debezium Connector messages: