I am experiencing a unexpected behavior when using postgres - debezium server - pulsar queue setup. When some db record is deleted pulsar producer creates the delete event which is corrent but right after that it also creates message with empty payload resulting in EOF when parsing. The empty message has the same key as the delete event containing id of the record that was deleted

Bug report

I am using debezium/server:2.7.3.Final docker image inside k8.

What Debezium connector do you use and what version?

io.debezium.connector.postgresql.PostgresConnector

What is the connector configuration?

debezium.source.topic.prefix=CHANGELOG
debezium.format.value=json
debezium.source.connector.class=io.debezium.connector.postgresql.PostgresConnector
debezium.source.offset.storage.file.filename=/data/offsets.dat
debezium.source.offset.storage=org.apache.kafka.connect.storage.FileOffsetBackingStore
debezium.source.offset.flush.interval.ms=0
debezium.source.database.hostname=postgresql-db
debezium.source.database.port=5432
debezium.source.database.user=postgres
debezium.source.database.password=postgres
debezium.source.database.dbname=db
debezium.source.database.server.name=dev
debezium.source.plugin.name=pgoutput
debezium.source.slot.drop.on.stop=true
debezium.source.snapshot.mode=never

What is the captured database version and mode of deployment?

(E.g. on-premises, with a specific cloud provider, etc.)

Postgres 16.3 deployed using bitnami helm chart

What behavior do you expect?

1 event after db record is deleted

What behavior do you see?

1 delete event + 1 empty message created right after the delete event. this message has no payload, only think it has is the key containing id of entity that was deleted

Do you see the same behaviour using the latest released Debezium version?

(Ideally, also verify with latest Alpha/Beta/CR version)

yes

Do you have the connector logs, ideally from start till finish?

(You might be asked later to provide DEBUG/TRACE level log)

no error logs are visible