Debezium MySQL Connector
Since Camel 3.0
Only consumer is supported
The Debezium MySQL component is wrapper around Debezium using 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 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.
Note: The Debezium MySQL component is currently not supported in OSGi
Maven users will need to add the following dependency to their pom.xml
for this component.
<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
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:
<dependency>
<groupId>mysql</groupId>
<artifactId>mysql-connector-java</artifactId>
<version>8.0.15</version>
</dependency>Options
The Debezium MySQL Connector component supports 75 options, which are listed below.
| Name | Description | Default | Type |
|---|---|---|---|
additionalProperties (common) |
Additional properties for debezium components in case they can’t be set directly on the camel configurations (e.g: setting Kafka Connect properties needed by Debezium engine, for example setting KafkaOffsetBackingStore), the properties have to be prefixed with additionalProperties.. E.g: additionalProperties.transactional.id=12345&additionalProperties.schema.registry.url=\http://localhost:8811/avro |
Map |
|
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 |
configuration (consumer) |
Allow pre-configured Configurations to be set. |
MySqlConnectorEmbeddedDebeziumConfiguration |
|
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. |
5s |
long |
offsetFlushIntervalMs (consumer) |
Interval at which to try committing offsets. The default is 1 minute. |
60s |
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 |
|
offsetStorageReplicationFactor (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 |
|
basicPropertyBinding (advanced) |
Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities |
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 |
binaryHandlingMode (mysql) |
Specify how binary (blob, binary, etc.) columns should be represented in change events, including:'bytes' represents binary data as byte array (default)'base64' represents binary data as base64-encoded string’hex' represents binary data as hex-encoded (base16) string |
bytes |
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) |
Regular expressions matching columns to exclude from change events |
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. |
1m |
long |
connectTimeoutMs (mysql) |
Maximum time in milliseconds to wait after trying to connect to the database before timing out. |
30s |
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 |
|
databaseHistoryKafkaBootstrap Servers (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 |
|
databaseHistoryKafkaRecovery Attempts (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 |
databaseHistoryKafkaRecovery PollIntervalMs (mysql) |
The number of milliseconds to wait while polling for persisted data during recovery. |
100ms |
int |
databaseHistoryKafkaTopic (mysql) |
The name of the topic for the database schema history |
String |
|
databaseHistorySkipUnparseable Ddl (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 configured Certificate Authority (CA) certificates, or fail if no valid matching CA certificates are found; or’verify_identity' like 'verify_ca' but additionally verify that the server certificate matches the host to which the connection is attempted. |
disabled |
String |
databaseSslTruststore (mysql) |
Location of the Java truststore file containing the collection of CA certificates trusted by this application process (trust store). |
String |
|
databaseSslTruststorePassword (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 |
|
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 consumers. |
precise |
String |
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 |
eventProcessingFailureHandling Mode (mysql) |
Specify how failures during processing of events (i.e. when encountering a corrupted event) should be handled, including:'fail' (the default) an exception indicating the problematic event and its position is raised, causing the connector to be stopped; 'warn' the problematic event and its 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' (the default) connector starts reading channel from first available (not purged) gtid position on the server. |
earliest |
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. |
0ms |
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 |
boolean |
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 include logical description of the new schema and optionally the DDL statement(s).The default is 'true'. This is independent of how the connector internally records database history. |
true |
boolean |
inconsistentSchemaHandlingMode (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;'skip' the problematic event will be skipped. |
fail |
String |
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 |
messageKeyColumns (mysql) |
A semicolon-separated list of expressions that match fully-qualified tables and column(s) to be used as message key. Each expression must match the pattern ':',where the table names could be defined as (DB_NAME.TABLE_NAME) or (SCHEMA_NAME.TABLE_NAME), depending on the specific connector,and the key columns are a comma-separated list of columns representing the custom key. For any table without an explicit key configuration the table’s primary key column(s) will be used as message key.Example: dbserver1.inventory.orderlines:orderId,orderLineId;dbserver1.inventory.orders:id |
String |
|
pollIntervalMs (mysql) |
Frequency in milliseconds to wait for new change events to appear after receiving no events. Defaults to 500ms. |
500ms |
long |
skippedOperations (mysql) |
The comma-separated list of operations to skip during streaming, defined as: 'i' for inserts; 'u' for updates; 'd' for deletes. By default, no operations will be skipped. |
String |
|
snapshotDelayMs (mysql) |
The number of milliseconds to delay before a snapshot will begin. |
0ms |
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 READ transaction even when the lock is no longer held and other operations are updating the database. However, in some cases it may be desirable to block all writes for the entire duration of the snapshot; in such cases set this property to 'extended'. Using a value of 'none' will prevent the connector from acquiring any table locks during the snapshot process. This mode can only be used in combination with snapshot.mode values of 'schema_only' or 'schema_only_recovery' and is only safe to use if no schema changes are happening while the snapshot is taken. |
minimal |
String |
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; 'schema_only' to only take a snapshot of the schema (table structures) but no actual data; '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’never' to specify the connector should never run a snapshot and that upon first startup the connector should read from the beginning of the binlog. The 'never' mode should be used with care, and only when the binlog is known to contain all history. |
initial |
String |
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 it catches up to present time. At this point, both old and new binlog readers will be momentarily halted and new binlog reader will start that will read the binlog for all configured tables. The parallel binlog reader will have a configured server id of 10000 the primary binlog reader’s server id. |
off |
String |
snapshotSelectStatement Overrides (mysql) |
This property contains a comma-separated list of fully-qualified tables (DB_NAME.TABLE_NAME) or (SCHEMA_NAME.TABLE_NAME), depending on thespecific connectors . Select statements for the individual tables are specified in further configuration properties, one for each table, identified by the id 'snapshot.select.statement.overrides.DB_NAME.TABLE_NAME' or 'snapshot.select.statement.overrides.SCHEMA_NAME.TABLE_NAME', respectively. The value of those properties is the select statement to use when retrieving data from the specific table during snapshotting. A possible use case for large append-only tables is setting a specific point where to start (resume) snapshotting, in case a previous snapshotting was interrupted. |
String |
|
sourceStructVersion (mysql) |
A version of the format of the publicly visible source part in the message |
v2 |
String |
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 precision of date and timestamp values is based the database column’s precision; but time fields always use microseconds precision;'connect': always represents time, date and timestamp values using Kafka Connect’s built-in representations for Time, Date, and Timestamp, which uses millisecond precision regardless of the database columns' precision. |
adaptive_time_microseconds |
String |
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 |
The Debezium MySQL Connector endpoint is configured using URI syntax:
debezium-mysql:name
with the following path and query parameters:
Path Parameters (1 parameters):
| Name | Description | Default | Type |
|---|---|---|---|
name |
Required Unique name for the connector. Attempting to register again with the same name will fail. |
String |
Query Parameters (77 parameters):
| Name | Description | Default | Type |
|---|---|---|---|
additionalProperties (common) |
Additional properties for debezium components in case they can’t be set directly on the camel configurations (e.g: setting Kafka Connect properties needed by Debezium engine, for example setting KafkaOffsetBackingStore), the properties have to be prefixed with additionalProperties.. E.g: additionalProperties.transactional.id=12345&additionalProperties.schema.registry.url=\http://localhost:8811/avro |
Map |
|
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. |
5s |
long |
offsetFlushIntervalMs (consumer) |
Interval at which to try committing offsets. The default is 1 minute. |
60s |
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 |
|
offsetStorageReplicationFactor (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. The value can be one of: InOnly, InOut, InOptionalOut |
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 |
binaryHandlingMode (mysql) |
Specify how binary (blob, binary, etc.) columns should be represented in change events, including:'bytes' represents binary data as byte array (default)'base64' represents binary data as base64-encoded string’hex' represents binary data as hex-encoded (base16) string |
bytes |
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) |
Regular expressions matching columns to exclude from change events |
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. |
1m |
long |
connectTimeoutMs (mysql) |
Maximum time in milliseconds to wait after trying to connect to the database before timing out. |
30s |
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 |
|
databaseHistoryKafkaBootstrap Servers (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 |
|
databaseHistoryKafkaRecovery Attempts (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 |
databaseHistoryKafkaRecovery PollIntervalMs (mysql) |
The number of milliseconds to wait while polling for persisted data during recovery. |
100ms |
int |
databaseHistoryKafkaTopic (mysql) |
The name of the topic for the database schema history |
String |
|
databaseHistorySkipUnparseable Ddl (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 configured Certificate Authority (CA) certificates, or fail if no valid matching CA certificates are found; or’verify_identity' like 'verify_ca' but additionally verify that the server certificate matches the host to which the connection is attempted. |
disabled |
String |
databaseSslTruststore (mysql) |
Location of the Java truststore file containing the collection of CA certificates trusted by this application process (trust store). |
String |
|
databaseSslTruststorePassword (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 |
|
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 consumers. |
precise |
String |
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 |
eventProcessingFailureHandling Mode (mysql) |
Specify how failures during processing of events (i.e. when encountering a corrupted event) should be handled, including:'fail' (the default) an exception indicating the problematic event and its position is raised, causing the connector to be stopped; 'warn' the problematic event and its 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' (the default) connector starts reading channel from first available (not purged) gtid position on the server. |
earliest |
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. |
0ms |
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 |
boolean |
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 include logical description of the new schema and optionally the DDL statement(s).The default is 'true'. This is independent of how the connector internally records database history. |
true |
boolean |
inconsistentSchemaHandlingMode (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;'skip' the problematic event will be skipped. |
fail |
String |
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 |
messageKeyColumns (mysql) |
A semicolon-separated list of expressions that match fully-qualified tables and column(s) to be used as message key. Each expression must match the pattern ':',where the table names could be defined as (DB_NAME.TABLE_NAME) or (SCHEMA_NAME.TABLE_NAME), depending on the specific connector,and the key columns are a comma-separated list of columns representing the custom key. For any table without an explicit key configuration the table’s primary key column(s) will be used as message key.Example: dbserver1.inventory.orderlines:orderId,orderLineId;dbserver1.inventory.orders:id |
String |
|
pollIntervalMs (mysql) |
Frequency in milliseconds to wait for new change events to appear after receiving no events. Defaults to 500ms. |
500ms |
long |
skippedOperations (mysql) |
The comma-separated list of operations to skip during streaming, defined as: 'i' for inserts; 'u' for updates; 'd' for deletes. By default, no operations will be skipped. |
String |
|
snapshotDelayMs (mysql) |
The number of milliseconds to delay before a snapshot will begin. |
0ms |
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 READ transaction even when the lock is no longer held and other operations are updating the database. However, in some cases it may be desirable to block all writes for the entire duration of the snapshot; in such cases set this property to 'extended'. Using a value of 'none' will prevent the connector from acquiring any table locks during the snapshot process. This mode can only be used in combination with snapshot.mode values of 'schema_only' or 'schema_only_recovery' and is only safe to use if no schema changes are happening while the snapshot is taken. |
minimal |
String |
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; 'schema_only' to only take a snapshot of the schema (table structures) but no actual data; '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’never' to specify the connector should never run a snapshot and that upon first startup the connector should read from the beginning of the binlog. The 'never' mode should be used with care, and only when the binlog is known to contain all history. |
initial |
String |
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 it catches up to present time. At this point, both old and new binlog readers will be momentarily halted and new binlog reader will start that will read the binlog for all configured tables. The parallel binlog reader will have a configured server id of 10000 the primary binlog reader’s server id. |
off |
String |
snapshotSelectStatement Overrides (mysql) |
This property contains a comma-separated list of fully-qualified tables (DB_NAME.TABLE_NAME) or (SCHEMA_NAME.TABLE_NAME), depending on thespecific connectors . Select statements for the individual tables are specified in further configuration properties, one for each table, identified by the id 'snapshot.select.statement.overrides.DB_NAME.TABLE_NAME' or 'snapshot.select.statement.overrides.SCHEMA_NAME.TABLE_NAME', respectively. The value of those properties is the select statement to use when retrieving data from the specific table during snapshotting. A possible use case for large append-only tables is setting a specific point where to start (resume) snapshotting, in case a previous snapshotting was interrupted. |
String |
|
sourceStructVersion (mysql) |
A version of the format of the publicly visible source part in the message |
v2 |
String |
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 precision of date and timestamp values is based the database column’s precision; but time fields always use microseconds precision;'connect': always represents time, date and timestamp values using Kafka Connect’s built-in representations for Time, Date, and Timestamp, which uses millisecond precision regardless of the database columns' precision. |
adaptive_time_microseconds |
String |
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 |
Message headers
Consumer headers
The following headers are available when consuming change events from Debezium.
| Header constant | Header value | Type | Description |
|---|---|---|---|
|
|
|
The identifier of the connector, normally is this format "{server-name}.{database-name}.{table-name}". |
|
|
|
The key of the event, normally is the table Primary Key. |
|
|
|
The metadata about the source event, for example |
|
|
|
If presents, the type of event operation. Values for the connector are |
|
|
|
If presents, the time (using the system clock in the JVM) at which the connector processed the event. |
|
|
|
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.
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 Struct data type, the reasoning behind this, is to perceive the schema information in case is needed.
However, the component as well contains a Type Converter that converts
from default output type of Struct to Map in order to leverage Camel’s rich 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 Schema type from Struct like this:
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 handling failures.
Spring Boot Auto-Configuration
When using debezium-mysql with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
<dependency>
<groupId>org.apache.camel.springboot</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 76 options, which are listed below.
| Name | Description | Default | Type |
|---|---|---|---|
camel.component.debezium-mysql.additional-properties |
Additional properties for debezium components in case they can’t be set directly on the camel configurations (e.g: setting Kafka Connect properties needed by Debezium engine, for example setting KafkaOffsetBackingStore), the properties have to be prefixed with additionalProperties.. E.g: additionalProperties.transactional.id=12345&additionalProperties.schema.registry.url=\http://localhost:8811/avro |
Map |
|
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.bigint-unsigned-handling-mode |
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 |
camel.component.debezium-mysql.binary-handling-mode |
Specify how binary (blob, binary, etc.) columns should be represented in change events, including:'bytes' represents binary data as byte array (default)'base64' represents binary data as base64-encoded string’hex' represents binary data as hex-encoded (base16) string |
bytes |
String |
camel.component.debezium-mysql.binlog-buffer-size |
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 |
Integer |
camel.component.debezium-mysql.bridge-error-handler |
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 |
camel.component.debezium-mysql.column-blacklist |
Regular expressions matching columns to exclude from change events |
String |
|
camel.component.debezium-mysql.configuration |
Allow pre-configured Configurations to be set. The option is a org.apache.camel.component.debezium.configuration.MySqlConnectorEmbeddedDebeziumConfiguration type. |
String |
|
camel.component.debezium-mysql.connect-keep-alive |
Whether a separate thread should be used to ensure the connection is kept alive. |
true |
Boolean |
camel.component.debezium-mysql.connect-keep-alive-interval-ms |
Interval in milliseconds to wait for connection checking if keep alive thread is used. The option is a long type. |
1m |
String |
camel.component.debezium-mysql.connect-timeout-ms |
Maximum time in milliseconds to wait after trying to connect to the database before timing out. The option is a int type. |
30s |
String |
camel.component.debezium-mysql.database-blacklist |
Description is not available here, please check Debezium website for corresponding key 'database.blacklist' description. |
String |
|
camel.component.debezium-mysql.database-history |
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 |
camel.component.debezium-mysql.database-history-file-filename |
The path to the file that will be used to record the database history |
String |
|
camel.component.debezium-mysql.database-history-kafka-bootstrap-servers |
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 |
|
camel.component.debezium-mysql.database-history-kafka-recovery-attempts |
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 |
Integer |
camel.component.debezium-mysql.database-history-kafka-recovery-poll-interval-ms |
The number of milliseconds to wait while polling for persisted data during recovery. The option is a int type. |
100ms |
String |
camel.component.debezium-mysql.database-history-kafka-topic |
The name of the topic for the database schema history |
String |
|
camel.component.debezium-mysql.database-history-skip-unparseable-ddl |
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 |
camel.component.debezium-mysql.database-history-store-only-monitored-tables-ddl |
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 |
camel.component.debezium-mysql.database-hostname |
Resolvable hostname or IP address of the MySQL database server. |
String |
|
camel.component.debezium-mysql.database-initial-statements |
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 |
|
camel.component.debezium-mysql.database-jdbc-driver |
JDBC Driver class name used to connect to the MySQL database server. |
class com.mysql.cj.jdbc.Driver |
String |
camel.component.debezium-mysql.database-password |
Password of the MySQL database user to be used when connecting to the database. |
String |
|
camel.component.debezium-mysql.database-port |
Port of the MySQL database server. |
3306 |
Integer |
camel.component.debezium-mysql.database-server-id |
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 |
|
camel.component.debezium-mysql.database-server-id-offset |
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 |
camel.component.debezium-mysql.database-server-name |
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 |
|
camel.component.debezium-mysql.database-ssl-keystore |
Location of the Java keystore file containing an application process’s own certificate and private key. |
String |
|
camel.component.debezium-mysql.database-ssl-keystore-password |
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 |
|
camel.component.debezium-mysql.database-ssl-mode |
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 configured Certificate Authority (CA) certificates, or fail if no valid matching CA certificates are found; or’verify_identity' like 'verify_ca' but additionally verify that the server certificate matches the host to which the connection is attempted. |
disabled |
String |
camel.component.debezium-mysql.database-ssl-truststore |
Location of the Java truststore file containing the collection of CA certificates trusted by this application process (trust store). |
String |
|
camel.component.debezium-mysql.database-ssl-truststore-password |
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 |
|
camel.component.debezium-mysql.database-user |
Name of the MySQL database user to be used when connecting to the database. |
String |
|
camel.component.debezium-mysql.database-whitelist |
The databases for which changes are to be captured |
String |
|
camel.component.debezium-mysql.decimal-handling-mode |
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 consumers. |
precise |
String |
camel.component.debezium-mysql.enable-time-adjuster |
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 |
camel.component.debezium-mysql.enabled |
Whether to enable auto configuration of the debezium-mysql component. This is enabled by default. |
Boolean |
|
camel.component.debezium-mysql.event-deserialization-failure-handling-mode |
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 |
camel.component.debezium-mysql.event-processing-failure-handling-mode |
Specify how failures during processing of events (i.e. when encountering a corrupted event) should be handled, including:'fail' (the default) an exception indicating the problematic event and its position is raised, causing the connector to be stopped; 'warn' the problematic event and its position will be logged and the event will be skipped;'ignore' the problematic event will be skipped. |
fail |
String |
camel.component.debezium-mysql.gtid-new-channel-position |
If set to 'latest', when connector sees new GTID, it will start consuming gtid channel from the server latest executed gtid position. If 'earliest' (the default) connector starts reading channel from first available (not purged) gtid position on the server. |
earliest |
String |
camel.component.debezium-mysql.gtid-source-excludes |
The source UUIDs used to exclude GTID ranges when determine the starting position in the MySQL server’s binlog. |
String |
|
camel.component.debezium-mysql.gtid-source-filter-dml-events |
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 |
camel.component.debezium-mysql.gtid-source-includes |
The source UUIDs used to include GTID ranges when determine the starting position in the MySQL server’s binlog. |
String |
|
camel.component.debezium-mysql.heartbeat-interval-ms |
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. The option is a int type. |
0ms |
String |
camel.component.debezium-mysql.heartbeat-topics-prefix |
The prefix that is used to name heartbeat topics.Defaults to __debezium-heartbeat. |
__debezium-heartbeat |
String |
camel.component.debezium-mysql.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 the default value is 'false'. |
false |
Boolean |
camel.component.debezium-mysql.include-schema-changes |
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 include logical description of the new schema and optionally the DDL statement(s).The default is 'true'. This is independent of how the connector internally records database history. |
true |
Boolean |
camel.component.debezium-mysql.inconsistent-schema-handling-mode |
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;'skip' the problematic event will be skipped. |
fail |
String |
camel.component.debezium-mysql.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.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.max-batch-size |
Maximum size of each batch of source records. Defaults to 2048. |
2048 |
Integer |
camel.component.debezium-mysql.max-queue-size |
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 |
Integer |
camel.component.debezium-mysql.message-key-columns |
A semicolon-separated list of expressions that match fully-qualified tables and column(s) to be used as message key. Each expression must match the pattern ':',where the table names could be defined as (DB_NAME.TABLE_NAME) or (SCHEMA_NAME.TABLE_NAME), depending on the specific connector,and the key columns are a comma-separated list of columns representing the custom key. For any table without an explicit key configuration the table’s primary key column(s) will be used as message key.Example: dbserver1.inventory.orderlines:orderId,orderLineId;dbserver1.inventory.orders:id |
String |
|
camel.component.debezium-mysql.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.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. The option is a long type. |
5s |
String |
camel.component.debezium-mysql.offset-flush-interval-ms |
Interval at which to try committing offsets. The default is 1 minute. The option is a long type. |
60s |
String |
camel.component.debezium-mysql.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.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.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.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.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.poll-interval-ms |
Frequency in milliseconds to wait for new change events to appear after receiving no events. Defaults to 500ms. The option is a long type. |
500ms |
String |
camel.component.debezium-mysql.skipped-operations |
The comma-separated list of operations to skip during streaming, defined as: 'i' for inserts; 'u' for updates; 'd' for deletes. By default, no operations will be skipped. |
String |
|
camel.component.debezium-mysql.snapshot-delay-ms |
The number of milliseconds to delay before a snapshot will begin. The option is a long type. |
0ms |
String |
camel.component.debezium-mysql.snapshot-fetch-size |
The maximum number of records that should be loaded into memory while performing a snapshot |
Integer |
|
camel.component.debezium-mysql.snapshot-locking-mode |
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 READ transaction even when the lock is no longer held and other operations are updating the database. However, in some cases it may be desirable to block all writes for the entire duration of the snapshot; in such cases set this property to 'extended'. Using a value of 'none' will prevent the connector from acquiring any table locks during the snapshot process. This mode can only be used in combination with snapshot.mode values of 'schema_only' or 'schema_only_recovery' and is only safe to use if no schema changes are happening while the snapshot is taken. |
minimal |
String |
camel.component.debezium-mysql.snapshot-mode |
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; 'schema_only' to only take a snapshot of the schema (table structures) but no actual data; '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’never' to specify the connector should never run a snapshot and that upon first startup the connector should read from the beginning of the binlog. The 'never' mode should be used with care, and only when the binlog is known to contain all history. |
initial |
String |
camel.component.debezium-mysql.snapshot-new-tables |
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 it catches up to present time. At this point, both old and new binlog readers will be momentarily halted and new binlog reader will start that will read the binlog for all configured tables. The parallel binlog reader will have a configured server id of 10000 the primary binlog reader’s server id. |
off |
String |
camel.component.debezium-mysql.snapshot-select-statement-overrides |
This property contains a comma-separated list of fully-qualified tables (DB_NAME.TABLE_NAME) or (SCHEMA_NAME.TABLE_NAME), depending on thespecific connectors . Select statements for the individual tables are specified in further configuration properties, one for each table, identified by the id 'snapshot.select.statement.overrides.DB_NAME.TABLE_NAME' or 'snapshot.select.statement.overrides.SCHEMA_NAME.TABLE_NAME', respectively. The value of those properties is the select statement to use when retrieving data from the specific table during snapshotting. A possible use case for large append-only tables is setting a specific point where to start (resume) snapshotting, in case a previous snapshotting was interrupted. |
String |
|
camel.component.debezium-mysql.source-struct-version |
A version of the format of the publicly visible source part in the message |
v2 |
String |
camel.component.debezium-mysql.table-blacklist |
Description is not available here, please check Debezium website for corresponding key 'table.blacklist' description. |
String |
|
camel.component.debezium-mysql.table-ignore-builtin |
Flag specifying whether built-in tables should be ignored. |
true |
Boolean |
camel.component.debezium-mysql.table-whitelist |
The tables for which changes are to be captured |
String |
|
camel.component.debezium-mysql.time-precision-mode |
Time, date and timestamps can be represented with different kinds of precisions, including:'adaptive_time_microseconds': the precision of date and timestamp values is based the database column’s precision; but time fields always use microseconds precision;'connect': always represents time, date and timestamp values using Kafka Connect’s built-in representations for Time, Date, and Timestamp, which uses millisecond precision regardless of the database columns' precision. |
adaptive_time_microseconds |
String |
camel.component.debezium-mysql.tombstones-on-delete |
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 |