Bug report

What Debezium connector do you use and what version?

Latest and main branch

What is the connector configuration?

"transforms": "transform-name",
"transforms.transform-name.type": "io.debezium.transforms.partitions.PartitionRouting",
"transforms.transform-name.partition.hash.function": "murmur",
"transforms.transform-name.partition.topic.num": "3",
"transforms.transform-name.partition.payload.fields": "change.id",

What is the captured database version and mode of depoyment?

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

Amazon RDS for Postgres

What behaviour do you expect?

When using the `PartitionRouting` transform, tombstone messages should be treated in the same way as normal messages.

What behaviour do you see?

Tombstone messages are excluded from the partition routing algorithm completely.

Tombstones should not be ignored and should be processed in the same way as other messages.

https://github.com/debezium/debezium/blob/main/debezium-core/src/main/java/io/debezium/transforms/partitions/PartitionRouting.java#L155-L158

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

Yes, issue also exists on latest main branch.

Implementation ideas (optional)

Provide a flag which allows to get the values from the key instead of getting it from the value. This would allow tombstone partitions to be calculated correctly.