-
Bug
-
Resolution: Can't Do
-
Major
-
None
-
2.3.2.Final
-
None
-
False
-
-
False
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:
When I update debezium to new version I expect it to continue synchronization, but it does not find offset and starts synchronization from 0 offset
What Debezium connector do you use and what version?
Mysql connector update from 1.5.2 to 2.3.2
What is the connector configuration?
old 1.5.2 configuration
debezium.sink.type=pubsub
debezium.source.offset.storage.file.filename=data/offsets.dat
debezium.source.database.history=io.debezium.relational.history.FileDatabaseHistory
debezium.source.database.history.file.filename=data/db-history.dat
debezium.source.database.history.skip.unparseable.ddl=true
debezium.transforms=singleTopic
debezium.transforms.singleTopic.type=io.debezium.transforms.ByLogicalTableRouter
debezium.transforms.singleTopic.topic.regex=([^.]+).*
debezium.transforms.singleTopic.topic.replacement=$1
debezium.sink.pubsub.project.id
debezium.source.connector.class
debezium.source.database.hostname
debezium.source.database.port
debezium.source.database.user
debezium.source.database.password
debezium.source.database.server.name=debezium_mysql_xxx debezium.source.database.include.list
debezium.source.table.exclude.list
new 2.3.2 configuration
debezium.sink.type=pubsub
debezium.source.offset.storage.file.filename=data/offsets.dat
debezium.source.schema.history.internal=io.debezium.storage.file.history.FileSchemaHistory
debezium.source.schema.history.internal.file.filename=data/db-history.dat
debezium.source.schema.history.internal.skip.unparseable.ddl=true
debezium.transforms=singleTopic
debezium.transforms.singleTopic.type=io.debezium.transforms.ByLogicalTableRouter
debezium.source.database.server.id=199999
debezium.transforms.singleTopic.topic.regex=([^.]+).*
debezium.transforms.singleTopic.topic.replacement=$1
debezium.sink.pubsub.project.id
debezium.source.topic.prefix=debezium_mysql_xxx
debezium.source.connector.class
debezium.source.database.hostname
debezium.source.database.port
debezium.source.database.user
debezium.source.database.password
debezium.source.database.server.name=debezium_mysql_xxx debezium.source.database.include.list
debezium.source.table.exclude.list
What is the captured database version and mode of depoyment?
(E.g. on-premises, with a specific cloud provider, etc.)
MySQL 8.0, Kubernetes cluster statefulset, GKE
What behaviour do you expect?
Synchronization will continue from the saved offset
What behaviour do you see?
Synchronization starts over
Do you see the same behaviour using the latest relesead Debezium version?
(Ideally, also verify with latest Alpha/Beta/CR version)
Checked only 2.3.0-2.3.2 Final
Do you have the connector logs, ideally from start till finish?
(You might be asked later to provide DEBUG/TRACE level log)
{"timestamp":"2023-08-08T11:20:14.738Z","sequence":120,"loggerClassName":"org.slf4j.impl.Slf4jLogger","loggerName":"io.debezium.connector.common.BaseSourceTask","level":"INFO","message":"No previous offsets found","threadName":"pool-7-thread-1","threadId":23,"mdc":{},"ndc":"","hostName":"debezium-mysql-xxx-0","processName":"io.debezium.server.Main","processId":1}
How to reproduce the issue using our tutorial deployment?
<Your answer>
Feature request or enhancement
For feature requests or enhancements, provide this information, please:
Which use case/requirement will be addressed by the proposed feature?
<Your answer>
Implementation ideas (optional)
<Your answer>
- impacts account
-
-
- Closed
-
