anchor.diff:  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 for a variety of reasons which include:
  -
  -* Allows use with MongoDB 5 (not yet tested, see future work below).
  -* With it being the new default, may become a replacement for oplog reading.
  -* Has the ability to provide full document output in update events (see below).
  +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.
   
  
positive.code: ]);
  ----
  
  This will generate a change event but as you'll see if you inspect the topic, the contents of the event are not all that different from Debezium 1.7 or before.
  Since the event is an insert, all field values are contained within the emitted event.
  
  Where we see the capture mode differences in action is during update operations.
  Now modify the customer's first and last name again using the MongoDB shell with this command:
  
  [source,shell]
  ----
  
negative.code:     } });
  ----
  
  This modifies the first and last name of the customer with id `1005`.
  The following sections show what each event will look like for the given capture mode.
  
  ==== Oplog
  
  