Sink connector's dependency on tombstone will cause dataloss

[fourpointfour]

The sink connector relies on tombstone records to process deletes for the target table. However, there’s a chance where the Debezium source connectors might cause a loss of tombstone records (being discussed in Debezium forum) - when that happens, the sink connector will also not process deletes in the target table and hence the data loss.

The problem basically arises because the sink connector relies on the tombstone records to process deletes instead of the op: d events published by Debezium source connectors.

I wanted to ask if we can collaborate and figure out a way to process deletes without relying on tombstone records.

Initiated a discussion on community: https://confluentcommunity.slack.com/archives/C49L0V3L7/p1747028710967459