anchor.diff:  	"op": "u",
   	"source": {
   		...
  -	}
  -	"ts_ms": "..."
  -	"before": {
  -		"field1", "oldvalue1",
  -		"field2", "oldvalue2"
  -	}
  -	"after": {
  -		"field1", "newvalue1",
  -		"field2", "newvalue2"
  +	},
  +	"ts_ms" : "...",
  +	"before" : {
  +		"field1" : "oldvalue1",
  +		"field2" : "oldvalue2"
  +	},
  +	"after" : {
  +		"field1" : "newvalue1",
  +		"field2" : "newvalue2"
   	}
   }
   ----
  
positive.code: ====
  
  == Configuration options
  [cols="35%a,10%a,55%a",width=100,options="header,footer",role="table table-bordered table-striped"] 
  |======================= 
  |Property 
  |Default 
  |Description 
   
  |`drop.tombstones` 
  |`true` 
  |SMT removes the tombstone generated by Debezium from the streeam.
  
  |`drop.deletes` 
  |`true` 
  |SMT removes the `d` record generated by Debezium and converted to tombstone by SMT) from the stream.
  |=======================
  
  
negative.code: 
  [NOTE]
  ====
  This SMT is supported only for the SQL database connectors, it does not work with the MongoDB connector.
  ====
  
  Debezium generates a data change in a form of a complex message structure.
  The message consists of three parts:
  
  * operation and metadata
  * the row data before change
  * the row data after change
  
  E.g. the general message structure for an `update` change looks like this:
  
  [source,json,indent=0]
  ----
  