What Debezium connector do you use and what version?

3.0.1.Final, 3.0.2.Final

What is the connector configuration?

{
"name": "postgres-source",
"config":

{ "name": "postgres-source", "connector.class": "io.debezium.connector.postgresql.PostgresConnector", "tasks.max": 1, "database.hostname": "pgsql", "database.port": 5432, "database.user": "dbzuser", "database.password": "dbzpswd", "database.dbname": "testdb", "plugin.name": "pgoutput", "publication.name": "dbz_publication", "publication.autocreate.mode": "filtered", "slot.name": "debezium_slot", "slot.drop.on.stop": "true", "tombstones.on.delete": "true", "topic.prefix": "postgres", "table.include.list": "example.origin_table", "replica.identity.autoset.values": "example.origin_table:FULL", "key.converter": "org.apache.kafka.connect.json.JsonConverter", "key.converter.schemas.enable": "true", "value.converter": "org.apache.kafka.connect.json.JsonConverter", "value.converter.schemas.enable": "true", "transforms": "Unwrap", "transforms.Unwrap.type": "io.debezium.transforms.ExtractNewRecordState", "transforms.Unwrap.delete.tombstone.handling.mode": "rewrite-with-tombstone" }

}

What is the captured database version and mode of deployment?

Postgres 16.5 in docker container

What behavior do you expect?

JDBC sink-connector delete records in target table matching tombstone messages

What behavior do you see?

JDBC sink-connector leaves deleted rows when using ExtractNewRecordState with "rewrite-with-tombstone"

Origin table after DML

Result in target table

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

3.0.1.Final, 3.0.2.Final

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

Yes, connect-service.log in attached archive.

How to reproduce the issue using our tutorial deployment?

1. Unpack attached archive
2. Start docker-compose.yml from /compose folder
3. Add source connector from /connectors/postgres-source-err.json
4. Add sink connector from /connectors/postgres-sink.json
5. Execute dml script from /sql/postgresql/dml.sql
6. Compare tables example.origin_table and example.copyof_origin_table