0
votes

I did not find any documentation about how the Kafka message timestamp is set by Debezium - and if it is set at all.

From comparing the values the Kafka message timestamp is always behind the timestamp of the change to the database table (source.ts_ms), and also behind the time the change got processed by Debezium (ts_ms). This suggests that the Kafka message timestamp is just the one that is set to ingestion time by the Kafka broker.

Does anybody knows some details about if and how Debezium sets the Kafka message timestamp in the sink topic it populates?

I am using the Debezium connector for SQL server for the case that this makes a difference.

2
No, not yet - I hoped that others already did :-) - anekdoti

2 Answers

0
votes

Worth checking the source.timestamp.mode parameter. As per documentation (liked before), its default value commit should set the ts_ms to the time when the record was committed to the database.

0
votes

Debezium does not set neither Kafka Connect timestamp nor Kafka message timestamp. The former is left empty, the latter is managed by Kafka Connect.