Class MySqlConnectorEmbeddedDebeziumConfiguration
java.lang.Object
org.apache.camel.component.debezium.configuration.EmbeddedDebeziumConfiguration
org.apache.camel.component.debezium.configuration.MySqlConnectorEmbeddedDebeziumConfiguration
- All Implemented Interfaces:
Cloneable
@UriParams
public class MySqlConnectorEmbeddedDebeziumConfiguration
extends org.apache.camel.component.debezium.configuration.EmbeddedDebeziumConfiguration
-
Constructor Summary
Constructors -
Method Summary
Modifier and TypeMethodDescriptionprotected Classprotected io.debezium.config.ConfigurationintlongintlongintintintlonglongintintintintlongintlongintlonglongintlongintbooleanbooleanbooleanbooleanbooleanbooleanbooleanbooleanbooleanbooleanbooleanbooleanbooleanbooleanvoidsetBigintUnsignedHandlingMode(String bigintUnsignedHandlingMode) 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.voidsetBinaryHandlingMode(String binaryHandlingMode) 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) stringvoidsetBinlogBufferSize(int binlogBufferSize) 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.voidsetColumnBlacklist(String columnBlacklist) Regular expressions matching columns to exclude from change events (deprecated, use "column.exclude.list" instead)voidsetColumnExcludeList(String columnExcludeList) Regular expressions matching columns to exclude from change eventsvoidsetColumnIncludeList(String columnIncludeList) Regular expressions matching columns to include in change eventsvoidsetColumnPropagateSourceType(String columnPropagateSourceType) A comma-separated list of regular expressions matching fully-qualified names of columns that adds the columns original type and original length as parameters to the corresponding field schemas in the emitted change records.voidsetColumnWhitelist(String columnWhitelist) Regular expressions matching columns to include in change events (deprecated, use "column.include.list" instead)voidsetConnectKeepAlive(boolean connectKeepAlive) Whether a separate thread should be used to ensure the connection is kept alive.voidsetConnectKeepAliveIntervalMs(long connectKeepAliveIntervalMs) Interval for connection checking if keep alive thread is used, given in milliseconds Defaults to 1 minute (60,000 ms).voidsetConnectTimeoutMs(int connectTimeoutMs) Maximum time to wait after trying to connect to the database before timing out, given in milliseconds.voidsetConverters(String converters) Optional list of custom converters that would be used instead of default ones.voidsetDatabaseExcludeList(String databaseExcludeList) A comma-separated list of regular expressions that match database names to be excluded from monitoringvoidsetDatabaseHistory(String databaseHistory) The name of the DatabaseHistory class that should be used to store and recover database schema changes.voidsetDatabaseHistoryFileFilename(String databaseHistoryFileFilename) The path to the file that will be used to record the database historyvoidsetDatabaseHistoryKafkaBootstrapServers(String databaseHistoryKafkaBootstrapServers) 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.voidsetDatabaseHistoryKafkaQueryTimeoutMs(long databaseHistoryKafkaQueryTimeoutMs) The number of milliseconds to wait while fetching cluster information using Kafka admin client.voidsetDatabaseHistoryKafkaRecoveryAttempts(int databaseHistoryKafkaRecoveryAttempts) The number of attempts in a row that no data are returned from Kafka before recover completes.voidsetDatabaseHistoryKafkaRecoveryPollIntervalMs(int databaseHistoryKafkaRecoveryPollIntervalMs) The number of milliseconds to wait while polling for persisted data during recovery.voidsetDatabaseHistoryKafkaTopic(String databaseHistoryKafkaTopic) The name of the topic for the database schema historyvoidsetDatabaseHistorySkipUnparseableDdl(boolean databaseHistorySkipUnparseableDdl) 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.voidsetDatabaseHistoryStoreOnlyCapturedTablesDdl(boolean databaseHistoryStoreOnlyCapturedTablesDdl) Controls what DDL will Debezium store in database history.voidsetDatabaseHistoryStoreOnlyMonitoredTablesDdl(boolean databaseHistoryStoreOnlyMonitoredTablesDdl) Controls what DDL will Debezium store in database history.voidsetDatabaseHostname(String databaseHostname) Resolvable hostname or IP address of the database server.voidsetDatabaseIncludeList(String databaseIncludeList) The databases for which changes are to be capturedvoidsetDatabaseInitialStatements(String databaseInitialStatements) A semicolon separated list of SQL statements to be executed when a JDBC connection (not binlog reading connection) to the database is established.voidsetDatabaseJdbcDriver(String databaseJdbcDriver) JDBC Driver class name used to connect to the MySQL database server.voidsetDatabasePassword(String databasePassword) Password of the database user to be used when connecting to the database.voidsetDatabasePort(int databasePort) Port of the database server.voidsetDatabaseServerId(long databaseServerId) A numeric ID of this database client, which must be unique across all currently-running database processes in the cluster.voidsetDatabaseServerIdOffset(long databaseServerIdOffset) Only relevant if parallel snapshotting is configured.voidsetDatabaseServerName(String databaseServerName) Unique name that identifies the database server and all recorded offsets, and that is used as a prefix for all schemas and topics.voidsetDatabaseSslKeystore(String databaseSslKeystore) The location of the key store file.voidsetDatabaseSslKeystorePassword(String databaseSslKeystorePassword) The password for the key store file.voidsetDatabaseSslMode(String databaseSslMode) Whether to use an encrypted connection to MySQL.voidsetDatabaseSslTruststore(String databaseSslTruststore) The location of the trust store file for the server certificate verification.voidsetDatabaseSslTruststorePassword(String databaseSslTruststorePassword) The password for the trust store file.voidsetDatabaseUser(String databaseUser) Name of the database user to be used when connecting to the database.voidsetDatatypePropagateSourceType(String datatypePropagateSourceType) A comma-separated list of regular expressions matching the database-specific data type names that adds the data type's original type and original length as parameters to the corresponding field schemas in the emitted change records.voidsetDecimalHandlingMode(String decimalHandlingMode) 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.voidsetEnableTimeAdjuster(boolean enableTimeAdjuster) MySQL allows user to insert year value as either 2-digit or 4-digit.voidsetEventDeserializationFailureHandlingMode(String eventDeserializationFailureHandlingMode) Specify how failures during deserialization of binlog events (i.e.voidsetEventProcessingFailureHandlingMode(String eventProcessingFailureHandlingMode) Specify how failures during processing of events (i.e.voidsetGtidSourceExcludes(String gtidSourceExcludes) The source UUIDs used to exclude GTID ranges when determine the starting position in the MySQL server's binlog.voidsetGtidSourceFilterDmlEvents(boolean gtidSourceFilterDmlEvents) 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.voidsetGtidSourceIncludes(String gtidSourceIncludes) The source UUIDs used to include GTID ranges when determine the starting position in the MySQL server's binlog.voidsetHeartbeatActionQuery(String heartbeatActionQuery) The query executed with every heartbeat.voidsetHeartbeatIntervalMs(int heartbeatIntervalMs) Length of an interval in milli-seconds in in which the connector periodically sends heartbeat messages to a heartbeat topic.voidsetHeartbeatTopicsPrefix(String heartbeatTopicsPrefix) The prefix that is used to name heartbeat topics.Defaults to __debezium-heartbeat.voidsetIncludeQuery(boolean includeQuery) Whether the connector should include the original SQL query that generated the change event.voidsetIncludeSchemaChanges(boolean includeSchemaChanges) Whether the connector should publish changes in the database schema to a Kafka topic with the same name as the database server ID.voidsetIncludeSchemaComments(boolean includeSchemaComments) Whether the connector parse table and column's comment to metadata object.Note: Enable this option will bring the implications on memory usage.voidsetInconsistentSchemaHandlingMode(String inconsistentSchemaHandlingMode) Specify how binlog events that belong to a table missing from internal schema representation (i.e.voidsetIncrementalSnapshotAllowSchemaChanges(boolean incrementalSnapshotAllowSchemaChanges) Detect schema change during an incremental snapshot and re-select a current chunk to avoid locking DDLs.voidsetIncrementalSnapshotChunkSize(int incrementalSnapshotChunkSize) The maximum size of chunk for incremental snapshottingvoidsetMaxBatchSize(int maxBatchSize) Maximum size of each batch of source records.voidsetMaxQueueSize(int maxQueueSize) Maximum size of the queue for change events read from the database log but not yet recorded or forwarded.voidsetMaxQueueSizeInBytes(long maxQueueSizeInBytes) Maximum size of the queue in bytes for change events read from the database log but not yet recorded or forwarded.voidsetMessageKeyColumns(String messageKeyColumns) A semicolon-separated list of expressions that match fully-qualified tables and column(s) to be used as message key.voidsetMinRowCountToStreamResults(int minRowCountToStreamResults) The number of rows a table must contain to stream results rather than pull all into memory during snapshots.voidsetPollIntervalMs(long pollIntervalMs) Time to wait for new change events to appear after receiving no events, given in milliseconds.voidsetProvideTransactionMetadata(boolean provideTransactionMetadata) Enables transaction metadata extraction together with event countingvoidsetQueryFetchSize(int queryFetchSize) The maximum number of records that should be loaded into memory while streaming.voidsetRetriableRestartConnectorWaitMs(long retriableRestartConnectorWaitMs) Time to wait before restarting connector after retriable exception occurs.voidsetSanitizeFieldNames(boolean sanitizeFieldNames) Whether field names will be sanitized to Avro naming conventionsvoidsetSchemaNameAdjustmentMode(String schemaNameAdjustmentMode) Specify how schema names should be adjusted for compatibility with the message converter used by the connector, including:'avro' replaces the characters that cannot be used in the Avro type name with underscore (default)'none' does not apply any adjustmentvoidsetSignalDataCollection(String signalDataCollection) The name of the data collection that is used to send signals/commands to Debezium.voidsetSkippedOperations(String skippedOperations) The comma-separated list of operations to skip during streaming, defined as: 'c' for inserts/create; 'u' for updates; 'd' for deletes, 't' for truncates, and 'none' to indicate nothing skipped.voidsetSnapshotDelayMs(long snapshotDelayMs) A delay period before a snapshot will begin, given in milliseconds.voidsetSnapshotFetchSize(int snapshotFetchSize) The maximum number of records that should be loaded into memory while performing a snapshotvoidsetSnapshotIncludeCollectionList(String snapshotIncludeCollectionList) this setting must be set to specify a list of tables/collections whose snapshot must be taken on creating or restarting the connector.voidsetSnapshotLockingMode(String snapshotLockingMode) Controls how long the connector holds onto the global read lock while it is performing a snapshot.voidsetSnapshotLockTimeoutMs(long snapshotLockTimeoutMs) The maximum number of millis to wait for table locks at the beginning of a snapshot.voidsetSnapshotMaxThreads(int snapshotMaxThreads) The maximum number of threads used to perform the snapshot.voidsetSnapshotMode(String snapshotMode) The criteria for running a snapshot upon startup of the connector.voidsetSnapshotNewTables(String snapshotNewTables) BETA FEATURE: On connector restart, the connector will check if there have been any new tables added to the configuration, and snapshot them.voidsetSnapshotSelectStatementOverrides(String snapshotSelectStatementOverrides) This property contains a comma-separated list of fully-qualified tables (DB_NAME.TABLE_NAME) or (SCHEMA_NAME.TABLE_NAME), depending on thespecific connectors.voidsetSourceStructVersion(String sourceStructVersion) A version of the format of the publicly visible source part in the messagevoidsetTableBlacklist(String tableBlacklist) A comma-separated list of regular expressions that match the fully-qualified names of tables to be excluded from monitoring (deprecated, use "table.exclude.list" instead)voidsetTableExcludeList(String tableExcludeList) A comma-separated list of regular expressions that match the fully-qualified names of tables to be excluded from monitoringvoidsetTableIgnoreBuiltin(boolean tableIgnoreBuiltin) Flag specifying whether built-in tables should be ignored.voidsetTableIncludeList(String tableIncludeList) The tables for which changes are to be capturedvoidsetTableWhitelist(String tableWhitelist) The tables for which changes are to be captured (deprecated, use "table.include.list" instead)voidsetTimePrecisionMode(String timePrecisionMode) 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.voidsetTombstonesOnDelete(boolean tombstonesOnDelete) Whether delete operations should be represented by a delete event and a subsquenttombstone event (true) or only by a delete event (false).voidsetTransactionTopic(String transactionTopic) The name of the transaction metadata topic.protected org.apache.camel.component.debezium.configuration.ConfigurationValidationMethods inherited from class org.apache.camel.component.debezium.configuration.EmbeddedDebeziumConfiguration
addPropertyIfNotNull, addPropertyIfNotNull, copy, createDebeziumConfiguration, getAdditionalProperties, getConnectorClass, getInternalKeyConverter, getInternalValueConverter, getName, getOffsetCommitPolicy, getOffsetCommitTimeoutMs, getOffsetFlushIntervalMs, getOffsetStorage, getOffsetStorageFileName, getOffsetStoragePartitions, getOffsetStorageReplicationFactor, getOffsetStorageTopic, isFieldValueNotSet, setAdditionalProperties, setConnectorClass, setInternalKeyConverter, setInternalValueConverter, setName, setOffsetCommitPolicy, setOffsetCommitTimeoutMs, setOffsetFlushIntervalMs, setOffsetStorage, setOffsetStorageFileName, setOffsetStoragePartitions, setOffsetStorageReplicationFactor, setOffsetStorageTopic, validateConfiguration
-
Constructor Details
-
MySqlConnectorEmbeddedDebeziumConfiguration
public MySqlConnectorEmbeddedDebeziumConfiguration()
-
-
Method Details
-
setSnapshotLockingMode
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. -
getSnapshotLockingMode
-
setMessageKeyColumns
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 '<fully-qualified table name>:',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 -
getMessageKeyColumns
-
setQueryFetchSize
public void setQueryFetchSize(int queryFetchSize) The maximum number of records that should be loaded into memory while streaming. A value of `0` uses the default JDBC fetch size. -
getQueryFetchSize
public int getQueryFetchSize() -
setColumnBlacklist
Regular expressions matching columns to exclude from change events (deprecated, use "column.exclude.list" instead) -
getColumnBlacklist
-
setTableBlacklist
A comma-separated list of regular expressions that match the fully-qualified names of tables to be excluded from monitoring (deprecated, use "table.exclude.list" instead) -
getTableBlacklist
-
setIncludeSchemaChanges
public void setIncludeSchemaChanges(boolean includeSchemaChanges) 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. -
isIncludeSchemaChanges
public boolean isIncludeSchemaChanges() -
setGtidSourceIncludes
The source UUIDs used to include GTID ranges when determine the starting position in the MySQL server's binlog. -
getGtidSourceIncludes
-
setDatabaseJdbcDriver
JDBC Driver class name used to connect to the MySQL database server. -
getDatabaseJdbcDriver
-
setHeartbeatActionQuery
The query executed with every heartbeat. -
getHeartbeatActionQuery
-
setPollIntervalMs
public void setPollIntervalMs(long pollIntervalMs) Time to wait for new change events to appear after receiving no events, given in milliseconds. Defaults to 500 ms. -
getPollIntervalMs
public long getPollIntervalMs() -
setDatabaseHistoryKafkaRecoveryPollIntervalMs
public void setDatabaseHistoryKafkaRecoveryPollIntervalMs(int databaseHistoryKafkaRecoveryPollIntervalMs) The number of milliseconds to wait while polling for persisted data during recovery. -
getDatabaseHistoryKafkaRecoveryPollIntervalMs
public int getDatabaseHistoryKafkaRecoveryPollIntervalMs() -
setSignalDataCollection
The name of the data collection that is used to send signals/commands to Debezium. Signaling is disabled when not set. -
getSignalDataCollection
-
setDatabaseInitialStatements
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. -
getDatabaseInitialStatements
-
setDatabaseHistoryStoreOnlyCapturedTablesDdl
public void setDatabaseHistoryStoreOnlyCapturedTablesDdl(boolean databaseHistoryStoreOnlyCapturedTablesDdl) Controls what DDL will Debezium store in database history. By default (false) Debezium will store all incoming DDL statements. If set to true, then only DDL that manipulates a captured table will be stored. -
isDatabaseHistoryStoreOnlyCapturedTablesDdl
public boolean isDatabaseHistoryStoreOnlyCapturedTablesDdl() -
setConverters
Optional list of custom converters that would be used instead of default ones. The converters are defined using '<converter.prefix>.type' config option and configured using options '<converter.prefix>. -
getConverters
-
setHeartbeatTopicsPrefix
The prefix that is used to name heartbeat topics.Defaults to __debezium-heartbeat. -
getHeartbeatTopicsPrefix
-
setBinlogBufferSize
public void setBinlogBufferSize(int binlogBufferSize) 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). -
getBinlogBufferSize
public int getBinlogBufferSize() -
setSnapshotFetchSize
public void setSnapshotFetchSize(int snapshotFetchSize) The maximum number of records that should be loaded into memory while performing a snapshot -
getSnapshotFetchSize
public int getSnapshotFetchSize() -
setSnapshotLockTimeoutMs
public void setSnapshotLockTimeoutMs(long snapshotLockTimeoutMs) The maximum number of millis to wait for table locks at the beginning of a snapshot. If locks cannot be acquired in this time frame, the snapshot will be aborted. Defaults to 10 seconds -
getSnapshotLockTimeoutMs
public long getSnapshotLockTimeoutMs() -
setDatabaseHistoryKafkaQueryTimeoutMs
public void setDatabaseHistoryKafkaQueryTimeoutMs(long databaseHistoryKafkaQueryTimeoutMs) The number of milliseconds to wait while fetching cluster information using Kafka admin client. -
getDatabaseHistoryKafkaQueryTimeoutMs
public long getDatabaseHistoryKafkaQueryTimeoutMs() -
setDatabaseUser
Name of the database user to be used when connecting to the database. -
getDatabaseUser
-
setDatatypePropagateSourceType
A comma-separated list of regular expressions matching the database-specific data type names that adds the data type's original type and original length as parameters to the corresponding field schemas in the emitted change records. -
getDatatypePropagateSourceType
-
setSanitizeFieldNames
public void setSanitizeFieldNames(boolean sanitizeFieldNames) Whether field names will be sanitized to Avro naming conventions -
isSanitizeFieldNames
public boolean isSanitizeFieldNames() -
setGtidSourceExcludes
The source UUIDs used to exclude GTID ranges when determine the starting position in the MySQL server's binlog. -
getGtidSourceExcludes
-
setSnapshotSelectStatementOverrides
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. -
getSnapshotSelectStatementOverrides
-
setDatabaseHistoryKafkaBootstrapServers
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. -
getDatabaseHistoryKafkaBootstrapServers
-
setDatabaseSslKeystore
The location of the key store file. This is optional and can be used for two-way authentication between the client and the MySQL Server. -
getDatabaseSslKeystore
-
setSourceStructVersion
A version of the format of the publicly visible source part in the message -
getSourceStructVersion
-
setHeartbeatIntervalMs
public void setHeartbeatIntervalMs(int heartbeatIntervalMs) 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. -
getHeartbeatIntervalMs
public int getHeartbeatIntervalMs() -
setColumnWhitelist
Regular expressions matching columns to include in change events (deprecated, use "column.include.list" instead) -
getColumnWhitelist
-
setDatabaseSslTruststorePassword
The password for the trust store file. Used to check the integrity of the truststore, and unlock the truststore. -
getDatabaseSslTruststorePassword
-
setIncrementalSnapshotAllowSchemaChanges
public void setIncrementalSnapshotAllowSchemaChanges(boolean incrementalSnapshotAllowSchemaChanges) Detect schema change during an incremental snapshot and re-select a current chunk to avoid locking DDLs. Note that changes to a primary key are not supported and can cause incorrect results if performed during an incremental snapshot. Another limitation is that if a schema change affects only columns' default values, then the change won't be detected until the DDL is processed from the binlog stream. This doesn't affect the snapshot events' values, but the schema of snapshot events may have outdated defaults. -
isIncrementalSnapshotAllowSchemaChanges
public boolean isIncrementalSnapshotAllowSchemaChanges() -
setColumnIncludeList
Regular expressions matching columns to include in change events -
getColumnIncludeList
-
setEnableTimeAdjuster
public void setEnableTimeAdjuster(boolean enableTimeAdjuster) 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 -
isEnableTimeAdjuster
public boolean isEnableTimeAdjuster() -
setColumnPropagateSourceType
A comma-separated list of regular expressions matching fully-qualified names of columns that adds the columns original type and original length as parameters to the corresponding field schemas in the emitted change records. -
getColumnPropagateSourceType
-
setInconsistentSchemaHandlingMode
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. -
getInconsistentSchemaHandlingMode
-
setMinRowCountToStreamResults
public void setMinRowCountToStreamResults(int minRowCountToStreamResults) The number of rows a table must contain to stream results rather than pull all into memory during snapshots. Defaults to 1,000. Use 0 to stream all results and completely avoid checking the size of each table. -
getMinRowCountToStreamResults
public int getMinRowCountToStreamResults() -
setTableExcludeList
A comma-separated list of regular expressions that match the fully-qualified names of tables to be excluded from monitoring -
getTableExcludeList
-
setDatabasePassword
Password of the database user to be used when connecting to the database. -
getDatabasePassword
-
setDatabaseExcludeList
A comma-separated list of regular expressions that match database names to be excluded from monitoring -
getDatabaseExcludeList
-
setDatabaseHistoryStoreOnlyMonitoredTablesDdl
public void setDatabaseHistoryStoreOnlyMonitoredTablesDdl(boolean databaseHistoryStoreOnlyMonitoredTablesDdl) Controls what DDL will Debezium store in database history. By default (false) Debezium will store all incoming DDL statements. If set to true, then only DDL that manipulates a monitored table will be stored (deprecated, use "database.history.store.only.captured.tables.ddl" instead) -
isDatabaseHistoryStoreOnlyMonitoredTablesDdl
public boolean isDatabaseHistoryStoreOnlyMonitoredTablesDdl() -
setGtidSourceFilterDmlEvents
public void setGtidSourceFilterDmlEvents(boolean gtidSourceFilterDmlEvents) 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. -
isGtidSourceFilterDmlEvents
public boolean isGtidSourceFilterDmlEvents() -
setMaxBatchSize
public void setMaxBatchSize(int maxBatchSize) Maximum size of each batch of source records. Defaults to 2048. -
getMaxBatchSize
public int getMaxBatchSize() -
setSkippedOperations
The comma-separated list of operations to skip during streaming, defined as: 'c' for inserts/create; 'u' for updates; 'd' for deletes, 't' for truncates, and 'none' to indicate nothing skipped. By default, no operations will be skipped. -
getSkippedOperations
-
setConnectKeepAlive
public void setConnectKeepAlive(boolean connectKeepAlive) Whether a separate thread should be used to ensure the connection is kept alive. -
isConnectKeepAlive
public boolean isConnectKeepAlive() -
setSnapshotMode
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. -
getSnapshotMode
-
setDatabaseHistory
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. -
getDatabaseHistory
-
setConnectTimeoutMs
public void setConnectTimeoutMs(int connectTimeoutMs) Maximum time to wait after trying to connect to the database before timing out, given in milliseconds. Defaults to 30 seconds (30,000 ms). -
getConnectTimeoutMs
public int getConnectTimeoutMs() -
setMaxQueueSize
public void setMaxQueueSize(int maxQueueSize) 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. -
getMaxQueueSize
public int getMaxQueueSize() -
setIncrementalSnapshotChunkSize
public void setIncrementalSnapshotChunkSize(int incrementalSnapshotChunkSize) The maximum size of chunk for incremental snapshotting -
getIncrementalSnapshotChunkSize
public int getIncrementalSnapshotChunkSize() -
setDatabaseHistoryKafkaTopic
The name of the topic for the database schema history -
getDatabaseHistoryKafkaTopic
-
setRetriableRestartConnectorWaitMs
public void setRetriableRestartConnectorWaitMs(long retriableRestartConnectorWaitMs) Time to wait before restarting connector after retriable exception occurs. Defaults to 10000ms. -
getRetriableRestartConnectorWaitMs
public long getRetriableRestartConnectorWaitMs() -
setSnapshotDelayMs
public void setSnapshotDelayMs(long snapshotDelayMs) A delay period before a snapshot will begin, given in milliseconds. Defaults to 0 ms. -
getSnapshotDelayMs
public long getSnapshotDelayMs() -
setDatabaseHistoryKafkaRecoveryAttempts
public void setDatabaseHistoryKafkaRecoveryAttempts(int databaseHistoryKafkaRecoveryAttempts) 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). -
getDatabaseHistoryKafkaRecoveryAttempts
public int getDatabaseHistoryKafkaRecoveryAttempts() -
setProvideTransactionMetadata
public void setProvideTransactionMetadata(boolean provideTransactionMetadata) Enables transaction metadata extraction together with event counting -
isProvideTransactionMetadata
public boolean isProvideTransactionMetadata() -
setTableWhitelist
The tables for which changes are to be captured (deprecated, use "table.include.list" instead) -
getTableWhitelist
-
setTombstonesOnDelete
public void setTombstonesOnDelete(boolean tombstonesOnDelete) 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. -
isTombstonesOnDelete
public boolean isTombstonesOnDelete() -
setDecimalHandlingMode
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. -
getDecimalHandlingMode
-
setBinaryHandlingMode
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 -
getBinaryHandlingMode
-
setIncludeSchemaComments
public void setIncludeSchemaComments(boolean includeSchemaComments) Whether the connector parse table and column's comment to metadata object.Note: Enable this option will bring the implications on memory usage. The number and size of ColumnImpl objects is what largely impacts how much memory is consumed by the Debezium connectors, and adding a String to each of them can potentially be quite heavy. The default is 'false'. -
isIncludeSchemaComments
public boolean isIncludeSchemaComments() -
setSnapshotNewTables
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. -
getSnapshotNewTables
-
setDatabaseHistorySkipUnparseableDdl
public void setDatabaseHistorySkipUnparseableDdl(boolean databaseHistorySkipUnparseableDdl) 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. -
isDatabaseHistorySkipUnparseableDdl
public boolean isDatabaseHistorySkipUnparseableDdl() -
setTableIgnoreBuiltin
public void setTableIgnoreBuiltin(boolean tableIgnoreBuiltin) Flag specifying whether built-in tables should be ignored. -
isTableIgnoreBuiltin
public boolean isTableIgnoreBuiltin() -
setSnapshotIncludeCollectionList
this setting must be set to specify a list of tables/collections whose snapshot must be taken on creating or restarting the connector. -
getSnapshotIncludeCollectionList
-
setDatabaseHistoryFileFilename
The path to the file that will be used to record the database history -
getDatabaseHistoryFileFilename
-
setBigintUnsignedHandlingMode
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. -
getBigintUnsignedHandlingMode
-
setDatabaseServerId
public void setDatabaseServerId(long databaseServerId) 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. -
getDatabaseServerId
public long getDatabaseServerId() -
setMaxQueueSizeInBytes
public void setMaxQueueSizeInBytes(long maxQueueSizeInBytes) Maximum size of the queue in bytes for change events read from the database log but not yet recorded or forwarded. Defaults to 0. Mean the feature is not enabled -
getMaxQueueSizeInBytes
public long getMaxQueueSizeInBytes() -
setTransactionTopic
The name of the transaction metadata topic. The placeholder ${database.server.name} can be used for referring to the connector's logical name; defaults to ${database.server.name}.transaction. -
getTransactionTopic
-
setTimePrecisionMode
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. -
getTimePrecisionMode
-
setEventDeserializationFailureHandlingMode
public void setEventDeserializationFailureHandlingMode(String eventDeserializationFailureHandlingMode) 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. -
getEventDeserializationFailureHandlingMode
-
setDatabaseServerName
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. -
getDatabaseServerName
-
setEventProcessingFailureHandlingMode
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. -
getEventProcessingFailureHandlingMode
-
setSnapshotMaxThreads
public void setSnapshotMaxThreads(int snapshotMaxThreads) The maximum number of threads used to perform the snapshot. Defaults to 1. -
getSnapshotMaxThreads
public int getSnapshotMaxThreads() -
setDatabasePort
public void setDatabasePort(int databasePort) Port of the database server. -
getDatabasePort
public int getDatabasePort() -
setDatabaseSslTruststore
The location of the trust store file for the server certificate verification. -
getDatabaseSslTruststore
-
setDatabaseSslMode
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. -
getDatabaseSslMode
-
setDatabaseSslKeystorePassword
The password for the key store file. This is optional and only needed if 'database.ssl.keystore' is configured. -
getDatabaseSslKeystorePassword
-
setColumnExcludeList
Regular expressions matching columns to exclude from change events -
getColumnExcludeList
-
setDatabaseHostname
Resolvable hostname or IP address of the database server. -
getDatabaseHostname
-
setSchemaNameAdjustmentMode
Specify how schema names should be adjusted for compatibility with the message converter used by the connector, including:'avro' replaces the characters that cannot be used in the Avro type name with underscore (default)'none' does not apply any adjustment -
getSchemaNameAdjustmentMode
-
setDatabaseServerIdOffset
public void setDatabaseServerIdOffset(long databaseServerIdOffset) 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. -
getDatabaseServerIdOffset
public long getDatabaseServerIdOffset() -
setConnectKeepAliveIntervalMs
public void setConnectKeepAliveIntervalMs(long connectKeepAliveIntervalMs) Interval for connection checking if keep alive thread is used, given in milliseconds Defaults to 1 minute (60,000 ms). -
getConnectKeepAliveIntervalMs
public long getConnectKeepAliveIntervalMs() -
setTableIncludeList
The tables for which changes are to be captured -
getTableIncludeList
-
setIncludeQuery
public void setIncludeQuery(boolean includeQuery) 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'. -
isIncludeQuery
public boolean isIncludeQuery() -
setDatabaseIncludeList
The databases for which changes are to be captured -
getDatabaseIncludeList
-
createConnectorConfiguration
protected io.debezium.config.Configuration createConnectorConfiguration()- Specified by:
createConnectorConfigurationin classorg.apache.camel.component.debezium.configuration.EmbeddedDebeziumConfiguration
-
configureConnectorClass
- Specified by:
configureConnectorClassin classorg.apache.camel.component.debezium.configuration.EmbeddedDebeziumConfiguration
-
validateConnectorConfiguration
protected org.apache.camel.component.debezium.configuration.ConfigurationValidation validateConnectorConfiguration()- Specified by:
validateConnectorConfigurationin classorg.apache.camel.component.debezium.configuration.EmbeddedDebeziumConfiguration
-
getConnectorDatabaseType
- Specified by:
getConnectorDatabaseTypein classorg.apache.camel.component.debezium.configuration.EmbeddedDebeziumConfiguration
-