[camel] branch master updated: Regen

[davsclaus]

This is an automated email from the ASF dual-hosted git repository.

davsclaus pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git


The following commit(s) were added to refs/heads/master by this push:
     new 9b21d36  Regen
9b21d36 is described below

commit 9b21d3643631a6bb3cba4c6e284dd2d9b58bf0e8
Author: Claus Ibsen <claus.ib...@gmail.com>
AuthorDate: Wed Oct 30 09:42:07 2019 +0100

    Regen
---
 docs/components/modules/ROOT/nav.adoc              |   2 +-
 .../modules/ROOT/pages/debezium-component.adoc     | 254 ----------------
 .../ROOT/pages/debezium-mysql-component.adoc       | 318 +++++++++++++++++++++
 .../modules/ROOT/pages/hdfs-component.adoc         |   9 +-
 docs/components/modules/ROOT/pages/index.adoc      |   2 +-
 .../ROOT/pages/sap-netweaver-component.adoc        |   2 +-
 6 files changed, 326 insertions(+), 261 deletions(-)

diff --git a/docs/components/modules/ROOT/nav.adoc 
b/docs/components/modules/ROOT/nav.adoc
index 802abe5..8649536 100644
--- a/docs/components/modules/ROOT/nav.adoc
+++ b/docs/components/modules/ROOT/nav.adoc
@@ -87,7 +87,7 @@
 * xref:dataformat-component.adoc[Data Format Component]
 * xref:dataset-component.adoc[Dataset Component]
 * xref:dataset-test-component.adoc[DataSet Test Component]
-* xref:debezium-component.adoc[Debezium Component]
+* xref:debezium-mysql-component.adoc[Debezium MySQL Connector Component]
 * xref:digitalocean-component.adoc[DigitalOcean Component]
 * xref:direct-component.adoc[Direct Component]
 * xref:direct-vm-component.adoc[Direct VM Component]
diff --git a/docs/components/modules/ROOT/pages/debezium-component.adoc 
b/docs/components/modules/ROOT/pages/debezium-component.adoc
deleted file mode 100644
index f1b98ec..0000000
--- a/docs/components/modules/ROOT/pages/debezium-component.adoc
+++ /dev/null
@@ -1,254 +0,0 @@
-[[debezium-component]]
-= Debezium Component
-:page-source: 
components/camel-debezium/camel-debezium-component/src/main/docs/debezium-component.adoc
-
-*Since Camel 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,
-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.
-
-Maven users will need to add the following dependency to their `pom.xml`
-for this component.
-
-[source,xml]
-----
-<dependency>
-    <groupId>org.apache.camel</groupId>
-    <artifactId>camel-debezium</artifactId>
-    <version>x.x.x</version>
-    <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-== URI format
-
-[source,text]
----------------------------
-debezium:connector-type[?options]
----------------------------
-
-== Supported Debezium Connectors
-- https://debezium.io/documentation/reference/0.9/connectors/mysql.html[MySQL].
-
-*Note:* Other Debezium connectors are _not_ supported at the moment.
-
-*Note:* Due to licensing issues, you will need to add the dependency for 
`mysql-conenctor-java` if you are using MySQL connector, just add the following 
to your POM file:
-[source,xml]
-----
-<dependency>
-    <groupId>mysql</groupId>
-    <artifactId>mysql-connector-java</artifactId>
-    <version>8.0.15</version>
-</dependency>
-----
-
-== Options
-
-
-// component options: START
-The Debezium component supports 2 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *configuration* (consumer) | Allow pre-configured Configurations to be set, 
you will need to extend EmbeddedDebeziumConfiguration in order to create the 
configuration for the component |  | EmbeddedDebeziumConfiguration
-| *basicPropertyBinding* (advanced) | Whether the component should use basic 
property binding (Camel 2.x) or the newer property binding with additional 
capabilities | false | boolean
-|===
-// component options: END
-
-
-// endpoint options: START
-The Debezium endpoint is configured using URI syntax:
-
-----
-debezium:connectorType
-----
-
-with the following path and query parameters:
-
-=== Path Parameters (1 parameters):
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *connectorType* | *Required* The Debezium connector type that is supported 
by Camel Debezium component. |  | String
-|===
-
-
-=== Query Parameters (72 parameters):
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the 
Camel routing Error Handler, which mean any exceptions occurred while the 
consumer is trying to pickup incoming messages, or the likes, will now be 
processed as a message and handled by the routing Error Handler. By default the 
consumer will use the org.apache.camel.spi.ExceptionHandler to deal with 
exceptions, that will be logged at WARN or ERROR level and ignored. | false | 
boolean
-| *internalKeyConverter* (consumer) | The Converter class that should be used 
to serialize and deserialize key data for offsets. The default is JSON 
converter. | org.apache.kafka.connect.json.JsonConverter | String
-| *internalValueConverter* (consumer) | The Converter class that should be 
used to serialize and deserialize value data for offsets. The default is JSON 
converter. | org.apache.kafka.connect.json.JsonConverter | String
-| *name* (consumer) | *Required* Unique name for the connector. Attempting to 
register again with the same name will fail. |  | String
-| *offsetCommitPolicy* (consumer) | The name of the Java class of the commit 
policy. It defines when offsets commit has to be triggered based on the number 
of events processed and the time elapsed since the last commit. This class must 
implement the interface .OffsetCommitPolicy. The default is a periodic commit 
policy based upon time intervals. | 
io.debezium.embedded.spi.OffsetCommitPolicy.PeriodicCommitOffsetPolicy | String
-| *offsetCommitTimeoutMs* (consumer) | Maximum number of milliseconds to wait 
for records to flush and partition offset data to be committed to offset 
storage before cancelling the process and restoring the offset data to be 
committed in a future attempt. The default is 5 seconds. | 5000 | long
-| *offsetFlushIntervalMs* (consumer) | Interval at which to try committing 
offsets. The default is 1 minute. | 60000 | long
-| *offsetStorage* (consumer) | The name of the Java class that is responsible 
for persistence of connector offsets. | 
org.apache.kafka.connect.storage.FileOffsetBackingStore | String
-| *offsetStorageFileName* (consumer) | Path to file where offsets are to be 
stored. Required when offset.storage is set to the FileOffsetBackingStore |  | 
String
-| *offsetStoragePartitions* (consumer) | The number of partitions used when 
creating the offset storage topic. Required when offset.storage is set to the 
.KafkaOffsetBackingStore. |  | int
-| *offsetStorageReplication Factor* (consumer) | Replication factor used when 
creating the offset storage topic. Required when offset.storage is set to the 
KafkaOffsetBackingStore |  | int
-| *offsetStorageTopic* (consumer) | The name of the Kafka topic where offsets 
are to be stored. Required when offset.storage is set to the 
KafkaOffsetBackingStore. |  | String
-| *exceptionHandler* (consumer) | To let the consumer use a custom 
ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this 
option is not in use. By default the consumer will deal with exceptions, that 
will be logged at WARN or ERROR level and ignored. |  | ExceptionHandler
-| *exchangePattern* (consumer) | Sets the exchange pattern when the consumer 
creates an exchange. |  | ExchangePattern
-| *basicPropertyBinding* (advanced) | Whether the endpoint should use basic 
property binding (Camel 2.x) or the newer property binding with additional 
capabilities | false | boolean
-| *synchronous* (advanced) | Sets whether synchronous processing should be 
strictly used, or Camel is allowed to use asynchronous processing (if 
supported). | false | boolean
-| *bigintUnsignedHandlingMode* (mysql) | Specify how BIGINT UNSIGNED columns 
should be represented in change events, including:'precise' uses 
java.math.BigDecimal to represent values, which are encoded in the change 
events using a binary representation and Kafka Connect's 
'org.apache.kafka.connect.data.Decimal' type; 'long' (the default) represents 
values using Java's 'long', which may not offer the precision but will be far 
easier to use in consumers. | long | String
-| *binlogBufferSize* (mysql) | The size of a look-ahead buffer used by the 
binlog reader to decide whether the transaction in progress is going to be 
committed or rolled back. Use 0 to disable look-ahead buffering. Defaults to 0 
(i.e. buffering is disabled). | 0 | int
-| *columnBlacklist* (mysql) | Description is not available here, please check 
Debezium website for corresponding key 'column.blacklist' description. |  | 
String
-| *connectKeepAlive* (mysql) | Whether a separate thread should be used to 
ensure the connection is kept alive. | true | boolean
-| *connectKeepAliveIntervalMs* (mysql) | Interval in milliseconds to wait for 
connection checking if keep alive thread is used. | 60000 | long
-| *connectTimeoutMs* (mysql) | Maximum time in milliseconds to wait after 
trying to connect to the database before timing out. | 30000 | int
-| *databaseBlacklist* (mysql) | Description is not available here, please 
check Debezium website for corresponding key 'database.blacklist' description. 
|  | String
-| *databaseHistory* (mysql) | The name of the DatabaseHistory class that 
should be used to store and recover database schema changes. The configuration 
properties for the history are prefixed with the 'database.history.' string. | 
io.debezium.relational.history.FileDatabaseHistory | String
-| *databaseHistoryFileFilename* (mysql) | The path to the file that will be 
used to record the database history |  | String
-| *databaseHistoryKafka BootstrapServers* (mysql) | A list of host/port pairs 
that the connector will use for establishing the initial connection to the 
Kafka cluster for retrieving database schema history previously stored by the 
connector. This should point to the same Kafka cluster used by the Kafka 
Connect process. |  | String
-| *databaseHistoryKafka RecoveryAttempts* (mysql) | The number of attempts in 
a row that no data are returned from Kafka before recover completes. The 
maximum amount of time to wait after receiving no data is (recovery.attempts) x 
(recovery.poll.interval.ms). | 100 | int
-| *databaseHistoryKafka RecoveryPollIntervalMs* (mysql) | The number of 
milliseconds to wait while polling for persisted data during recovery. | 100 | 
int
-| *databaseHistoryKafkaTopic* (mysql) | The name of the topic for the database 
schema history |  | String
-| *databaseHistorySkip UnparseableDdl* (mysql) | Controls the action Debezium 
will take when it meets a DDL statement in binlog, that it cannot parse.By 
default the connector will stop operating but by changing the setting it can 
ignore the statements which it cannot parse. If skipping is enabled then 
Debezium can miss metadata changes. | false | boolean
-| *databaseHistoryStoreOnly MonitoredTablesDdl* (mysql) | Controls what DDL 
will Debezium store in database history.By default (false) Debezium will store 
all incoming DDL statements. If set to truethen only DDL that manipulates a 
monitored table will be stored. | false | boolean
-| *databaseHostname* (mysql) | Resolvable hostname or IP address of the MySQL 
database server. |  | String
-| *databaseInitialStatements* (mysql) | A semicolon separated list of SQL 
statements to be executed when a JDBC connection (not binlog reading 
connection) to the database is established. Note that the connector may 
establish JDBC connections at its own discretion, so this should typically be 
used for configuration of session parameters only,but not for executing DML 
statements. Use doubled semicolon (';;') to use a semicolon as a character and 
not as a delimiter. |  | String
-| *databaseJdbcDriver* (mysql) | JDBC Driver class name used to connect to the 
MySQL database server. | class com.mysql.cj.jdbc.Driver | String
-| *databasePassword* (mysql) | *Required* Password of the MySQL database user 
to be used when connecting to the database. |  | String
-| *databasePort* (mysql) | Port of the MySQL database server. | 3306 | int
-| *databaseServerId* (mysql) | A numeric ID of this database client, which 
must be unique across all currently-running database processes in the cluster. 
This connector joins the MySQL database cluster as another server (with this 
unique ID) so it can read the binlog. By default, a random number is generated 
between 5400 and 6400. |  | long
-| *databaseServerIdOffset* (mysql) | Only relevant if parallel snapshotting is 
configured. During parallel snapshotting, multiple (4) connections open to the 
database client, and they each need their own unique connection ID. This offset 
is used to generate those IDs from the base configured cluster ID. | 10000 | 
long
-| *databaseServerName* (mysql) | *Required* Unique name that identifies the 
database server and all recorded offsets, and that is used as a prefix for all 
schemas and topics. Each distinct installation should have a separate namespace 
and be monitored by at most one Debezium connector. |  | String
-| *databaseSslKeystore* (mysql) | Location of the Java keystore file 
containing an application process's own certificate and private key. |  | String
-| *databaseSslKeystorePassword* (mysql) | Password to access the private key 
from the keystore file specified by 'ssl.keystore' configuration property or 
the 'javax.net.ssl.keyStore' system or JVM property. This password is used to 
unlock the keystore file (store password), and to decrypt the private key 
stored in the keystore (key password). |  | String
-| *databaseSslMode* (mysql) | Whether to use an encrypted connection to MySQL. 
Options include'disabled' (the default) to use an unencrypted connection; 
'preferred' to establish a secure (encrypted) connection if the server supports 
secure connections, but fall back to an unencrypted connection otherwise; 
'required' to use a secure (encrypted) connection, and fail if one cannot be 
established; 'verify_ca' like 'required' but additionally verify the server TLS 
certificate against the conf [...]
-| *databaseSslTruststore* (mysql) | Location of the Java truststore file 
containing the collection of CA certificates trusted by this application 
process (trust store). |  | String
-| *databaseSslTruststore Password* (mysql) | Password to unlock the keystore 
file (store password) specified by 'ssl.trustore' configuration property or the 
'javax.net.ssl.trustStore' system or JVM property. |  | String
-| *databaseUser* (mysql) | Name of the MySQL database user to be used when 
connecting to the database. |  | String
-| *databaseWhitelist* (mysql) | The databases for which changes are to be 
captured |  | String
-| *ddlParserMode* (mysql) | MySQL DDL statements can be parsed in different 
ways:'legacy' parsing is creating a TokenStream and comparing token by token 
with an expected values.The decisions are made by matched token values.'antlr' 
(the default) uses generated parser from MySQL grammar using ANTLR v4 tool 
which use ALL() algorithm for parsing.This parser creates a parsing tree for 
DDL statement, then walks trough it and apply changes by node types in parsed 
tree. | antlr | String
-| *decimalHandlingMode* (mysql) | Specify how DECIMAL and NUMERIC columns 
should be represented in change events, including:'precise' (the default) uses 
java.math.BigDecimal to represent values, which are encoded in the change 
events using a binary representation and Kafka Connect's 
'org.apache.kafka.connect.data.Decimal' type; 'string' uses string to represent 
values; 'double' represents values using Java's 'double', which may not offer 
the precision but will be far easier to use in con [...]
-| *enableTimeAdjuster* (mysql) | MySQL allows user to insert year value as 
either 2-digit or 4-digit. In case of two digit the value is automatically 
mapped into 1970 - 2069.false - delegates the implicit conversion to the 
databasetrue - (the default) Debezium makes the conversion | true | boolean
-| *eventDeserializationFailure HandlingMode* (mysql) | Specify how failures 
during deserialization of binlog events (i.e. when encountering a corrupted 
event) should be handled, including:'fail' (the default) an exception 
indicating the problematic event and its binlog position is raised, causing the 
connector to be stopped; 'warn' the problematic event and its binlog position 
will be logged and the event will be skipped;'ignore' the problematic event 
will be skipped. | fail | String
-| *gtidNewChannelPosition* (mysql) | If set to 'latest', when connector sees 
new GTID, it will start consuming gtid channel from the server latest executed 
gtid position. If 'earliest' connector starts reading channel from first 
available (not purged) gtid position on the server. | latest | String
-| *gtidSourceExcludes* (mysql) | The source UUIDs used to exclude GTID ranges 
when determine the starting position in the MySQL server's binlog. |  | String
-| *gtidSourceFilterDmlEvents* (mysql) | If set to true, we will only produce 
DML events into Kafka for transactions that were written on mysql servers with 
UUIDs matching the filters defined by the gtid.source.includes or 
gtid.source.excludes configuration options, if they are specified. | true | 
boolean
-| *gtidSourceIncludes* (mysql) | The source UUIDs used to include GTID ranges 
when determine the starting position in the MySQL server's binlog. |  | String
-| *heartbeatIntervalMs* (mysql) | Length of an interval in milli-seconds in in 
which the connector periodically sends heartbeat messages to a heartbeat topic. 
Use 0 to disable heartbeat messages. Disabled by default. | 0 | int
-| *heartbeatTopicsPrefix* (mysql) | The prefix that is used to name heartbeat 
topics.Defaults to __debezium-heartbeat. | __debezium-heartbeat | String
-| *includeQuery* (mysql) | 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 snapshot. 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 the 
default value is 'false'. | false | [...]
-| *includeSchemaChanges* (mysql) | 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).The 
default is 'true'. This is independent of how the connector internally records 
database history. | true | boolean
-| *inconsistentSchemaHandling Mode* (mysql) | Specify how binlog events that 
belong to a table missing from internal schema representation (i.e. internal 
representation is not consistent with database) should be handled, 
including:'fail' (the default) an exception indicating the problematic event 
and its binlog position is raised, causing the connector to be stopped; 'warn' 
the problematic event and its binlog position will be logged and the event will 
be skipped;'ignore' the problematic [...]
-| *maxBatchSize* (mysql) | Maximum size of each batch of source records. 
Defaults to 2048. | 2048 | int
-| *maxQueueSize* (mysql) | Maximum size of the queue for change events read 
from the database log but not yet recorded or forwarded. Defaults to 8192, and 
should always be larger than the maximum batch size. | 8192 | int
-| *pollIntervalMs* (mysql) | Frequency in milliseconds to wait for new change 
events to appear after receiving no events. Defaults to 500ms. | 500 | long
-| *snapshotDelayMs* (mysql) | The number of milliseconds to delay before a 
snapshot will begin. | 0 | long
-| *snapshotFetchSize* (mysql) | The maximum number of records that should be 
loaded into memory while performing a snapshot |  | int
-| *snapshotLockingMode* (mysql) | Controls how long the connector holds onto 
the global read lock while it is performing a snapshot. The default is 
'minimal', which means the connector holds the global read lock (and thus 
prevents any updates) for just the initial portion of the snapshot while the 
database schemas and other metadata are being read. The remaining work in a 
snapshot involves selecting all rows from each table, and this can be done 
using the snapshot process' REPEATABLE REA [...]
-| *snapshotMode* (mysql) | The criteria for running a snapshot upon startup of 
the connector. Options include: 'when_needed' to specify that the connector run 
a snapshot upon startup whenever it deems it necessary; 'initial' (the default) 
to specify the connector can run a snapshot only when no offsets are available 
for the logical server name; 'initial_only' same as 'initial' except the 
connector should stop after completing the snapshot and before it would 
normally read the binlog; and [...]
-| *snapshotNewTables* (mysql) | BETA FEATURE: On connector restart, the 
connector will check if there have been any new tables added to the 
configuration, and snapshot them. There is presently only two options:'off': 
Default behavior. Do not snapshot new tables.'parallel': The snapshot of the 
new tables will occur in parallel to the continued binlog reading of the old 
tables. When the snapshot completes, an independent binlog reader will begin 
reading the events for the new tables until  [...]
-| *tableBlacklist* (mysql) | Description is not available here, please check 
Debezium website for corresponding key 'table.blacklist' description. |  | 
String
-| *tableIgnoreBuiltin* (mysql) | Flag specifying whether built-in tables 
should be ignored. | true | boolean
-| *tableWhitelist* (mysql) | The tables for which changes are to be captured | 
 | String
-| *timePrecisionMode* (mysql) | Time, date, and timestamps can be represented 
with different kinds of precisions, including:'adaptive_time_microseconds' (the 
default) like 'adaptive' mode, but TIME fields always use microseconds 
precision;'adaptive' (deprecated) bases the precision of time, date, and 
timestamp values on the database column's precision; 'connect' always 
represents time, date, and timestamp values using Kafka Connect's built-in 
representations for Time, Date, and Timestamp [...]
-| *tombstonesOnDelete* (mysql) | Whether delete operations should be 
represented by a delete event and a subsquenttombstone event (true) or only by 
a delete event (false). Emitting the tombstone event (the default behavior) 
allows Kafka to completely delete all events pertaining to the given key once 
the source record got deleted. | false | boolean
-|===
-// endpoint options: END
-// spring-boot-auto-configure options: START
-== Spring Boot Auto-Configuration
-
-When using Spring Boot make sure to use the following Maven dependency to have 
support for auto configuration:
-
-[source,xml]
-----
-<dependency>
-  <groupId>org.apache.camel</groupId>
-  <artifactId>camel-debezium-starter</artifactId>
-  <version>x.x.x</version>
-  <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 3 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.debezium.basic-property-binding* | Whether the component 
should use basic property binding (Camel 2.x) or the newer property binding 
with additional capabilities | false | Boolean
-| *camel.component.debezium.configuration* | Allow pre-configured 
Configurations to be set, you will need to extend EmbeddedDebeziumConfiguration 
in order to create the configuration for the component. The option is a 
org.apache.camel.component.debezium.configuration.EmbeddedDebeziumConfiguration 
type. |  | String
-| *camel.component.debezium.enabled* | Whether to enable auto configuration of 
the debezium component. This is enabled by default. |  | Boolean
-|===
-// spring-boot-auto-configure options: END
-
-For more information about configuration:
-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
-
-=== Consumer headers
-
-The following headers are available when consuming change events from Debezium.
-[width="100%",cols="2m,2m,1m,5",options="header"]
-|===
-| Header constant                           | Header value                     
              | Type        | Description
-| DebeziumConstants.HEADER_IDENTIFIER       | "CamelDebeziumIdentifier"        
              | String      | The identifier of the connector, normally is this 
format "{server-name}.{database-name}.{table-name}".
-| DebeziumConstants.HEADER_KEY              | "CamelDebeziumKey"               
              | Struct      | The key of the event, normally is the table 
Primary Key.
-| DebeziumConstants.HEADER_SOURCE_METADATA  | "CamelDebeziumSourceMetadata"    
              | Map         | The metadata about the source event, for example 
`table` name, database `name`, log position, etc, please refer to the Debezium 
documentation for more info.
-| DebeziumConstants.HEADER_OPERATION        | "CamelDebeziumOperation"         
              | String      | If presents, the type of event operation. Values 
for the connector are `c` for create (or insert), `u` for update, `d` for 
delete or `r` in case of a snapshot event.
-| DebeziumConstants.HEADER_TIMESTAMP        | "CamelDebeziumTimestamp"         
              | Long        | If presents, the time (using the system clock in 
the JVM) at which the connector processed the event.
-| DebeziumConstants.HEADER_BEFORE           | "CamelDebeziumBefore"            
              | Struct     | If presents, contains the state of the row before 
the event occurred.
-|===
-
-== Message body
-The message body if is not `null` (in case of tombstones), it contains the 
state of the row after the event occurred as `Struct` format or `Map` format if 
you use the included Type Converter from `Struct` to `Map` (please look below 
for more explanation).
-
-== Samples
-
-=== Consuming events
-
-Here is a very simple route that you can use in order to listen to Debezium 
events from MySQL connector.
-[source,java]
-----
-from("debezium:mysql?name=dbz-test-1&offsetStorageFileName=/usr/offset-file-1.dat&databaseHostName=localhost&databaseUser=debezium&databasePassword=dbz&databaseServerName=my-app-connector&databaseHistoryFileName=/usr/history-file-1.dat")
-    .log("Event received from Debezium : ${body}")
-    .log("    with this identifier ${headers.CamelDebeziumIdentifier}")
-    .log("    with these source metadata 
${headers.CamelDebeziumSourceMetadata}")
-    .log("    the event occured upon this operation 
'${headers.CamelDebeziumSourceOperation}'")
-    .log("    on this database '${headers.CamelDebeziumSourceMetadata[db]}' 
and this table '${headers.CamelDebeziumSourceMetadata[table]}'")
-    .log("    with the key ${headers.CamelDebeziumKey}")
-    .log("    the previous value is ${headers.CamelDebeziumBefore}")
-----
-
-By default, the component will emit the events in the body and 
`CamelDebeziumBefore` header as 
https://kafka.apache.org/22/javadoc/org/apache/kafka/connect/data/Struct.html[`Struct`]
 data type, the reasoning behind this, is to perceive the schema information in 
case is needed.
-However, the component as well contains a 
xref:manual::type-converter.adoc[Type Converter] that converts
-from default output type of 
https://kafka.apache.org/22/javadoc/org/apache/kafka/connect/data/Struct.html[`Struct`]
 to `Map` in order to leverage Camel's rich xref:manual::data-format.adoc[Data 
Format] types which many of them work out of box with `Map` data type.
-To use it, you can either add `Map.class` type when you access the message 
e.g: `exchange.getIn().getBody(Map.class)`, or you can convert the body always 
to `Map` from the route builder by adding `.convertBodyTo(Map.class)` to your 
Camel Route DSL after `from` statement.
-
-We mentioned above about the schema, which can be used in case you need to 
perform advance data transformation and the schema is needed for that. If you 
choose not to convert your body to `Map`,
-you can obtain the schema information as 
https://kafka.apache.org/22/javadoc/org/apache/kafka/connect/data/Schema.html[`Schema`]
 type from `Struct` like this:
-[source,java]
-----
-from("debezium:[connectorType]?[options]])
-    .process(exchange -> {
-        final Struct bodyValue = exchange.getIn().getBody(Struct.class);
-        final Schema schemaValue = bodyValue.schema();
-
-        log.info("Body value is :" + bodyValue);
-        log.info("With Schema : " + schemaValue);
-        log.info("And fields of :" + schemaValue.fields());
-        log.info("Field name has `" + schemaValue.field("name").schema() + "` 
type");
-    });
-----
-
-*Important Note:* This component is a thin wrapper around Debezium Engine as 
mentioned, therefore before using this component in production, you need to 
understand how Debezium works and how configurations can reflect the expected 
behavior, especially in regards to 
https://debezium.io/documentation/reference/0.9/operations/embedded.html#_handling_failures[handling
 failures].
diff --git a/docs/components/modules/ROOT/pages/debezium-mysql-component.adoc 
b/docs/components/modules/ROOT/pages/debezium-mysql-component.adoc
new file mode 100644
index 0000000..55f31b8
--- /dev/null
+++ b/docs/components/modules/ROOT/pages/debezium-mysql-component.adoc
@@ -0,0 +1,318 @@
+[[debezium-mysql-component]]
+= Debezium MySQL Connector Component
+:page-source: 
components/camel-debezium-mysql/src/main/docs/debezium-mysql-component.adoc
+= Debezium MySQL Component
+*Since Camel 3.0*
+
+
+*Since Camel 3.0*
+
+The Debezium MySQL 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 MySQL database 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,
+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.
+
+Maven users will need to add the following dependency to their `pom.xml`
+for this component.
+
+[source,xml]
+----
+<dependency>
+    <groupId>org.apache.camel</groupId>
+    <artifactId>camel-debezium-mysql</artifactId>
+    <version>x.x.x</version>
+    <!-- use the same version as your Camel core version -->
+</dependency>
+----
+
+== URI format
+
+[source,text]
+---------------------------
+debezium-mysql:name[?options]
+---------------------------
+
+*Note:* Due to licensing issues, you will need to add the dependency for 
`mysql-conenctor-java` if you are using MySQL connector, just add the following 
to your POM file:
+[source,xml]
+----
+<dependency>
+    <groupId>mysql</groupId>
+    <artifactId>mysql-connector-java</artifactId>
+    <version>8.0.15</version>
+</dependency>
+----
+
+== Options
+
+
+// component options: START
+The Debezium MySQL Connector component supports 2 options, which are listed 
below.
+
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Type
+| *configuration* (consumer) | Allow pre-configured Configurations to be set. 
|  | MySqlConnectorEmbeddedDebeziumConfiguration
+| *basicPropertyBinding* (advanced) | Whether the component should use basic 
property binding (Camel 2.x) or the newer property binding with additional 
capabilities | false | boolean
+|===
+// component options: END
+
+
+// endpoint options: START
+The Debezium MySQL Connector endpoint is configured using URI syntax:
+
+----
+debezium-mysql:name
+----
+
+with the following path and query parameters:
+
+=== Path Parameters (1 parameters):
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Type
+| *name* | *Required* Unique name for the connector. Attempting to register 
again with the same name will fail. |  | String
+|===
+
+
+=== Query Parameters (71 parameters):
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Type
+| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the 
Camel routing Error Handler, which mean any exceptions occurred while the 
consumer is trying to pickup incoming messages, or the likes, will now be 
processed as a message and handled by the routing Error Handler. By default the 
consumer will use the org.apache.camel.spi.ExceptionHandler to deal with 
exceptions, that will be logged at WARN or ERROR level and ignored. | false | 
boolean
+| *internalKeyConverter* (consumer) | The Converter class that should be used 
to serialize and deserialize key data for offsets. The default is JSON 
converter. | org.apache.kafka.connect.json.JsonConverter | String
+| *internalValueConverter* (consumer) | The Converter class that should be 
used to serialize and deserialize value data for offsets. The default is JSON 
converter. | org.apache.kafka.connect.json.JsonConverter | String
+| *offsetCommitPolicy* (consumer) | The name of the Java class of the commit 
policy. It defines when offsets commit has to be triggered based on the number 
of events processed and the time elapsed since the last commit. This class must 
implement the interface .OffsetCommitPolicy. The default is a periodic commit 
policy based upon time intervals. | 
io.debezium.embedded.spi.OffsetCommitPolicy.PeriodicCommitOffsetPolicy | String
+| *offsetCommitTimeoutMs* (consumer) | Maximum number of milliseconds to wait 
for records to flush and partition offset data to be committed to offset 
storage before cancelling the process and restoring the offset data to be 
committed in a future attempt. The default is 5 seconds. | 5000 | long
+| *offsetFlushIntervalMs* (consumer) | Interval at which to try committing 
offsets. The default is 1 minute. | 60000 | long
+| *offsetStorage* (consumer) | The name of the Java class that is responsible 
for persistence of connector offsets. | 
org.apache.kafka.connect.storage.FileOffsetBackingStore | String
+| *offsetStorageFileName* (consumer) | Path to file where offsets are to be 
stored. Required when offset.storage is set to the FileOffsetBackingStore |  | 
String
+| *offsetStoragePartitions* (consumer) | The number of partitions used when 
creating the offset storage topic. Required when offset.storage is set to the 
.KafkaOffsetBackingStore. |  | int
+| *offsetStorageReplication Factor* (consumer) | Replication factor used when 
creating the offset storage topic. Required when offset.storage is set to the 
KafkaOffsetBackingStore |  | int
+| *offsetStorageTopic* (consumer) | The name of the Kafka topic where offsets 
are to be stored. Required when offset.storage is set to the 
KafkaOffsetBackingStore. |  | String
+| *exceptionHandler* (consumer) | To let the consumer use a custom 
ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this 
option is not in use. By default the consumer will deal with exceptions, that 
will be logged at WARN or ERROR level and ignored. |  | ExceptionHandler
+| *exchangePattern* (consumer) | Sets the exchange pattern when the consumer 
creates an exchange. |  | ExchangePattern
+| *basicPropertyBinding* (advanced) | Whether the endpoint should use basic 
property binding (Camel 2.x) or the newer property binding with additional 
capabilities | false | boolean
+| *synchronous* (advanced) | Sets whether synchronous processing should be 
strictly used, or Camel is allowed to use asynchronous processing (if 
supported). | false | boolean
+| *bigintUnsignedHandlingMode* (mysql) | Specify how BIGINT UNSIGNED columns 
should be represented in change events, including:'precise' uses 
java.math.BigDecimal to represent values, which are encoded in the change 
events using a binary representation and Kafka Connect's 
'org.apache.kafka.connect.data.Decimal' type; 'long' (the default) represents 
values using Java's 'long', which may not offer the precision but will be far 
easier to use in consumers. | long | String
+| *binlogBufferSize* (mysql) | The size of a look-ahead buffer used by the 
binlog reader to decide whether the transaction in progress is going to be 
committed or rolled back. Use 0 to disable look-ahead buffering. Defaults to 0 
(i.e. buffering is disabled). | 0 | int
+| *columnBlacklist* (mysql) | Description is not available here, please check 
Debezium website for corresponding key 'column.blacklist' description. |  | 
String
+| *connectKeepAlive* (mysql) | Whether a separate thread should be used to 
ensure the connection is kept alive. | true | boolean
+| *connectKeepAliveIntervalMs* (mysql) | Interval in milliseconds to wait for 
connection checking if keep alive thread is used. | 60000 | long
+| *connectTimeoutMs* (mysql) | Maximum time in milliseconds to wait after 
trying to connect to the database before timing out. | 30000 | int
+| *databaseBlacklist* (mysql) | Description is not available here, please 
check Debezium website for corresponding key 'database.blacklist' description. 
|  | String
+| *databaseHistory* (mysql) | The name of the DatabaseHistory class that 
should be used to store and recover database schema changes. The configuration 
properties for the history are prefixed with the 'database.history.' string. | 
io.debezium.relational.history.FileDatabaseHistory | String
+| *databaseHistoryFileFilename* (mysql) | The path to the file that will be 
used to record the database history |  | String
+| *databaseHistoryKafka BootstrapServers* (mysql) | A list of host/port pairs 
that the connector will use for establishing the initial connection to the 
Kafka cluster for retrieving database schema history previously stored by the 
connector. This should point to the same Kafka cluster used by the Kafka 
Connect process. |  | String
+| *databaseHistoryKafka RecoveryAttempts* (mysql) | The number of attempts in 
a row that no data are returned from Kafka before recover completes. The 
maximum amount of time to wait after receiving no data is (recovery.attempts) x 
(recovery.poll.interval.ms). | 100 | int
+| *databaseHistoryKafka RecoveryPollIntervalMs* (mysql) | The number of 
milliseconds to wait while polling for persisted data during recovery. | 100 | 
int
+| *databaseHistoryKafkaTopic* (mysql) | The name of the topic for the database 
schema history |  | String
+| *databaseHistorySkip UnparseableDdl* (mysql) | Controls the action Debezium 
will take when it meets a DDL statement in binlog, that it cannot parse.By 
default the connector will stop operating but by changing the setting it can 
ignore the statements which it cannot parse. If skipping is enabled then 
Debezium can miss metadata changes. | false | boolean
+| *databaseHistoryStoreOnly MonitoredTablesDdl* (mysql) | Controls what DDL 
will Debezium store in database history.By default (false) Debezium will store 
all incoming DDL statements. If set to truethen only DDL that manipulates a 
monitored table will be stored. | false | boolean
+| *databaseHostname* (mysql) | Resolvable hostname or IP address of the MySQL 
database server. |  | String
+| *databaseInitialStatements* (mysql) | A semicolon separated list of SQL 
statements to be executed when a JDBC connection (not binlog reading 
connection) to the database is established. Note that the connector may 
establish JDBC connections at its own discretion, so this should typically be 
used for configuration of session parameters only,but not for executing DML 
statements. Use doubled semicolon (';;') to use a semicolon as a character and 
not as a delimiter. |  | String
+| *databaseJdbcDriver* (mysql) | JDBC Driver class name used to connect to the 
MySQL database server. | class com.mysql.cj.jdbc.Driver | String
+| *databasePassword* (mysql) | *Required* Password of the MySQL database user 
to be used when connecting to the database. |  | String
+| *databasePort* (mysql) | Port of the MySQL database server. | 3306 | int
+| *databaseServerId* (mysql) | A numeric ID of this database client, which 
must be unique across all currently-running database processes in the cluster. 
This connector joins the MySQL database cluster as another server (with this 
unique ID) so it can read the binlog. By default, a random number is generated 
between 5400 and 6400. |  | long
+| *databaseServerIdOffset* (mysql) | Only relevant if parallel snapshotting is 
configured. During parallel snapshotting, multiple (4) connections open to the 
database client, and they each need their own unique connection ID. This offset 
is used to generate those IDs from the base configured cluster ID. | 10000 | 
long
+| *databaseServerName* (mysql) | *Required* Unique name that identifies the 
database server and all recorded offsets, and that is used as a prefix for all 
schemas and topics. Each distinct installation should have a separate namespace 
and be monitored by at most one Debezium connector. |  | String
+| *databaseSslKeystore* (mysql) | Location of the Java keystore file 
containing an application process's own certificate and private key. |  | String
+| *databaseSslKeystorePassword* (mysql) | Password to access the private key 
from the keystore file specified by 'ssl.keystore' configuration property or 
the 'javax.net.ssl.keyStore' system or JVM property. This password is used to 
unlock the keystore file (store password), and to decrypt the private key 
stored in the keystore (key password). |  | String
+| *databaseSslMode* (mysql) | Whether to use an encrypted connection to MySQL. 
Options include'disabled' (the default) to use an unencrypted connection; 
'preferred' to establish a secure (encrypted) connection if the server supports 
secure connections, but fall back to an unencrypted connection otherwise; 
'required' to use a secure (encrypted) connection, and fail if one cannot be 
established; 'verify_ca' like 'required' but additionally verify the server TLS 
certificate against the conf [...]
+| *databaseSslTruststore* (mysql) | Location of the Java truststore file 
containing the collection of CA certificates trusted by this application 
process (trust store). |  | String
+| *databaseSslTruststore Password* (mysql) | Password to unlock the keystore 
file (store password) specified by 'ssl.trustore' configuration property or the 
'javax.net.ssl.trustStore' system or JVM property. |  | String
+| *databaseUser* (mysql) | Name of the MySQL database user to be used when 
connecting to the database. |  | String
+| *databaseWhitelist* (mysql) | The databases for which changes are to be 
captured |  | String
+| *ddlParserMode* (mysql) | MySQL DDL statements can be parsed in different 
ways:'legacy' parsing is creating a TokenStream and comparing token by token 
with an expected values.The decisions are made by matched token values.'antlr' 
(the default) uses generated parser from MySQL grammar using ANTLR v4 tool 
which use ALL() algorithm for parsing.This parser creates a parsing tree for 
DDL statement, then walks trough it and apply changes by node types in parsed 
tree. | antlr | String
+| *decimalHandlingMode* (mysql) | Specify how DECIMAL and NUMERIC columns 
should be represented in change events, including:'precise' (the default) uses 
java.math.BigDecimal to represent values, which are encoded in the change 
events using a binary representation and Kafka Connect's 
'org.apache.kafka.connect.data.Decimal' type; 'string' uses string to represent 
values; 'double' represents values using Java's 'double', which may not offer 
the precision but will be far easier to use in con [...]
+| *enableTimeAdjuster* (mysql) | MySQL allows user to insert year value as 
either 2-digit or 4-digit. In case of two digit the value is automatically 
mapped into 1970 - 2069.false - delegates the implicit conversion to the 
databasetrue - (the default) Debezium makes the conversion | true | boolean
+| *eventDeserializationFailure HandlingMode* (mysql) | Specify how failures 
during deserialization of binlog events (i.e. when encountering a corrupted 
event) should be handled, including:'fail' (the default) an exception 
indicating the problematic event and its binlog position is raised, causing the 
connector to be stopped; 'warn' the problematic event and its binlog position 
will be logged and the event will be skipped;'ignore' the problematic event 
will be skipped. | fail | String
+| *gtidNewChannelPosition* (mysql) | If set to 'latest', when connector sees 
new GTID, it will start consuming gtid channel from the server latest executed 
gtid position. If 'earliest' connector starts reading channel from first 
available (not purged) gtid position on the server. | latest | String
+| *gtidSourceExcludes* (mysql) | The source UUIDs used to exclude GTID ranges 
when determine the starting position in the MySQL server's binlog. |  | String
+| *gtidSourceFilterDmlEvents* (mysql) | If set to true, we will only produce 
DML events into Kafka for transactions that were written on mysql servers with 
UUIDs matching the filters defined by the gtid.source.includes or 
gtid.source.excludes configuration options, if they are specified. | true | 
boolean
+| *gtidSourceIncludes* (mysql) | The source UUIDs used to include GTID ranges 
when determine the starting position in the MySQL server's binlog. |  | String
+| *heartbeatIntervalMs* (mysql) | Length of an interval in milli-seconds in in 
which the connector periodically sends heartbeat messages to a heartbeat topic. 
Use 0 to disable heartbeat messages. Disabled by default. | 0 | int
+| *heartbeatTopicsPrefix* (mysql) | The prefix that is used to name heartbeat 
topics.Defaults to __debezium-heartbeat. | __debezium-heartbeat | String
+| *includeQuery* (mysql) | 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 snapshot. 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 the 
default value is 'false'. | false | [...]
+| *includeSchemaChanges* (mysql) | 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).The 
default is 'true'. This is independent of how the connector internally records 
database history. | true | boolean
+| *inconsistentSchemaHandling Mode* (mysql) | Specify how binlog events that 
belong to a table missing from internal schema representation (i.e. internal 
representation is not consistent with database) should be handled, 
including:'fail' (the default) an exception indicating the problematic event 
and its binlog position is raised, causing the connector to be stopped; 'warn' 
the problematic event and its binlog position will be logged and the event will 
be skipped;'ignore' the problematic [...]
+| *maxBatchSize* (mysql) | Maximum size of each batch of source records. 
Defaults to 2048. | 2048 | int
+| *maxQueueSize* (mysql) | Maximum size of the queue for change events read 
from the database log but not yet recorded or forwarded. Defaults to 8192, and 
should always be larger than the maximum batch size. | 8192 | int
+| *pollIntervalMs* (mysql) | Frequency in milliseconds to wait for new change 
events to appear after receiving no events. Defaults to 500ms. | 500 | long
+| *snapshotDelayMs* (mysql) | The number of milliseconds to delay before a 
snapshot will begin. | 0 | long
+| *snapshotFetchSize* (mysql) | The maximum number of records that should be 
loaded into memory while performing a snapshot |  | int
+| *snapshotLockingMode* (mysql) | Controls how long the connector holds onto 
the global read lock while it is performing a snapshot. The default is 
'minimal', which means the connector holds the global read lock (and thus 
prevents any updates) for just the initial portion of the snapshot while the 
database schemas and other metadata are being read. The remaining work in a 
snapshot involves selecting all rows from each table, and this can be done 
using the snapshot process' REPEATABLE REA [...]
+| *snapshotMode* (mysql) | The criteria for running a snapshot upon startup of 
the connector. Options include: 'when_needed' to specify that the connector run 
a snapshot upon startup whenever it deems it necessary; 'initial' (the default) 
to specify the connector can run a snapshot only when no offsets are available 
for the logical server name; 'initial_only' same as 'initial' except the 
connector should stop after completing the snapshot and before it would 
normally read the binlog; and [...]
+| *snapshotNewTables* (mysql) | BETA FEATURE: On connector restart, the 
connector will check if there have been any new tables added to the 
configuration, and snapshot them. There is presently only two options:'off': 
Default behavior. Do not snapshot new tables.'parallel': The snapshot of the 
new tables will occur in parallel to the continued binlog reading of the old 
tables. When the snapshot completes, an independent binlog reader will begin 
reading the events for the new tables until  [...]
+| *tableBlacklist* (mysql) | Description is not available here, please check 
Debezium website for corresponding key 'table.blacklist' description. |  | 
String
+| *tableIgnoreBuiltin* (mysql) | Flag specifying whether built-in tables 
should be ignored. | true | boolean
+| *tableWhitelist* (mysql) | The tables for which changes are to be captured | 
 | String
+| *timePrecisionMode* (mysql) | Time, date, and timestamps can be represented 
with different kinds of precisions, including:'adaptive_time_microseconds' (the 
default) like 'adaptive' mode, but TIME fields always use microseconds 
precision;'adaptive' (deprecated) bases the precision of time, date, and 
timestamp values on the database column's precision; 'connect' always 
represents time, date, and timestamp values using Kafka Connect's built-in 
representations for Time, Date, and Timestamp [...]
+| *tombstonesOnDelete* (mysql) | Whether delete operations should be 
represented by a delete event and a subsquenttombstone event (true) or only by 
a delete event (false). Emitting the tombstone event (the default behavior) 
allows Kafka to completely delete all events pertaining to the given key once 
the source record got deleted. | false | boolean
+|===
+// endpoint options: END
+// spring-boot-auto-configure options: START
+== Spring Boot Auto-Configuration
+
+When using Spring Boot make sure to use the following Maven dependency to have 
support for auto configuration:
+
+[source,xml]
+----
+<dependency>
+  <groupId>org.apache.camel</groupId>
+  <artifactId>camel-debezium-mysql-starter</artifactId>
+  <version>x.x.x</version>
+  <!-- use the same version as your Camel core version -->
+</dependency>
+----
+
+
+The component supports 70 options, which are listed below.
+
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Type
+| *camel.component.debezium-mysql.basic-property-binding* | Whether the 
component should use basic property binding (Camel 2.x) or the newer property 
binding with additional capabilities | false | Boolean
+| *camel.component.debezium-mysql.configuration.bigint-unsigned-handling-mode* 
| 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 snapshot. WARNING: Enabling this option may expose tables 
or fields explicitly blacklisted or masked by including the original SQL 
statement in the change event. F [...]
+| *camel.component.debezium-mysql.configuration.binlog-buffer-size* | 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 snapshot. 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 rea [...]
+| *camel.component.debezium-mysql.configuration.column-blacklist* | 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 snapshot. 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 reaso [...]
+| *camel.component.debezium-mysql.configuration.connect-keep-alive* | 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 snapshot. 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 rea [...]
+| 
*camel.component.debezium-mysql.configuration.connect-keep-alive-interval-ms* | 
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 snapshot. WARNING: Enabling this option may expose tables 
or fields explicitly blacklisted or masked by including the original SQL 
statement in the change event.  [...]
+| *camel.component.debezium-mysql.configuration.connect-timeout-ms* | 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 snapshot. 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 rea [...]
+| *camel.component.debezium-mysql.configuration.connector-class* | The name of 
the Java class for the connector |  | Class
+| *camel.component.debezium-mysql.configuration.database-blacklist* | 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 snapshot. 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 rea [...]
+| *camel.component.debezium-mysql.configuration.database-history* | 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 snapshot. 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 reaso [...]
+| 
*camel.component.debezium-mysql.configuration.database-history-file-filename* | 
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 snapshot. WARNING: Enabling this option may expose tables 
or fields explicitly blacklisted or masked by including the original SQL 
statement in the change event.  [...]
+| 
*camel.component.debezium-mysql.configuration.database-history-kafka-bootstrap-servers*
 | 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 snapshot. WARNING: Enabling this option may expose tables 
or fields explicitly blacklisted or masked by including the original SQL 
statement in the chan [...]
+| 
*camel.component.debezium-mysql.configuration.database-history-kafka-recovery-attempts*
 | 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 snapshot. WARNING: Enabling this option may expose tables 
or fields explicitly blacklisted or masked by including the original SQL 
statement in the chan [...]
+| 
*camel.component.debezium-mysql.configuration.database-history-kafka-recovery-poll-interval-ms*
 | 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 snapshot. WARNING: Enabling this option may expose tables 
or fields explicitly blacklisted or masked by including the original SQL 
statement in  [...]
+| *camel.component.debezium-mysql.configuration.database-history-kafka-topic* 
| 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 snapshot. WARNING: Enabling this option may expose tables 
or fields explicitly blacklisted or masked by including the original SQL 
statement in the change event. Fo [...]
+| 
*camel.component.debezium-mysql.configuration.database-history-skip-unparseable-ddl*
 | 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 snapshot. WARNING: Enabling this option may expose tables 
or fields explicitly blacklisted or masked by including the original SQL 
statement in the change  [...]
+| 
*camel.component.debezium-mysql.configuration.database-history-store-only-monitored-tables-ddl*
 | 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 snapshot. WARNING: Enabling this option may expose tables 
or fields explicitly blacklisted or masked by including the original SQL 
statement in  [...]
+| *camel.component.debezium-mysql.configuration.database-hostname* | 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 snapshot. 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 reas [...]
+| *camel.component.debezium-mysql.configuration.database-initial-statements* | 
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 snapshot. WARNING: Enabling this option may expose tables 
or fields explicitly blacklisted or masked by including the original SQL 
statement in the change event. For [...]
+| *camel.component.debezium-mysql.configuration.database-jdbc-driver* | 
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 snapshot. 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 r [...]
+| *camel.component.debezium-mysql.configuration.database-password* | 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 snapshot. 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 reas [...]
+| *camel.component.debezium-mysql.configuration.database-port* | 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 snapshot. 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 t [...]
+| *camel.component.debezium-mysql.configuration.database-server-id* | 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 snapshot. 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 rea [...]
+| *camel.component.debezium-mysql.configuration.database-server-id-offset* | 
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 snapshot. WARNING: Enabling this option may expose tables 
or fields explicitly blacklisted or masked by including the original SQL 
statement in the change event. For t [...]
+| *camel.component.debezium-mysql.configuration.database-server-name* | 
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 snapshot. 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 r [...]
+| *camel.component.debezium-mysql.configuration.database-ssl-keystore* | 
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 snapshot. 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  [...]
+| 
*camel.component.debezium-mysql.configuration.database-ssl-keystore-password* | 
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 snapshot. WARNING: Enabling this option may expose tables 
or fields explicitly blacklisted or masked by including the original SQL 
statement in the change event.  [...]
+| *camel.component.debezium-mysql.configuration.database-ssl-mode* | 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 snapshot. 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 reas [...]
+| *camel.component.debezium-mysql.configuration.database-ssl-truststore* | 
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 snapshot. WARNING: Enabling this option may expose tables 
or fields explicitly blacklisted or masked by including the original SQL 
statement in the change event. For thi [...]
+| 
*camel.component.debezium-mysql.configuration.database-ssl-truststore-password* 
| 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 snapshot. WARNING: Enabling this option may expose tables 
or fields explicitly blacklisted or masked by including the original SQL 
statement in the change event [...]
+| *camel.component.debezium-mysql.configuration.database-user* | 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 snapshot. 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 t [...]
+| *camel.component.debezium-mysql.configuration.database-whitelist* | 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 snapshot. 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 rea [...]
+| *camel.component.debezium-mysql.configuration.ddl-parser-mode* | 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 snapshot. 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 [...]
+| *camel.component.debezium-mysql.configuration.decimal-handling-mode* | 
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 snapshot. 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  [...]
+| *camel.component.debezium-mysql.configuration.enable-time-adjuster* | 
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 snapshot. 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 r [...]
+| 
*camel.component.debezium-mysql.configuration.event-deserialization-failure-handling-mode*
 | 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 snapshot. WARNING: Enabling this option may expose tables 
or fields explicitly blacklisted or masked by including the original SQL 
statement in the c [...]
+| *camel.component.debezium-mysql.configuration.gtid-new-channel-position* | 
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 snapshot. WARNING: Enabling this option may expose tables 
or fields explicitly blacklisted or masked by including the original SQL 
statement in the change event. For t [...]
+| *camel.component.debezium-mysql.configuration.gtid-source-excludes* | 
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 snapshot. 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 r [...]
+| *camel.component.debezium-mysql.configuration.gtid-source-filter-dml-events* 
| 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 snapshot. WARNING: Enabling this option may expose tables 
or fields explicitly blacklisted or masked by including the original SQL 
statement in the change event. F [...]
+| *camel.component.debezium-mysql.configuration.gtid-source-includes* | 
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 snapshot. 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 r [...]
+| *camel.component.debezium-mysql.configuration.heartbeat-interval-ms* | 
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 snapshot. 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  [...]
+| *camel.component.debezium-mysql.configuration.heartbeat-topics-prefix* | 
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 snapshot. WARNING: Enabling this option may expose tables 
or fields explicitly blacklisted or masked by including the original SQL 
statement in the change event. For thi [...]
+| *camel.component.debezium-mysql.configuration.include-query* | 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 snapshot. 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 t [...]
+| *camel.component.debezium-mysql.configuration.include-schema-changes* | 
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 snapshot. 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 [...]
+| 
*camel.component.debezium-mysql.configuration.inconsistent-schema-handling-mode*
 | 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 snapshot. WARNING: Enabling this option may expose tables 
or fields explicitly blacklisted or masked by including the original SQL 
statement in the change even [...]
+| *camel.component.debezium-mysql.configuration.internal-key-converter* | The 
Converter class that should be used to serialize and deserialize key data for 
offsets. The default is JSON converter. | 
org.apache.kafka.connect.json.JsonConverter | String
+| *camel.component.debezium-mysql.configuration.internal-value-converter* | 
The Converter class that should be used to serialize and deserialize value data 
for offsets. The default is JSON converter. | 
org.apache.kafka.connect.json.JsonConverter | String
+| *camel.component.debezium-mysql.configuration.max-batch-size* | 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 snapshot. 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  [...]
+| *camel.component.debezium-mysql.configuration.max-queue-size* | 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 snapshot. 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  [...]
+| *camel.component.debezium-mysql.configuration.name* | Unique name for the 
connector. Attempting to register again with the same name will fail. |  | 
String
+| *camel.component.debezium-mysql.configuration.offset-commit-policy* | The 
name of the Java class of the commit policy. It defines when offsets commit has 
to be triggered based on the number of events processed and the time elapsed 
since the last commit. This class must implement the interface 
<…​>.OffsetCommitPolicy. The default is a periodic commit policy based upon 
time intervals. | 
io.debezium.embedded.spi.OffsetCommitPolicy.PeriodicCommitOffsetPolicy | String
+| *camel.component.debezium-mysql.configuration.offset-commit-timeout-ms* | 
Maximum number of milliseconds to wait for records to flush and partition 
offset data to be committed to offset storage before cancelling the process and 
restoring the offset data to be committed in a future attempt. The default is 5 
seconds. | 5000 | Long
+| *camel.component.debezium-mysql.configuration.offset-flush-interval-ms* | 
Interval at which to try committing offsets. The default is 1 minute. | 60000 | 
Long
+| *camel.component.debezium-mysql.configuration.offset-storage* | The name of 
the Java class that is responsible for persistence of connector offsets. | 
org.apache.kafka.connect.storage.FileOffsetBackingStore | String
+| *camel.component.debezium-mysql.configuration.offset-storage-file-name* | 
Path to file where offsets are to be stored. Required when offset.storage is 
set to the FileOffsetBackingStore |  | String
+| *camel.component.debezium-mysql.configuration.offset-storage-partitions* | 
The number of partitions used when creating the offset storage topic. Required 
when offset.storage is set to the <…​>.KafkaOffsetBackingStore. |  | Integer
+| 
*camel.component.debezium-mysql.configuration.offset-storage-replication-factor*
 | Replication factor used when creating the offset storage topic. Required 
when offset.storage is set to the KafkaOffsetBackingStore |  | Integer
+| *camel.component.debezium-mysql.configuration.offset-storage-topic* | The 
name of the Kafka topic where offsets are to be stored. Required when 
offset.storage is set to the KafkaOffsetBackingStore. |  | String
+| *camel.component.debezium-mysql.configuration.poll-interval-ms* | 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 snapshot. 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 reaso [...]
+| *camel.component.debezium-mysql.configuration.snapshot-delay-ms* | 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 snapshot. 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 reas [...]
+| *camel.component.debezium-mysql.configuration.snapshot-fetch-size* | 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 snapshot. 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 re [...]
+| *camel.component.debezium-mysql.configuration.snapshot-locking-mode* | 
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 snapshot. 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  [...]
+| *camel.component.debezium-mysql.configuration.snapshot-mode* | 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 snapshot. 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 t [...]
+| *camel.component.debezium-mysql.configuration.snapshot-new-tables* | 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 snapshot. 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 re [...]
+| *camel.component.debezium-mysql.configuration.table-blacklist* | 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 snapshot. 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 [...]
+| *camel.component.debezium-mysql.configuration.table-ignore-builtin* | 
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 snapshot. 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 r [...]
+| *camel.component.debezium-mysql.configuration.table-whitelist* | 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 snapshot. 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 [...]
+| *camel.component.debezium-mysql.configuration.time-precision-mode* | 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 snapshot. 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 re [...]
+| *camel.component.debezium-mysql.configuration.tombstones-on-delete* | 
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 snapshot. 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 r [...]
+| *camel.component.debezium-mysql.enabled* | Whether to enable auto 
configuration of the debezium-mysql component. This is enabled by default. |  | 
Boolean
+|===
+// spring-boot-auto-configure options: END
+
+For more information about configuration:
+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
+
+=== Consumer headers
+
+The following headers are available when consuming change events from Debezium.
+[width="100%",cols="2m,2m,1m,5",options="header"]
+|===
+| Header constant                           | Header value                     
              | Type        | Description
+| DebeziumConstants.HEADER_IDENTIFIER       | "CamelDebeziumIdentifier"        
              | String      | The identifier of the connector, normally is this 
format "{server-name}.{database-name}.{table-name}".
+| DebeziumConstants.HEADER_KEY              | "CamelDebeziumKey"               
              | Struct      | The key of the event, normally is the table 
Primary Key.
+| DebeziumConstants.HEADER_SOURCE_METADATA  | "CamelDebeziumSourceMetadata"    
              | Map         | The metadata about the source event, for example 
`table` name, database `name`, log position, etc, please refer to the Debezium 
documentation for more info.
+| DebeziumConstants.HEADER_OPERATION        | "CamelDebeziumOperation"         
              | String      | If presents, the type of event operation. Values 
for the connector are `c` for create (or insert), `u` for update, `d` for 
delete or `r` in case of a snapshot event.
+| DebeziumConstants.HEADER_TIMESTAMP        | "CamelDebeziumTimestamp"         
              | Long        | If presents, the time (using the system clock in 
the JVM) at which the connector processed the event.
+| DebeziumConstants.HEADER_BEFORE           | "CamelDebeziumBefore"            
              | Struct     | If presents, contains the state of the row before 
the event occurred.
+|===
+
+== Message body
+The message body if is not `null` (in case of tombstones), it contains the 
state of the row after the event occurred as `Struct` format or `Map` format if 
you use the included Type Converter from `Struct` to `Map` (please look below 
for more explanation).
+
+== Samples
+
+=== Consuming events
+
+Here is a very simple route that you can use in order to listen to Debezium 
events from MySQL connector.
+[source,java]
+----
+from("debezium-mysql:dbz-test-1?offsetStorageFileName=/usr/offset-file-1.dat&databaseHostName=localhost&databaseUser=debezium&databasePassword=dbz&databaseServerName=my-app-connector&databaseHistoryFileName=/usr/history-file-1.dat")
+    .log("Event received from Debezium : ${body}")
+    .log("    with this identifier ${headers.CamelDebeziumIdentifier}")
+    .log("    with these source metadata 
${headers.CamelDebeziumSourceMetadata}")
+    .log("    the event occured upon this operation 
'${headers.CamelDebeziumSourceOperation}'")
+    .log("    on this database '${headers.CamelDebeziumSourceMetadata[db]}' 
and this table '${headers.CamelDebeziumSourceMetadata[table]}'")
+    .log("    with the key ${headers.CamelDebeziumKey}")
+    .log("    the previous value is ${headers.CamelDebeziumBefore}")
+----
+
+By default, the component will emit the events in the body and 
`CamelDebeziumBefore` header as 
https://kafka.apache.org/22/javadoc/org/apache/kafka/connect/data/Struct.html[`Struct`]
 data type, the reasoning behind this, is to perceive the schema information in 
case is needed.
+However, the component as well contains a 
xref:manual::type-converter.adoc[Type Converter] that converts
+from default output type of 
https://kafka.apache.org/22/javadoc/org/apache/kafka/connect/data/Struct.html[`Struct`]
 to `Map` in order to leverage Camel's rich xref:manual::data-format.adoc[Data 
Format] types which many of them work out of box with `Map` data type.
+To use it, you can either add `Map.class` type when you access the message 
e.g: `exchange.getIn().getBody(Map.class)`, or you can convert the body always 
to `Map` from the route builder by adding `.convertBodyTo(Map.class)` to your 
Camel Route DSL after `from` statement.
+
+We mentioned above about the schema, which can be used in case you need to 
perform advance data transformation and the schema is needed for that. If you 
choose not to convert your body to `Map`,
+you can obtain the schema information as 
https://kafka.apache.org/22/javadoc/org/apache/kafka/connect/data/Schema.html[`Schema`]
 type from `Struct` like this:
+[source,java]
+----
+from("debezium-mysql:[name]?[options]])
+    .process(exchange -> {
+        final Struct bodyValue = exchange.getIn().getBody(Struct.class);
+        final Schema schemaValue = bodyValue.schema();
+
+        log.info("Body value is :" + bodyValue);
+        log.info("With Schema : " + schemaValue);
+        log.info("And fields of :" + schemaValue.fields());
+        log.info("Field name has `" + schemaValue.field("name").schema() + "` 
type");
+    });
+----
+
+*Important Note:* This component is a thin wrapper around Debezium Engine as 
mentioned, therefore before using this component in production, you need to 
understand how Debezium works and how configurations can reflect the expected 
behavior, especially in regards to 
https://debezium.io/documentation/reference/0.9/operations/embedded.html#_handling_failures[handling
 failures].
diff --git a/docs/components/modules/ROOT/pages/hdfs-component.adoc 
b/docs/components/modules/ROOT/pages/hdfs-component.adoc
index 7cb005f..20ff38b 100644
--- a/docs/components/modules/ROOT/pages/hdfs-component.adoc
+++ b/docs/components/modules/ROOT/pages/hdfs-component.adoc
@@ -94,7 +94,7 @@ with the following path and query parameters:
 |===
 
 
-=== Query Parameters (45 parameters):
+=== Query Parameters (46 parameters):
 
 
 [width="100%",cols="2,5,^1,2",options="header"]
@@ -103,9 +103,6 @@ with the following path and query parameters:
 | *connectOnStartup* (common) | Whether to connect to the HDFS file system on 
starting the producer/consumer. If false then the connection is created 
on-demand. Notice that HDFS may take up till 15 minutes to establish a 
connection, as it has hardcoded 45 x 20 sec redelivery. By setting this option 
to false allows your application to startup, and not block for up till 15 
minutes. | true | boolean
 | *fileSystemType* (common) | Set to LOCAL to not use HDFS but local 
java.io.File instead. | HDFS | HdfsFileSystemType
 | *fileType* (common) | The file type to use. For more details see Hadoop HDFS 
documentation about the various files types. | NORMAL_FILE | HdfsFileType
-| *kerberosConfigFileLocation* (common) | The location of the kerb5.conf file 
(\https://web.mit.edu/kerberos/krb5-1.12/doc/admin/conf_files/krb5_conf.html) | 
 | String
-| *kerberosKeytabLocation* (common) | The location of the keytab file used to 
authenticate with the kerberos nodes (contains pairs of kerberos principals and 
encrypted keys (which are derived from the Kerberos password)) |  | String
-| *kerberosUsername* (common) | The username used to authenticate with the 
kerberos nodes |  | String
 | *keyType* (common) | The type for the key in case of sequence or map files. 
| NULL | WritableType
 | *namedNodes* (common) | A comma separated list of named nodes (e.g. 
srv11.example.com:8020,srv12.example.com:8020) |  | String
 | *owner* (common) | The file owner must match this owner for the consumer to 
pickup the file. Otherwise the file is skipped. |  | String
@@ -113,6 +110,7 @@ with the following path and query parameters:
 | *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the 
Camel routing Error Handler, which mean any exceptions occurred while the 
consumer is trying to pickup incoming messages, or the likes, will now be 
processed as a message and handled by the routing Error Handler. By default the 
consumer will use the org.apache.camel.spi.ExceptionHandler to deal with 
exceptions, that will be logged at WARN or ERROR level and ignored. | false | 
boolean
 | *pattern* (consumer) | The pattern used for scanning the directory | * | 
String
 | *sendEmptyMessageWhenIdle* (consumer) | If the polling consumer did not poll 
any files, you can enable this option to send an empty message (no body) 
instead. | false | boolean
+| *streamDownload* (consumer) | Sets the download method to use when not using 
a local working directory. If set to true, the remote files are streamed to the 
route as they are read. When set to false, the remote files are loaded into 
memory before being sent into the route. | false | boolean
 | *exceptionHandler* (consumer) | To let the consumer use a custom 
ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this 
option is not in use. By default the consumer will deal with exceptions, that 
will be logged at WARN or ERROR level and ignored. |  | ExceptionHandler
 | *exchangePattern* (consumer) | Sets the exchange pattern when the consumer 
creates an exchange. |  | ExchangePattern
 | *pollStrategy* (consumer) | A pluggable 
org.apache.camel.PollingConsumerPollingStrategy allowing you to provide your 
custom implementation to control error handling usually occurred during the 
poll operation before an Exchange have been created and being routed in Camel. 
|  | PollingConsumerPollStrategy
@@ -145,6 +143,9 @@ with the following path and query parameters:
 | *startScheduler* (scheduler) | Whether the scheduler should be auto started. 
| true | boolean
 | *timeUnit* (scheduler) | Time unit for initialDelay and delay options. | 
MILLISECONDS | TimeUnit
 | *useFixedDelay* (scheduler) | Controls if fixed delay or fixed rate is used. 
See ScheduledExecutorService in JDK for details. | true | boolean
+| *kerberosConfigFileLocation* (security) | The location of the kerb5.conf 
file 
(\https://web.mit.edu/kerberos/krb5-1.12/doc/admin/conf_files/krb5_conf.html) | 
 | String
+| *kerberosKeytabLocation* (security) | The location of the keytab file used 
to authenticate with the kerberos nodes (contains pairs of kerberos principals 
and encrypted keys (which are derived from the Kerberos password)) |  | String
+| *kerberosUsername* (security) | The username used to authenticate with the 
kerberos nodes |  | String
 |===
 // endpoint options: END
 // spring-boot-auto-configure options: START
diff --git a/docs/components/modules/ROOT/pages/index.adoc 
b/docs/components/modules/ROOT/pages/index.adoc
index 0614488..930de68 100644
--- a/docs/components/modules/ROOT/pages/index.adoc
+++ b/docs/components/modules/ROOT/pages/index.adoc
@@ -148,7 +148,7 @@ Number of Components: 299 in 237 JAR artifacts (0 
deprecated)
 
 | xref:dataset-test-component.adoc[DataSet Test] (camel-dataset) | 1.3 | The 
dataset-test component extends the mock component by on startup to pull 
messages from another endpoint to set the expected message bodies.
 
-| xref:debezium-component.adoc[Debezium] (camel-debezium) | 3.0 | Represents a 
Debezium endpoint which is used for interacting with Debezium embedded engine.
+| xref:debezium-mysql-component.adoc[Debezium MySQL Connector] 
(camel-debezium-mysql) | 3.0 | Represents a Debezium MySQL endpoint which is 
used to capture changes in MySQL database so that that applications can see 
those changes and respond to them.
 
 | xref:digitalocean-component.adoc[DigitalOcean] (camel-digitalocean) | 2.19 | 
The DigitalOcean component allows you to manage Droplets and resources within 
the DigitalOcean cloud.
 
diff --git a/docs/components/modules/ROOT/pages/sap-netweaver-component.adoc 
b/docs/components/modules/ROOT/pages/sap-netweaver-component.adoc
index d391c4f..3a2f5f3 100644
--- a/docs/components/modules/ROOT/pages/sap-netweaver-component.adoc
+++ b/docs/components/modules/ROOT/pages/sap-netweaver-component.adoc
@@ -210,7 +210,7 @@ HTML page
 </html>
 ------------------------------------------------------------------------
 
-When running the application you get sampel output:
+When running the application you get sample output:
 
 [source,java]
 -------------------------------