Debezium may lose some multi-row events if failure happens at exactly the wrong time

A MySQL insert, update, or delete event can contain multiple rows. When the MySQL connector processes these multi-row events, it incorrectly sets the position in the offset so that if the connector fails after Kafka Connect has flushed the offset for some of the rows but not all, then upon restart the connector will begin at the next event, thereby missing some of the rows.