-
Sub-task
-
Resolution: Done
-
Major
-
None
-
None
The most probable reason is the call of io.debezium.connector.mysql.BinlogReaderIT.filterAtLeast(int, long, TimeUnit). It is not guaranteed that all events have not been already filtered when the metrics is read for the first time. To make it correct iti is necessary to
1) Read the filtered metrics
2) Generate 35 changes
3) Compare with expected number
This is the only reliable way