anchor.diff:  
   |2
   |`name`
  -a|In the `schema` section, each `name` field specifies the schema for a field in the value's payload. In this example: 
  -
  -* `mysql-server-1.inventory.customers.Value` is the schema for the payload's `before` and `after` fields. This schema is specific to the `customers` table.
  -
  -* `io.debezium.connector.mysql.Source` is the schema for the payload's `source` field. This schema is specific to the MySQL connector. The connector uses it for all events that it generates. 
  -
  -* `mysql-server-1.inventory.customers.Envelope` is the schema for the overall structure of the payload, where `mysql-server-1` is the connector name, `inventory` is the database, and `customers` is the table.
  -
  -ifdef::community[]
  +a|In the `schema` section, each `name` field specifies the schema for a field in the value's payload. +
  + +
  +`mysql-server-1.inventory.customers.Value` is the schema for the payload's `before` and `after` fields. This schema is specific to the `customers` table. +
  + +
   Names of schemas for `before` and `after` fields are of the form `_logicalName_._tableName_.Value`, which ensures that the schema name is unique in the database. This means that when using the {link-prefix}:{link-avro-serialization}[Avro converter], the resulting Avro schema for each table in each logical source has its own evolution and history.
  -endif::community[]
   
   |3
  +|`name`
  +|`io.debezium.connector.mysql.Source` is the schema for the payload's `source` field. This schema is specific to the MySQL connector. The connector uses it for all events that it generates. 
  +
  +|4
  +|`name`
  +|`mysql-server-1.inventory.customers.Envelope` is the schema for the overall structure of the payload, where `mysql-server-1` is the connector name, `inventory` is the database, and `customers` is the table.
  +
  +|5
   |`payload`
  -|The value's actual data. This is the information that the change event is providing. 
  -
  +|The value's actual data. This is the information that the change event is providing. +
  + +
   It may appear that the JSON representations of the events are much larger than the rows they describe. This is because the JSON representation must include the schema and the payload portions of the message.
   However, by using the {link-prefix}:{link-avro-serialization}[Avro converter], you can significantly decrease the size of the messages that the connector streams to Kafka topics.
   
  -|4
  +|6
   |`op`
   a| Mandatory string that describes the type of operation that caused the connector to generate the event. In this example, `c` indicates that the operation created a row. Valid values are: 
   
  
positive.code:       }
      ],
      "optional": false,
      "name": "mysql-server-1.inventory.customers.Envelope" // <2>
    },
    "payload": { // <3>
      "op": "c", // <4>
      "ts_ms": 1465491411815, // <5>
      "before": null, // <6>
      "after": { // <7>
        "id": 1004,
        "first_name": "Anne",
        "last_name": "Kretchmar",
        "email": "annek@noanswer.org"
      },
      "source": { // <8>
        "version": "{debezium-version}",
        "connector": "mysql",
        "name": "mysql-server-1",
  
negative.code: * `d` = delete
  * `r` = read (applies to only snapshots)
  
  |7
  |`ts_ms`
  a| Optional field that displays the time at which the connector processed the event. The time is based on the system clock in the JVM running the Kafka Connect task.
  
  |8
  |`before`
  | An optional field that specifies the state of the row before the event occurred. When the `op` field is `c` for create, as it is in this example, the `before` field is `null` since this change event is for new content. 
  
  |9
  |`after`
  | An optional field that specifies the state of the row after the event occurred. In this example, the `after` field contains the values of the new row's `id`, `first_name`, `last_name`, and `email` columns.
  
  |10
  |`source`
  a| Mandatory field that describes the source metadata for the event. This field contains information that you can use to compare this event with other events, with regard to the origin of the events, the order in which the events occurred, and whether events were part of the same transaction. The source metadata includes: 
  
  