anchor.diff:  }
   ----
   
  -The emitted event has a slightly different set of values that the legacy oplog output.
  +The emitted event has a slightly different set of values than the legacy oplog output.
   As shown above, the event does not have a value in the after, patch, or filter fields.
   Instead, the event relies on describing the changes to the document's fields in the `updateDescription` structure.
   While this provides a bit more detail about values that may have been set and even unset due to an update,
  
positive.code: 
  +++<!-- more -->+++
  
  == MongoDB Change Stream Support
  
  MonogoDB https://docs.mongodb.com/manual/changeStreams/[change streams] allow an application or client access to real-time change data capture events without the complexity of tailing the oplog.
  This functionality was first introduced by the MongoDB engine in version 3.6; however the functionality was limited.
  Starting with MongoDB 4.0, change streams now captures changes across a database, replica set, or even a sharded cluster.
  
  Debezium added change stream support to:
  
  * Enable compatibility with MongoDB 5 (not yet tested, see future work below).
  * Possibly become a replacement for oplog reading.
  * Provide full document output in update events (see below).
  
  In order to use change stream support with Debezium, you must use MongoDB 4.0 or later.
  
  
negative.code: Specifies that changes should  be captured by tailing the oplog; this is the legacy behavior.
  `change_streams`::
  Specifies that changes should be captured by using MongoDB change streams.
  Updates will not contain the full message; only changed fields are part of the event.
  `change_streams_update_full`::
  Specifies that changes should be captured by using MongoDB change streams.
  Updates will contain a full snapshot of the current record in the event.
  