-
Bug
-
Resolution: Not a Bug
-
Major
-
1.8.0.Final
-
None
-
False
-
False
-
The documentation on the MongoDB connector was not fully updated to reflect the change in Debezium 1.8 from oplog to change streams.
In particular, this section which explains how the connector actually works is really lacking in v1.8.
This is important because the change makes me question how Debezium can ensure that each oplog row becomes an event: in 1.7, the position in the oplog was saved to track this. In 1.8, we are presumably relying on Mongo to take care of this - but I want to know for sure.
- relates to
-
DBZ-4339 MongoDB connector to use secondary node
- Closed