anchor.diff:  
   |1
   |`schema`
  -|The first `schema` field is part of the event key. It specifies a Kafka Connect schema that describes what is in the event key's `payload` portion. In other words, the first `schema` field describes the structure of the primary key, or the unique key if the table does not have a primary key, for the table that was changed. 
  -
  -Rarely, converter configuration overrides the key column with some other structure. In this case, the first schema field describes that structure.
  +|The first `schema` field is part of the event key. It specifies a Kafka Connect schema that describes what is in the event key's `payload` portion. In other words, the first `schema` field describes the structure of the primary key, or the unique key if the table does not have a primary key, for the table that was changed. +
  + +
  +It is possible to override the table's primary key by setting the {link-prefix}:{link-mysql-connector}#mysql-property-message-key-columns[`message.key.columns` connector configuration property]. In this case, the first schema field describes the structure of the the key identified by that property.
   
   |2
   |`payload`
  
positive.code:       "name": "mysql-server-1",
        "connector": "mysql",
        "name": "mysql-server-1",
        "ts_ms": 1465581,
        "snapshot": false,
        "db": "inventory",
        "table": "customers",
  
negative.code:       "version": "{debezium-version}",
        "connector": "mysql",
        "name": "mysql-server-1",
        "ts_sec": 0,
        "snapshot": false,
        "db": "inventory",
        "table": "customers",
  