anchor.diff:  // spring-boot-auto-configure options: END
   
   For more information about configuration:
  -https://debezium.io/docs/embedded/#engine-properties[https://debezium.io/docs/embedded/#engine-properties]
  -https://debezium.io/docs/connectors/mysql/#connector-properties[https://debezium.io/docs/connectors/mysql/#connector-properties]
  +https://debezium.io/documentation/reference/0.9/operations/embedded.html#engine-properties[https://debezium.io/documentation/reference/0.9/operations/embedded.html#engine-properties]
  +https://debezium.io/documentation/reference/0.9/connectors/mysql.html#connector-properties[https://debezium.io/documentation/reference/0.9/connectors/mysql.html#connector-properties]
   
   == Message headers
   
  
positive.code: ---------------------------
  
  == Supported Debezium Connectors
  - https://debezium.io/docs/connectors/mysql/[MySql].
  
  
  == Options
  
negative.code: 
  *Available as of Camel version 3.0*
  
  The Debezium component is wrapper around https://debezium.io/[Debezium] using https://debezium.io/documentation/reference/0.9/operations/embedded.html[Debezium Embedded], which enabled Change Data Capture from various databases without the need of Kafka or Kafka Connect.
  
  *Note on handling failures:* Per https://debezium.io/documentation/reference/0.9/operations/embedded.html#_handling_failures[Debezium Embedded Engine] documentation, the engines is actively recording source offsets and periodically flushes these offsets to a persistent storage, so when the application is restarted or crashed, the engine will resume from the last recorded offset.
  Thus, at normal operation, your downstream routes will receive each event exactly once, however in case of an application crash (not having a graceful shutdown), the application will resume from the last recorded offset,
  which may result in receiving duplicate events immediately after the restart. Therefore, your downstream routes should be tolerant enough of such case and deduplicate events if needed.
  
  