anchor.diff:          "topics": "customers",
           "connection.url": "jdbc:postgresql://postgres:5432/inventory?user=postgresuser&password=postgrespw",
           "transforms": "unwrap",                                                  (1)
  -        "transforms.unwrap.type": "io.debezium.transforms.UnwrapFromEnvelope",   (1)
  +        "transforms.unwrap.type": "io.debezium.transforms.ExtractNewRecordState",(1)
           "auto.create": "true",                                                   (2)
           "insert.mode": "upsert",                                                 (3)
           "pk.fields": "id",                                                       (4)
  
positive.code: [source,indent=0]
  ----
          "transforms": "unwrap",
          "transforms.unwrap.type": "io.debezium.transforms.UnwrapFromEnvelope",
  ----
  
  === Delete records
  
negative.code: 
  While we think it's actually a great thing that Debezium CDC connectors provide as much detail as possible, we also make it easy for you to transform Debezium's _"envelope"_ format into the _"row"_ format that is expected by many other connectors.
  Debezium provides a bridge between those two formats in a form of a https://cwiki.apache.org/confluence/display/KAFKA/KIP-66%3A+Single+Message+Transforms+for+Kafka+Connect[single message transform].
  The `ExtractNewRecordState` transformation automatically extracts a new row record and thus effectively _flattens_ the complex record into a simple one consumable by other connectors.
  
  You can use this SMT on the source connector to transform the message _before_ it is written to Kafka, or you can instead store the source connector's richer _"envelope"_ form of the message in Kafka and use this SMT on the sink connector to transform the message _after_ it is read from Kafka and before it is passed to the sink connector.
  Both options work, and it just depends on whether you find the envelope form of the message useful for other purposes.
  