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: The SMT by default filters out *BOTH* delete records as widely used sink connectors such as for JDBC do not support handling of tombstone records at this point.
  ====
  
  == Configuration options
  [cols="35%a,10%a,55%a",width=100,options="header,footer",role="table table-bordered table-striped"]
  |=======================
  
negative.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 three 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
  * optionally adds metadata fields from the change event's `source` field, prefixing them with "__" 
  
  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.
  