Which use case/requirement will be addressed by the proposed feature?

When binlog compression is used, binary columns are mapped to a String. So a UUID that is saved in a binary(16) column is mapped to a String, and mapping that back to a UUID result in a totally different UUID. This is a problem in the mysql-binlog-connector-java dependency, for which I created an issue on their GitHub (https://github.com/osheroff/mysql-binlog-connector-java/issues/118), but there is not much activity there.

As a workaround, it is possible to use the custom row deserializers that are already part of the Debezium code. For this, the TransactionPayloadEventDataDeserializer has to be subclassed.

Implementation ideas

https://github.com/debezium/debezium/pull/4759