anchor.diff:        "file": "mysql-bin.000003",
         "pos": 154,
         "row": 0,
  -      "snapshot": true
  +      "snapshot": null,
  +      "query": "INSERT INTO customers (first_name, last_name, email) VALUES ('Anne', 'Kretchmar', 'annek@noanswer.org')"
       }
     }
   }
  
positive.code: ====
  The MySQL connector does not require MySQL to use GTIDs and GTID-based replication. Each time the connector starts up, it will automatically detect whether it is enabled and adjust its behavior accordingly.
  ====
  
  [[mysql-user]]
  [[create-a-mysql-user-for-the-connector]]
  
negative.code: |`true`
  |Boolean value that specifies whether the connector should publish changes in the database schema to a Kafka topic with the same name as the database server ID. Each schema change will be recorded using a key that contains the database name and whose value includes the DDL statement(s). This is independent of how the connector internally records database history. The default is `true`.
  
  |`include.query`
  |`false`
  |Boolean value that specifies whether the connector should include the original SQL query that generated the change event. +
  Note: This option requires MySQL be configured with the binlog_rows_query_log_events option set to ON. Query will not be present for events generated from the snapshot process. +
  WARNING: Enabling this option may expose tables or fields explicitly blacklisted or masked by including the original SQL statement in the change event. For this reason this option is defaulted to 'false'.
  
  |`event.deserialization{zwsp}.failure.handling.mode` +
  0.6.2 and later
  |`fail`
  