In order to make your issue reports as actionable as possible, please provide the following information, depending on the issue type.

Bug report

For bug reports, provide this information, please:

What Debezium connector do you use and what version?

debezium-connector-mysql: 1.5.4-Final

What is the connector configuration?

// code placeholder

"connector.class": "io.debezium.connector.mysql.MySqlConnector"
"bigint.unsigned.handling.mode": "precise"
"database.user": "secret"
"offset.storage": "org.apache.kafka.connect.storage.FileOffsetBackingStore"
"offset.storage.file.filename": "/tmp/offsets.dat"
"database.server.name": "mysql_binlog_source"
"include.schema.changes": "false"
"database.port": "secret"
"table.whitelist": "test.simple"
"offset.flush.interval.ms": "60000"
"tombstones.on.delete": "false"
"database.hostname": "secret"
"database.password": "secret"
"name": "engine"
"database.history.skip.unparseable.ddl": "true"
"database.whitelist": "test"
"database.history.instance.name": "ca40b12a-7fd8-480a-8f8d-3ed463138315"
"snapshot.mode": "initial"
"database.history": "io.debezium.relational.history.FileDatabaseHistory"
"database.history.file.filename": "/tmp/dbhistory.dat"

What is the captured database version and mode of depoyment?

mysql: 5.6.51-log

What behaviour do you expect?

Debezium provides exactly once delivery of every change event record.

What behaviour do you see?

While reading snapshots, MySQL Connector will not implicitly starts the transaction until the select query is executed.

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

(Ideally, also verify with latest Alpha/Beta/CR version)

Yes, I repeated the same error in the latest relesead version 2.1.0.Beta1.

Feature request or enhancement

For feature requests or enhancements, provide this information, please:

Implementation ideas (optional)

start transaction explicitly while reading snapshots.