anchor.diff:      "payload": {
         "op": "d", // <1>
         "ts_ms": 1465495462115, // <2>
  +      "before":"{\"_id\": {\"$numberLong\": \"1004\"},\"first_name\": \"Anne Marie\",\"last_name\": \"Kretchmar\",\"email\": \"annek@noanswer.org\"}",// <3>
         "source": { // <4>
           "version": "{debezium-version}",
           "connector": "mongodb",
  
positive.code: [id="mongodb-delete-events"]
  === _delete_ events
  
  The value in a _delete_ change event has the same `schema` portion as _create_ and _update_ events for the same collection. The `payload` portion in a _delete_ event contains values that are different from _create_ and _update_ events for the same collection. In particular, a _delete_ event contains neither an `after` value nor a `patch` or `updateDescription` values. Here is an example of a _delete_ event for a document in the `customers` collection:
  
  [source,json,indent=0,subs="+attributes"]
  ----
  
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",
  