JingGe commented on code in PR #24395: URL: https://github.com/apache/flink/pull/24395#discussion_r1505116020
########## docs/content/docs/connectors/table/formats/debezium.md: ########## @@ -133,7 +134,30 @@ In some cases, users may setup the Debezium Kafka Connect with the Kafka configu In order to interpret such messages, you need to add the option `'debezium-json.schema-include' = 'true'` into above DDL WITH clause (`false` by default). Usually, this is not recommended to include schema because this makes the messages very verbose and reduces parsing performance. -After registering the topic as a Flink table, then you can consume the Debezium messages as a changelog source. +#### Debezium Avro DDL Review Comment: ```suggestion #### Debezium Confluent Avro DDL ``` ########## docs/content/docs/connectors/table/formats/debezium.md: ########## @@ -85,7 +85,9 @@ Debezium provides a unified format for changelog, here is a simple example for a *Note: please refer to [Debezium documentation](https://debezium.io/documentation/reference/1.3/connectors/mysql.html#mysql-connector-events_debezium) about the meaning of each fields.* The MySQL `products` table has 4 columns (`id`, `name`, `description` and `weight`). The above JSON message is an update change event on the `products` table where the `weight` value of the row with `id = 111` is changed from `5.18` to `5.15`. -Assuming this messages is synchronized to Kafka topic `products_binlog`, then we can use the following DDL to consume this topic and interpret the change events. +Assuming this messages is synchronized to Kafka topic `products_binlog`, then we can use the following DDLs (for Debezium Json and Debezium Avro) to consume this topic and interpret the change events. Review Comment: ```suggestion Assuming this messages is synchronized to Kafka topic `products_binlog`, then we can use the following DDLs (for Debezium Json and Debezium Confluent Avro) to consume this topic and interpret the change events. ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
