anchor.diff:  ---------------------------
   
   == Supported Debezium Connectors
  -- https://debezium.io/documentation/reference/0.9/connectors/mysql.html[MySql].
  +- https://debezium.io/documentation/reference/0.9/connectors/mysql.html[MySQL].
   
   *Note:* Other Debezium connectors are _not_ supported at the moment.
   
  
positive.code: | DebeziumConstants.HEADER_BEFORE           | "CamelDebeziumBefore"                          | Map/Struct  | If presents, contains the state of the row before the event occurred.
  |===
  
  == Samples
  
  === Consuming events
  
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 enables Change Data Capture from various databases using Debezium without the need for 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,
  