anchor.diff:  As mentioned above, the connector tasks always use the replica set's primary node to stream changes from the oplog, ensuring that the connector sees the most up-to-date operations as possible and can capture the changes with lower latency than if secondaries were to be used instead. When the replica set elects a new primary, the connector immediately stops streaming changes, connects to the new primary, and starts streaming changes from the new primary node at the same position. Likewise, if the connector experiences any problems communicating with the replica set members, it tries to reconnect, by using exponential backoff so as to not overwhelm the replica set, and once connected it continues streaming changes from where it last left off. In this way, the connector is able to dynamically adjust to changes in replica set membership and automatically handle communication failures.
   
   To summarize, the MongoDB connector continues running in most situations. Communication problems might cause the connector to wait until the problems are resolved.
  +
  +// Type: concept
  +[[mongodb-pre-image-support]]
  +=== Pre-image support
  +Starting in MongoDB 6.0, you can configure change stream to emit pre-image to populate the `before` field for Mongo change events. To utilize pre-image, you need to first enable `changeStreamPreAndPostImages` for a collection using
  +`db.createCollection()`, `create`, or `collMod`. And configure `capture.mode` as one of the `*_with_pre_image` options.
  +
  +[NOTE]
  +.Size limits on Mong change stream events
  +====
  +Since the size of Mongo change stream event is limited to 16 megabytes, enabling pre-image will increase the likelihood of hitting this limit and cause failure. To avoid that, please refer to Mongo's https://www.mongodb.com/docs/manual/changeStreams/#change-streams-with-document-pre--and-post-images/[official documentation] for recommendation and details.
  +====
   
   // Type: concept
   // ModuleID: default-names-of-kafka-topics-that-receive-debezium-mongodb-change-event-records
  
positive.code:       },
      "payload": { // <5>
        "after": "{\"_id\" : {\"$numberLong\" : \"1004\"},\"first_name\" : \"Anne\",\"last_name\" : \"Kretchmar\",\"email\" : \"annek@noanswer.org\"}", // <6>
        "patch": null,
        "source": { // <7>
          "version": "{debezium-version}",
          "connector": "mongodb",
  
negative.code:     "payload": {
        "op": "u", // <1>
        "ts_ms": 1465491461815, // <2>
        "before":"{\"_id\": {\"$numberLong\": \"1004\"},\"first_name\": \"unknown\",\"last_name\": \"Kretchmar\",\"email\": \"annek@noanswer.org\"}", // <3>
        "after":"{\"_id\": {\"$numberLong\": \"1004\"},\"first_name\": \"Anne Marie\",\"last_name\": \"Kretchmar\",\"email\": \"annek@noanswer.org\"}", // <4>
        "updateDescription": {
          "removedFields": null,
          "updatedFields": "{\"first_name\": \"Anne Marie\"}", // <5>
          "truncatedArrays": null
        },
        "source": { // <6>
          "version": "{debezium-version}",
          "connector": "mongodb",
          "name": "fulfillment",
  