anchor.diff:  :source-highlighter: highlight.js
   :context: debezium
   
  -[id="debezium-connector-for-mysql"]
  -= {prodname} connector for MySQL
  +toc::[]
  +
  +endif::community[]
   
   MySQL has a binary log (binlog) that records all operations in the order in which they are committed to the database. This includes changes to table schemas as well as changes to the data in tables. MySQL uses the binlog for replication and recovery.
   
  
positive.code: [[how-the-mysql-connector-works]]
  == How the connector works
  
  To optimally configure and run a {prodname} MySQL connector, it is helpful to understand how the connector tracks the structure of tables, exposes schema changes, performs snapshots, and determines Kafka topic names. An overview of the MySQL topologies that the connector supports is useful for planning your application. 
  
  ifdef::product[]
  Details are in the following topics:
  
  * xref:how-debezium-mysql-connectors-handle-database-schema-changes[]
  * xref:how-debezium-mysql-connectors-expose-database-schema-changes[]
  * xref:how-debezium-mysql-connectors-perform-database-snapshots[]
  * xref:default-names-of-kafka-topics-that-receive-debezium-mysql-change-event-records[]
  * xref:mysql-topologies-supported-by-debezium-connectors[]
  
  endif::product[]
  
  // Type: concept
  // ModuleID: how-debezium-mysql-connectors-handle-database-schema-changes
  
negative.code: // Category: debezium-using
  // Type: assembly
  [id="debezium-connector-for-mysql"]
  = {prodname} connector for MySQL
  
  ifdef::community[]
  
  :toc:
  :toc-placement: macro
  