anchor.diff:  
   |===
   
  +ifdef::community[]
  +
  +// Type: continue
  +[id="mysql-snapshot-events"]
  +=== Operation type for snapshot events
  +The MySql connector emits snapshot events using the "r" operation type (`READ`). In case you want the connector to emit snapshot events as "c" events (`CREATE`, as done incorrectly in earlier versions), this can be achieved using a Simple Message Transforms (SMT).
  +Configure the Debezium `ReadToInsertEvent` SMT by adding the SMT configuration details to your connector’s configuration.
  +
  +An example of the configuration is this:
  +
  +----
  +transforms=snapshotasinsert,...
  +transforms.snapshotasinsert.type=io.debezium.connector.mysql.transforms.ReadToInsertEvent
  +----
  +endif::community[]
  +
   // Type: concept
   // ModuleID: default-names-of-kafka-topics-that-receive-debezium-mysql-change-event-records
   // Title: Default names of Kafka topics that receive {prodname} MySQL change event records
  
positive.code: * <<mysql-primary-key-updates,Primary key updates>>
  * <<mysql-delete-events,_delete_ events>>
  * <<mysql-tombstone-events,Tombstone events>>
  * <<mysql-snapshot-events, Snapshot events>>
  
  // Type: continue
  [id="mysql-create-events"]
  
negative.code: === Tombstone events
  When a row is deleted, the _delete_ event value still works with log compaction, because Kafka can remove all earlier messages that have that same key. However, for Kafka to remove all messages that have that same key, the message value must be `null`. To make this possible, after {prodname}’s MySQL connector emits a _delete_ event, the connector emits a special tombstone event that has the same key but a `null` value.
  
  // Type: reference
  // ModuleID: how-debezium-mysql-connectors-map-data-types
  // Title: How {prodname} MySQL connectors map data types
  