-
Bug
-
Resolution: Duplicate
-
Blocker
-
None
-
2.4.0.Final
-
None
-
False
-
None
-
False
-
Critical
Hi, When I run a blocking snapshot with kafka signal, Debezium did not stop streaming, Incremental data was still collected, including snapshot tables and other tables, If data modification occurs at the same time, and the snapshot of the same data is later than the streaming, the final streaming data will be overwritten, as follows:
Bug report
For bug reports, provide this information, please:
What Debezium connector do you use and what version?
2.4.0.Final
What is the connector configuration?
{
"name": "mysql_cdc_test_10000000000003",
"config":
}
What is the captured database version and mode of depoyment?
5.7
What behaviour do you expect?
Stop streaming of snapshot table
What behaviour do you see?
If data modification occurs at the same time, and the snapshot of the same data is later than the streaming, the final streaming data will be overwritten
Do you see the same behaviour using the latest relesead 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)
<Your answer>
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>
- duplicates
-
DBZ-7035 Blocking ad-hoc snapshot is not really blocking for MySQL
- Closed