Heartbeat table and it's relation with topic.heartbeat.prefix

[Ashish Tiwari]

Hey,

I’ve been setting up the Debezium PostgreSQL connector, and I’ve got a heartbeat table configured. I added it to the publication and included it in my table.include.list. Everything seems to be working, but I’m confused about this topic.heartbeat.prefix property. Why do I need it? I noticed it creates two topics (regular topic and another one using that prefix)—one with the regular name and another with the prefix I set. Is that expected behavior or am I doing something wrong entirely?

I’ve got my Debezium config set up like this:

"table.include.list": "cdc.heartbeat, ...",
"heartbeat.interval.ms": "90000"
"heartbeat.action.query": "update cdc.heartbeat set id = id+1"
"topic.heartbeat.prefix": "cdc-HEARTBEAT"

Thanks,
At.

[jiri.p...@gmail.com]

Hi,

yes that's correct. The first topic comes from that update of heartbeat table and the other topic contains special heartbeat message.

Without heartbeat.action.query you'll see only the second topic.

Jiri