Changelog-Data-Capture Format: Serialization Schema Format: Deserialization Schema

Debezium is a set of distributed services to capture changes in your databases so that your applications can see those changes and respond to them. Debezium records all row-level changes within each database table in a change event stream, and applications simply read these streams to see the change events in the same order in which they occurred.

Seatunnel supports to interpret Debezium JSON messages as INSERT/UPDATE/DELETE messages into seatunnel system. This is useful in many cases to leverage this feature, such as

  1. synchronizing incremental data from databases to other systems
  2. auditing logs
  3. real-time materialized views on databases
  4. temporal join changing history of a database table and so on.

Seatunnel also supports to encode the INSERT/UPDATE/DELETE messages in Seatunnel asDebezium JSON messages, and emit to storage like Kafka.

Format Options

Option Default Required Description
format (none) yes Specify what format to use, here should be ‘debezium_json’.
debezium-json.ignore-parse-errors false no Skip fields and rows with parse errors instead of failing. Fields are set to null in case of errors.

How To Use

Kafka Uses example

Debezium provides a unified format for changelog, here is a simple example for an update operation captured from a MySQL products table:

  1. {
  2.     "before": {
  3.         "id": 111,
  4.         "name": "scooter",
  5.         "description": "Big 2-wheel scooter ",
  6.         "weight": 5.18
  7.     },
  8.     "after": {
  9.         "id": 111,
  10.         "name": "scooter",
  11.         "description": "Big 2-wheel scooter ",
  12.         "weight": 5.17
  13.     },
  14.     "source": {
  15.         "version": "1.1.1.Final",
  16.         "connector": "mysql",
  17.         "name": "dbserver1",
  18.         "ts_ms": 1589362330000,
  19.         "snapshot": "false",
  20.         "db": "inventory",
  21.         "table": "products",
  22.         "server_id": 223344,
  23.         "gtid": null,
  24.         "file": "mysql-bin.000003",
  25.         "pos": 2090,
  26.         "row": 0,
  27.         "thread": 2,
  28.         "query": null
  29.     },
  30.     "op": "u",
  31.     "ts_ms": 1589362330904,
  32.     "transaction": null
  33. }

Note: please refer to Debezium documentation 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.17. 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
  1. env {
  2.     parallelism = 1
  3.     job.mode = "BATCH"
  4. }
  6. source {
  7.   Kafka {
  8.     bootstrap.servers = "kafkaCluster:9092"
  9.     topic = "products_binlog"
  10.     result_table_name = "kafka_name"
  11.     start_mode = earliest
  12.     schema = {
  13.       fields {
  14.            id = "int"
  15.            name = "string"
  16.            description = "string"
  17.            weight = "string"
  18.       }
  19.     }
  20.     debezium_record_include_schema = false
  21.     format = debezium_json
  22.   }
  24. }
  26. transform {
  27. }
  29. sink {
  30.   Kafka {
  31.     bootstrap.servers = "kafkaCluster:9092"
  32.     topic = "consume-binlog"
  33.     format = debezium_json
  34.   }
  35. }