-
Bug
-
Resolution: Done
-
Minor
-
None
-
None
What Debezium connector do you use and what version?
MySQL connector and Debezium 2.x.x
What is the connector configuration?
snapshot.mode = initial_only, everything else is irrelevant.
What is the captured database version and mode of depoyment?
On premise MySQL 5.7 server.
What behaviour do you expect?
When running the connector with the initial_only snapshot mode, the connector stops after the snapshot is performed. Since the snapshot is a simple SELECT query that doesn't require the bin log, we don't care about the bin log being enabled and configured properly. This is only a concern for MySQL 5.7 as version 8 works off the shelf.
What behaviour do you see?
Fails with when trying to fetch the bin log file through:
"SHOW MASTER STATUS"
Do you see the same behaviour using the latest released Debezium version?
Yes.
Do you have the connector logs, ideally from start till finish?
(You might be asked later to provide DEBUG/TRACE level log)
I do but they wouldn't be required as I know where it fails and intend to supply a fix.
How to reproduce the issue using our tutorial deployment?
No need.
- clones
-
DBZ-6265 Postgres connector doesn't need logical WAL level when snapshotting only
- Closed
- links to
-
RHEA-2023:120698 Red Hat build of Debezium 2.3.4 release