Like debezium and canal, changes are delivered separated by tables. Usually, one mysql transaction contains several db changes. If I package these db changes in one kafka message body, is there a way that flink can guarantee transaction atomicity. I googled and found sth like this, https://www.ververica.com/blog/serializable-acid-transactions-on-streaming-data, but it is two years earlier, and nothing further.
