anchor.diff:      "filter": null,
       "updateDescription": {
         "removedFields": null,
  -      "updatedFields": "{\"first_name\": \"Bobby\"}",
  +      "updatedFields": "{\"first_name\": \"Bobby\", \"last_name\": \"Copper\"}",
         "truncatedArrays": null
       },
       "source": {
  -      "version": "1.8.0-SNAPSHOT",
  +      "version": "1.8.0.Alpha1",
         "connector": "mongodb",
         "name": "dbserver1",
         "ts_ms": 1635292448000,
  
positive.code:       ...
    },
    "payload": {
      "after": "{\"_id\": {\"$numberLong\": \"1005\"},\"first_name\": \"Bobby\",\"last_name\": \"Hopper\",\"email\": \"thebob@example.com\",\"unique_id\": {\"$binary\": \"KRywzYp5RneNu8DUmhQHAQ==\",\"$type\": \"04\"}}",
      "patch": null,
      "filter": null,
      "updateDescription": {
        "removedFields": null,
        "updatedFields": "{\"first_name\": \"Bobby\"}",
        "truncatedArrays": null
      },
      "source": {
        "version": "1.8.0-SNAPSHOT",
        "connector": "mongodb",
        "name": "dbserver1",
        "ts_ms": 1635292878000,
  
negative.code: 
  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 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).
  
  In order to use change stream support with Debezium, you must use MongoDB 4.0 or later.
  
  === Enablement
  