-
Bug
-
Resolution: Duplicate
-
Major
-
3.2.0.Final
-
None
-
False
-
-
False
-
-
When DBZ-9118 was implemented, the reference code for feasibility was based solely on MySQL/MariaDB, but the change made in Debezium 3.2 was in the base source task and applied to all connectors. This has caused the following SQL Server test to fail repeatedly due to this change.
2025-07-08T12:12:29.3425583Z [ERROR] SchemaHistoryTopicIT.schemaChangeAfterSnapshot:295->AbstractConnectorTest.assertConnectorIsRunning:1050 2025-07-08T12:12:29.3426651Z Expecting value to be true but was false expected:<[tru]e> but was:<[fals]e>
and also
2025-07-08T12:12:29.3430264Z [ERROR] NotificationsIT>AbstractNotificationsIT.sinkNotificationWillCorrectlySaveOffsetAfterSnapshot:277->AbstractConnectorTest.waitForStreamingRunning:1420 » ConditionTimeout Condition with alias 'Streaming was not started on time' didn't complete within 5 minutes because condition io.debezium.embedded.AbstractConnectorTest$$Lambda/0x00007efcec3ec460 was not fulfilled.
and also
2025-07-08T12:12:29.3430264Z [ERROR] NotificationsIT>AbstractNotificationsIT.sinkNotificationWillCorrectlySaveOffsetAfterSnapshot:277->AbstractConnectorTest.waitForStreamingRunning:1420 » ConditionTimeout Condition with alias 'Streaming was not started on time' didn't complete within 5 minutes because condition io.debezium.embedded.AbstractConnectorTest$$Lambda/0x00007efcec3ec460 was not fulfilled.
and also
2025-07-08T12:12:29.3420079Z [ERROR] IncrementalSnapshotIT>AbstractIncrementalSnapshotTest.snapshotNewTableWithoutCapturedSchema:873->AbstractSnapshotTest.startConnector:276->AbstractSnapshotTest.startConnector:283->AbstractSnapshotTest.waitForConnectorToStart:301->AbstractConnectorTest.assertConnectorIsRunning:1050 2025-07-08T12:12:29.3421808Z Expecting value to be true but was false expected:<[tru]e> but was:<[fals]e>
- is caused by
-
DBZ-9118 Fix warn log if snapshot mode when needed is required but is not set
-
- Closed
-
- links to
-
RHEA-2025:154266
Red Hat build of Debezium 3.2.4 release