conduktor.io ↗
🐬

Debezium MySQL Connector Configuration

All configuration properties for the Debezium MySQL connector across versions 2.4–3.5. Cells highlighted in green are additions, red are removals, yellow are default changes.

100 properties · 10 versions (2.4–3.5) · Compare all connectors →
Property Description 2.42.52.62.73.03.13.23.33.43.5
bigint.unsigned.handling.modeSpecify how BIGINT UNSIGNED columns should be represented in change events, including: 'precise' uses java.math.BigDecim..longlonglonglonglonglonglonglonglonglong
binary.handling.modeSpecify how binary (blob, binary, etc.) columns should be represented in change events, including: 'bytes' represents bi..bytesbytesbytesbytesbytesbytesbytesbytesbytesbytes
binlog.buffer.sizeThe size of a look-ahead buffer used by the binlog reader to decide whether the transaction in progress is going to be c..nullnullnullnullnullnullnullnullnullnull
column.exclude.listRegular expressions matching columns to exclude from change eventsnullnullnullnullnullnullnullnullnullnull
column.include.listRegular expressions matching columns to include in change eventsnullnullnullnullnullnullnullnullnullnull
column.propagate.source.typeA comma-separated list of regular expressions matching fully-qualified names of columns that adds the column’s original ..nullnullnullnullnullnullnullnullnullnull
connect.keep.aliveWhether a separate thread should be used to ensure the connection is kept alive.truetruetruetruetruetruetruetruetruetrue
connect.keep.alive.interval.msInterval for connection checking if keep alive thread is used, given in milliseconds Defaults to 1 minute (60,000 ms).nullnullnullnullnullnullnullnullnullnull
connect.timeout.msMaximum time to wait after trying to connect to the database before timing out, given in milliseconds. Defaults to 30 se..nullnullnull30000300003000030000300003000030000
convertersOptional list of custom converters that would be used instead of default ones. The converters are defined using '<conver..nullnullnullnullnullnullnullnullnullnull
custom.metric.tagsThe custom metric tags will accept key-value pairs to customize the MBean object name which should be appended the end o..nullnullnullnullnullnullnullnullnullnull
database.dbnameThe name of the database from which the connector should capture changesnullnullnullnullnullnullnullnullnullnull
database.hostnameResolvable hostname or IP address of the database server.nullnullnullnullnullnullnullnullnullnull
database.initial.statementsA semicolon separated list of SQL statements to be executed when a JDBC connection (not binlog reading connection) to th..nullnullnullnullnullnullnullnullnullnull
database.jdbc.driverJDBC Driver class name used to connect to the MySQL database server.nullnullnullnullnullnullnullnullnullnull
database.passwordPassword of the database user to be used when connecting to the database.nullnullnullnullnullnullnullnullnullnull
database.portPort of the database server.nullnullnullnullnullnullnullnullnullnull
database.protocolJDBC protocol to use with the driver.jdbc:mysqljdbc:mysqljdbc:mysqljdbc:mysqljdbc:mysqljdbc:mysqljdbc:mysqljdbc:mysqljdbc:mysqljdbc:mysql
database.server.idA numeric ID of this database client, which must be unique across all currently-running database processes in the cluste..nullnullnullnullnullnullnullnullnullnull
database.server.id.offsetOnly relevant if parallel snapshotting is configured. During parallel snapshotting, multiple (4) connections open to the..10000100001000010000100001000010000100001000010000
database.ssl.keystoreThe location of the key store file. This is optional and can be used for two-way authentication between the client and t..nullnullnullnullnullnullnullnullnullnull
database.ssl.keystore.passwordThe password for the key store file. This is optional and only needed if 'database.ssl.keystore' is configured.nullnullnullnullnullnullnullnullnullnull
database.ssl.modeWhether to use an encrypted connection to the database. Options include: 'disabled' to use an unencrypted connection; 'p..preferredpreferredpreferredpreferredpreferredpreferredpreferredpreferredpreferredpreferred
database.ssl.truststoreThe location of the trust store file for the server certificate verification.nullnullnullnullnullnullnullnullnullnull
database.ssl.truststore.passwordThe password for the trust store file. Used to check the integrity of the truststore, and unlock the truststore.nullnullnullnullnullnullnullnullnullnull
database.userName of the database user to be used when connecting to the database.nullnullnullnullnullnullnullnullnullnull
datatype.propagate.source.typeA comma-separated list of regular expressions matching the database-specific data type names that adds the data type's o..nullnullnullnullnullnullnullnullnullnull
decimal.handling.modeSpecify how DECIMAL and NUMERIC columns should be represented in change events, including: 'precise' (the default) uses ..preciseprecisepreciseprecisepreciseprecisepreciseprecisepreciseprecise
enable.time.adjusterThe database allows the user to insert year value as either 2-digit or 4-digit. In case of two digit the value is automa..truetruetruetruetruetruetruetruetruetrue
errors.max.retriesThe maximum number of retries on connection errors before failing (-1 = no limit, 0 = disabled, > 0 = num of retries).nullnullnullnullnullnullnullnullnullnull
event.deserialization.failure.handling.modeSpecify how failures during deserialization of binlog events (i.e. when encountering a corrupted event) should be handle..failfailfailfailfailfailfailfailfailfail
event.processing.failure.handling.modeSpecify how failures during processing of events (i.e. when encountering a corrupted event) should be handled, including..failfailfailfailfailfailfailfailfailfail
field.name.adjustment.modeSpecify how field names should be adjusted for compatibility with the message converter used by the connector, including..nonenonenonenonenonenonenonenonenonenone
gtid.source.excludesThe source UUIDs used to exclude GTID ranges when determine the starting position in the MySQL server's binlog.nullnullnullnullnullnullnullnullnullnull
gtid.source.filter.dml.eventsWhen set to true, only produce DML events for transactions that were written on the server with matching GTIDs defined b..truetruetruetruetruetruetruetruetruetrue
gtid.source.includesThe source UUIDs used to include GTID ranges when determine the starting position in the MySQL server's binlog.nullnullnullnullnullnullnullnullnullnull
include.queryWhether the connector should include the original SQL query that generated the change event. Note: This option requires ..falsefalsefalsefalsefalsefalsefalsefalsefalsefalse
include.schema.changesWhether the connector should publish changes in the database schema to a Kafka topic with the same name as the database ..truetruetruetruetruetruetruetruetruetrue
include.schema.commentsWhether the connector parse table and column's comment to metadata object. Note: Enable this option will bring the impli..falsefalsefalsefalsefalsefalsefalsefalsefalsefalse
inconsistent.schema.handling.modeSpecify how binlog events that belong to a table missing from internal schema representation (i.e. internal representati..failfailfailfailfailfailfailfailfailfail
incremental.snapshot.allow.schema.changesDetect schema change during an incremental snapshot and re-select a current chunk to avoid locking DDLs. Note that chang..falsefalsefalsefalsefalsefalsefalsefalsefalsefalse
incremental.snapshot.chunk.sizeThe maximum size of chunk (number of documents/rows) for incremental snapshotting1024102410241024102410241024102410241024
max.batch.sizeMaximum size of each batch of source records. Defaults to .nullnullnullnullnullnullnullnullnullnull
max.queue.sizeMaximum size of the queue for change events read from the database log but not yet recorded or forwarded. Defaults to , ..nullnullnullnullnullnullnullnullnullnull
max.queue.size.in.bytesMaximum size of the queue in bytes for change events read from the database log but not yet recorded or forwarded. Defau..nullnullnullnullnullnullnullnullnullnull
message.key.columnsA semicolon-separated list of expressions that match fully-qualified tables and column(s) to be used as message key. Eac..nullnullnullnullnullnullnullnullnullnull
min.row.count.to.stream.resultsThe number of rows a table must contain to stream results rather than pull all into memory during snapshots. Defaults to..nullnullnullnullnullnullnullnullnullnull
notification.enabled.channelsList of notification channels names that are enabled.nullnullnullnullnullnullnullnullnullnull
poll.interval.msTime to wait for new change events to appear after receiving no events, given in milliseconds. Defaults to 500 ms.nullnullnullnullnullnullnullnullnullnull
provide.transaction.metadataEnables transaction metadata extraction together with event countingfalsefalsefalsefalsefalsefalsefalsefalsefalsefalse
query.fetch.sizeThe maximum number of records that should be loaded into memory while streaming. A value of '0' uses the default JDBC fe..nullnullnullnullnullnullnullnullnullnull
read.onlySwitched connector to use alternative methods to deliver signals to Debezium instead of writing to signaling tablefalsefalsefalsefalsefalsefalsefalsefalsefalsefalse
retriable.restart.connector.wait.msTime to wait before restarting connector after retriable exception occurs. Defaults to ms.nullnullnullnullnullnullnullnullnullnull
schema.name.adjustment.modeSpecify how schema names should be adjusted for compatibility with the message converter used by the connector, includin..nonenonenonenonenonenonenonenonenonenone
signal.data.collectionThe name of the data collection that is used to send signals/commands to Debezium. For multi-partition mode connectors, ..nullnullnullnullnullnullnullnullnullnull
signal.enabled.channelsList of channels names that are enabled. Source channel is enabled by defaultsourcesourcesourcesourcesourcesourcesourcesourcesourcesource
signal.poll.interval.msInterval for looking for new signals in registered channels, given in milliseconds. Defaults to 5 seconds.5000500050005000500050005000500050005000
skip.messages.without.changeEnable to skip publishing messages when there is no change in included columns.This would essentially filter messages to..falsefalsefalsefalsefalsefalsefalsefalsefalsefalse
skipped.operationsThe comma-separated list of operations to skip during streaming, defined as: 'c' for inserts/create; 'u' for updates; 'd..tttttttttt
snapshot.delay.msA delay period before a snapshot will begin, given in milliseconds. Defaults to 0 ms.0000000000
snapshot.fetch.sizeThe maximum number of records that should be loaded into memory while performing a snapshot.nullnullnullnullnullnullnullnullnullnull
snapshot.include.collection.listThis setting must be set to specify a list of tables/collections whose snapshot must be taken on creating or restarting ..nullnullnullnullnullnullnullnullnullnull
snapshot.lock.timeout.msThe maximum number of millis to wait for table locks at the beginning of a snapshot. If locks cannot be acquired in this..nullnullnullnullnullnullnullnullnullnull
snapshot.locking.modeControls how long the connector holds onto the global read lock while it is performing a snapshot. The default is 'minim..minimalminimalminimalminimalminimalminimalminimalminimalminimalminimal
snapshot.max.threadsThe maximum number of threads used to perform the snapshot. Defaults to 1.1111111111
snapshot.modeThe criteria for running a snapshot upon startup of the connector. Select one of the following snapshot options: 'when_n..initialinitialinitialinitialinitialinitialinitialinitialinitialinitial
snapshot.new.tablesBETA FEATURE: On connector restart, the connector will check if there have been any new tables added to the configuratio..offoffoff
snapshot.select.statement.overridesThis property contains a comma-separated list of fully-qualified tables (DB_NAME.TABLE_NAME) or (SCHEMA_NAME.TABLE_NAME)..nullnullnullnullnullnullnullnullnullnull
snapshot.tables.order.by.row.countControls the order in which tables are processed in the initial snapshot. A `descending` value will order the tables by ..disableddisableddisableddisableddisableddisableddisableddisableddisableddisabled
sourceinfo.struct.makerThe name of the SourceInfoStructMaker class that returns SourceInfo schema and struct.nullnullnullnullnullnullnullnullnullnull
table.ignore.builtinFlag specifying whether built-in tables should be ignored.truetruetruetruetruetruetruetruetruetrue
time.precision.modeTime, date, and timestamps can be represented with different kinds of precisions, including: 'adaptive' (the default) ba..adaptiveadaptiveadaptiveadaptiveadaptiveadaptiveadaptiveadaptiveadaptiveadaptive
tombstones.on.deleteWhether delete operations should be represented by a delete event and a subsequent tombstone event (true) or only by a d..truetruetruetruetruetruetruetruetruetrue
topic.naming.strategyThe name of the TopicNamingStrategy class that should be used to determine the topic name for data change, schema change..nullnullnullnullnullnullnullnullnullnull
topic.prefixTopic prefix that identifies and provides a namespace for the particular database server/cluster is capturing changes. T..nullnullnullnullnullnullnullnullnullnull
unavailable.value.placeholderSpecify the constant that will be provided by Debezium to indicate that the original value is unavailable and not provid..nullnullnullnullnullnullnullnullnullnull
connector.adapterSpecifies the connection adapter to be usedmysqlmysql
incremental.snapshot.watermarking.strategySpecify the strategy used for watermarking during an incremental snapshot: 'insert_insert' both open and close signal is..INSERT_INSERTINSERT_INSERTINSERT_INSERTINSERT_INSERTINSERT_INSERTINSERT_INSERTINSERT_INSERTINSERT_INSERTINSERT_INSERT
post.processorsOptional list of post processors. The processors are defined using '<post.processor.prefix>.type' config option and conf..nullnullnullnullnullnullnullnullnull
event.converting.failure.handling.modeSpecify how failures during converting of event should be handled, including: 'fail' throw an exception that the column ..warnwarnwarnwarnwarnwarnwarnwarn
snapshot.locking.mode.custom.nameWhen 'snapshot.locking.mode' is set as custom, this setting must be set to specify a the name of the custom implementati..nullnullnullnullnullnullnullnull
snapshot.mode.configuration.based.snapshot.dataWhen 'snapshot.mode' is set as configuration_based, this setting permits to specify whenever the data should be snapshot..falsefalsefalsefalsefalsefalsefalsefalse
snapshot.mode.configuration.based.snapshot.on.data.errorWhen 'snapshot.mode' is set as configuration_based, this setting permits to specify whenever the data should be snapshot..falsefalsefalsefalsefalsefalsefalsefalse
snapshot.mode.configuration.based.snapshot.on.schema.errorWhen 'snapshot.mode' is set as configuration_based, this setting permits to specify whenever the schema should be snapsh..falsefalsefalsefalsefalsefalsefalsefalse
snapshot.mode.configuration.based.snapshot.schemaWhen 'snapshot.mode' is set as configuration_based, this setting permits to specify whenever the schema should be snapsh..falsefalsefalsefalsefalsefalsefalsefalse
snapshot.mode.configuration.based.start.streamWhen 'snapshot.mode' is set as configuration_based, this setting permits to specify whenever the stream should start or ..falsefalsefalsefalsefalsefalsefalsefalse
snapshot.mode.custom.nameWhen 'snapshot.mode' is set as custom, this setting must be set to specify a the name of the custom implementation provi..nullnullnullnullnullnullnullnull
snapshot.query.modeControls query used during the snapshotselect_allselect_allselect_allselect_allselect_allselect_allselect_allselect_all
snapshot.query.mode.custom.nameWhen 'snapshot.query.mode' is set as custom, this setting must be set to specify a the name of the custom implementation..nullnullnullnullnullnullnullnull
database.query.timeout.msTime to wait for a query to execute, given in milliseconds. Defaults to 600 seconds (600,000 ms); zero means there is no..600000600000600000600000600000600000600000
streaming.delay.msA delay period after the snapshot is completed and the streaming begins, given in milliseconds. Defaults to 0 ms.0000000
transaction.metadata.factoryClass to make transaction context & transaction struct/schemasnullnullnullnullnullnullnull
use.nongraceful.disconnectWhether to use `socket.setSoLinger(true, 0)` when BinaryLogClient keepalive thread triggers a disconnect for a stale con..falsefalsefalsefalsefalsefalsefalse
connection.validation.timeout.msThe maximum time in milliseconds to wait for connection validation to complete. Defaults to 60 seconds.nullnullnullnull
executor.shutdown.timeout.msThe maximum time in milliseconds to wait for task executor to shut down.nullnullnullnull
guardrail.collections.limit.actionSpecify the action to take when a guardrail collections limit is exceeded: 'warn' (the default) logs a warning message a..warnwarnwarn
guardrail.collections.maxThe maximum number of collections or tables that can be captured by the connector. When this limit is exceeded, the acti..000
binlog.net.read.timeoutThe number of seconds to wait for a read from the binlog connection to complete before the server times out. A value of ..0
binlog.net.write.timeoutThe number of seconds to wait for a write to the binlog connection to complete before the server times out. A value of 0..0
snapshot.max.threads.multiplierThe factor used to scale the number of snapshot chunks per table. The default behavior is to take 'row_count/snapshot.ma..1