From 5b508c6d7bea7ef4f63c55fadcc013ace6992ef1 Mon Sep 17 00:00:00 2001 From: nhsmw Date: Wed, 4 Dec 2024 18:44:08 +0800 Subject: [PATCH] Update ticdc/ticdc-avro-protocol.md Co-authored-by: kennytm --- ticdc/ticdc-avro-protocol.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ticdc/ticdc-avro-protocol.md b/ticdc/ticdc-avro-protocol.md index ee28ec77715f1..4a588afcb817b 100644 --- a/ticdc/ticdc-avro-protocol.md +++ b/ticdc/ticdc-avro-protocol.md @@ -84,7 +84,7 @@ The data format of Value is the same as that of Key, by default. However, `field > - For Insert events, Avro encodes all column data to the Value part. > - For Update events, Avro encodes only all column data that is updated to the Value part. > -> If you want the old values with Update or Delete events, you can use other protocols. +> The Avro protocol does not encode the old values for Update and Delete events. Additionally, in order to be compatible to most Confluent sink connectors which only recognizes `null` record for deletion (`"delete.on.null"`), a Delete event cannot carry extension information such as `_tidb_commit_ts` even when enabling `enable-tidb-extension`. If you need these features, consider using other protocols such as Canal-JSON or Debezium. ## TiDB extension fields