Skip to content

Commit

Permalink
Update ticdc/ticdc-avro-protocol.md
Browse files Browse the repository at this point in the history
Co-authored-by: kennytm <[email protected]>
  • Loading branch information
wk989898 and kennytm authored Dec 4, 2024
1 parent 9fa09d6 commit 5b508c6
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion ticdc/ticdc-avro-protocol.md
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down

0 comments on commit 5b508c6

Please sign in to comment.