anchor.diff:  transforms.unwrap.type=io.debezium.transforms.ExtractNewRecordState
   transforms.unwrap.drop.tombstones=false
   transforms.unwrap.delete.handling.mode=rewrite
  +transforms.unwrap.add.source.fields=table,lsn
   ----
   
   === Record filtering for delete records
  
positive.code: 
  Debezium provides https://kafka.apache.org/documentation/#connect_transforms[a single message transformation] that crosses the bridge between the complex and simple formats, the https://github.com/debezium/debezium/blob/master/debezium-core/src/main/java/io/debezium/transforms/ExtractNewRecordState.java[ExtractNewRecordState] SMT.
  
  The SMT provides two main functions.
  It
  
  * extracts the `after` field from change events and replaces the original event just with this part
  * optionally filters delete and tombstone records, as per the capabilities and requirements of downstream consumers
  
  The SMT can be applied either to a source connector (Debezium) or a sink connector.
  We generally recommend to apply the transformation on the sink side as it means that the messages stored in Apache Kafka will contain the whole context.
  
negative.code: |`delete.handling.mode`
  |`drop`
  |The SMT can `drop` (the default), `rewrite` or pass delete events (`none`). The rewrite mode will add a `__deleted` column with true/false values based on record operation.
  
  |`add.source.fields`
  |
  |Fields from the change event's `source` structure to add as metadata (prefixed with "__") to the flattened record
  |=======================
  