anchor.diff:  
   |6
   |`after`
  -|An optional field that specifies the state of the document after the event occurred. In this example, the `after` field contains the values of the new document's `\_id`, `first_name`, `last_name`, and `email` fields. The `after` value is always a string. By convention, it contains a JSON representation of the document. MongoDB's oplog entries contain the full state of a document only for _create_ events and also for `update` events, when the `capture.mode` option is set to `change_streams_update_full`; in other words, a _create_ event is the only kind of event that contains an _after_ field, when the `capture.mode` option is set either to `oplog` or `change_streams`.
  +|An optional field that specifies the state of the document after the event occurred. In this example, the `after` field contains the values of the new document's `\_id`, `first_name`, `last_name`, and `email` fields. The `after` value is always a string. By convention, it contains a JSON representation of the document. MongoDB's oplog entries contain the full state of a document only for _create_ events and also for `update` events, when the `capture.mode` option is set to `change_streams_update_full`; in other words, a _create_ event is the only kind of event that contains an _after_ field, when the `capture.mode` option is set either to `change_streams`.
   
   |7
   |`source`
  
positive.code: The {prodname} connector watches the stream and delivers the changes downstream.
  And, when the connector sees a replica set for the first time, it looks at the oplog to get the last recorded transaction and then performs a snapshot of the primary's databases and collections.
  When all the data is copied, the connector then creates a change stream from the position it read earlier from the oplog.
  
  This is the recommended mode starting with MongoDB 4.x.
  
  [WARNING]
  ====
  Both capture modes use different values stored in offsets that allow them to resume streaming from the last position seen after a connector restart.
  Thus it is not possible to switch from the change streams mode to the oplog mode.
  To prevent any inadvertent capture mode changes, the connector has a built-in safety check.
  
  When the connector is started it checks the stored offsets.
  If the original capture mode was oplog-based and the new mode is change streams based, then it will try to migrate to change streams.
  If the original capture mode was change streams based, it will keep using change streams, also if the new mode is oplog-based, and a warning about this will be emitted to the logs.
  ====
  
  As the MongoDB connector processes changes, it periodically records the position in the oplog/stream where the event originated.
  When the connector stops, it records the last oplog/stream position that it processed, so that upon restart it simply begins streaming from that position.
  
negative.code: === Logical connector name
  
  The connector configuration property `mongodb.name` serves as a _logical name_ for the MongoDB replica set or sharded cluster.
  The connector uses the logical name in a number of ways: as the prefix for all topic names, and as a unique identifier when recording the change stream position of each replica set.
  
  You should give each MongoDB connector a unique logical name that meaningfully describes the source MongoDB system.
  We recommend logical names begin with an alphabetic or underscore character, and remaining characters that are alphanumeric or underscore.
  