This is an automated email from the ASF dual-hosted git repository.

wanghailin pushed a commit to branch dev
in repository https://gitbox.apache.org/repos/asf/seatunnel.git


The following commit(s) were added to refs/heads/dev by this push:
     new 64ebdb753e [Docs] update debezium json document (#6652)
64ebdb753e is described below

commit 64ebdb753e3f9f857f2623c3f37c34129c41509f
Author: Jarvis <[email protected]>
AuthorDate: Sun Apr 7 18:53:33 2024 +0800

    [Docs] update debezium json document (#6652)
---
 docs/en/connector-v2/formats/debezium-json.md | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/docs/en/connector-v2/formats/debezium-json.md 
b/docs/en/connector-v2/formats/debezium-json.md
index a01e6c70d6..d1deebfef9 100644
--- a/docs/en/connector-v2/formats/debezium-json.md
+++ b/docs/en/connector-v2/formats/debezium-json.md
@@ -68,6 +68,12 @@ 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 the messages have been synchronized to Kafka topic products_binlog, 
then we can use the following Seatunnel conf to consume this topic and 
interpret the change events by Debezium format.
 
+**In this config, you must specify the `schema` and 
`debezium_record_include_schema` options **
+- `schema` should same with your table format
+- if your json data contains `schema` field, `debezium_record_include_schema` 
should be true, and if your json data doesn't contains `schema` field, 
`debezium_record_include_schema` should be false
+- `{"schema" : {}, "payload": { "before" : {}, "after": {} ... } }` --> `true`
+- `{"before" : {}, "after": {} ... }` --> `false`
+
 ```bash
 env {
     parallelism = 1
@@ -88,6 +94,7 @@ source {
            weight = "string"
       }
     }
+    debezium_record_include_schema = false
     format = debezium_json
   }
 

Reply via email to