Debezium series: MySQL tombstone event

One 、mysql tombstone events

• The deletion operation is represented by the deletion event and the subsequent tombstone event .
• Only one delete event is sent .
• After deleting the source record , issue tombstone event （ Default behavior ） allow Kafka Completely delete all events related to the key of the Deleted Row , In case the topic enables log compression .

The format of tombstone event data is as follows , Include primary key id but value It's a null value ：
ConsumerRecord(topic=‘debezium-prod-optics-prod_1h.optics_prod.optics_order’, partition=2, offset=3636705, timestamp=1656746091521, timestamp_type=0, key=b’{“schema”:{“type”:“struct”,“fields”:[{“type”:“int32”,“optional”:false,“field”:“order_id”}],“optional”:false,“name”:“debezium_prod_optics_prod_1h.optics_prod.optics_order.Key”},“payload”:{“order_id”:2752094}}', value=None, headers=[], checksum=None, serialized_key_size=223, serialized_value_size=-1, serialized_header_size=-1)

Two 、debezium Parameters control whether tombstone events are generated

• tombstones.on.delete
• stay connector Set this parameter in the configuration , Parameter is true, The deletion operation is represented by the deletion event and the subsequent tombstone event .
• Parameter is false, Only one delete event is sent .
• The default is true