Interface DebeziumMySqlEndpointBuilderFactory.DebeziumMySqlEndpointBuilder

  • All Superinterfaces:
    org.apache.camel.builder.EndpointConsumerBuilder, org.apache.camel.EndpointConsumerResolver
    Enclosing interface:
    DebeziumMySqlEndpointBuilderFactory

    public static interface DebeziumMySqlEndpointBuilderFactory.DebeziumMySqlEndpointBuilder
    extends org.apache.camel.builder.EndpointConsumerBuilder
    Builder for endpoint for the Debezium MySQL Connector component.
    • Method Detail

      • additionalProperties

        default DebeziumMySqlEndpointBuilderFactory.DebeziumMySqlEndpointBuilder additionalProperties​(String key,
                                                                                                      Object value)
        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. The option is a: java.util.Map<java.lang.String, java.lang.Object> type. The option is multivalued, and you can use the additionalProperties(String, Object) method to add a value (call the method multiple times to set more values). Group: common
      • additionalProperties

        default DebeziumMySqlEndpointBuilderFactory.DebeziumMySqlEndpointBuilder additionalProperties​(Map values)
        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. The option is a: java.util.Map<java.lang.String, java.lang.Object> type. The option is multivalued, and you can use the additionalProperties(String, Object) method to add a value (call the method multiple times to set more values). Group: common
      • bridgeErrorHandler

        default DebeziumMySqlEndpointBuilderFactory.DebeziumMySqlEndpointBuilder bridgeErrorHandler​(boolean bridgeErrorHandler)
        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. The option is a: boolean type. Default: false Group: consumer
      • bridgeErrorHandler

        default DebeziumMySqlEndpointBuilderFactory.DebeziumMySqlEndpointBuilder bridgeErrorHandler​(String bridgeErrorHandler)
        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. The option will be converted to a boolean type. Default: false Group: consumer
      • internalKeyConverter

        default DebeziumMySqlEndpointBuilderFactory.DebeziumMySqlEndpointBuilder internalKeyConverter​(String internalKeyConverter)
        The Converter class that should be used to serialize and deserialize key data for offsets. The default is JSON converter. The option is a: java.lang.String type. Default: org.apache.kafka.connect.json.JsonConverter Group: consumer
      • internalValueConverter

        default DebeziumMySqlEndpointBuilderFactory.DebeziumMySqlEndpointBuilder internalValueConverter​(String internalValueConverter)
        The Converter class that should be used to serialize and deserialize value data for offsets. The default is JSON converter. The option is a: java.lang.String type. Default: org.apache.kafka.connect.json.JsonConverter Group: consumer
      • offsetCommitPolicy

        default DebeziumMySqlEndpointBuilderFactory.DebeziumMySqlEndpointBuilder offsetCommitPolicy​(String offsetCommitPolicy)
        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. The option is a: java.lang.String type. Default: io.debezium.embedded.spi.OffsetCommitPolicy.PeriodicCommitOffsetPolicy Group: consumer
      • offsetCommitTimeoutMs

        default DebeziumMySqlEndpointBuilderFactory.DebeziumMySqlEndpointBuilder offsetCommitTimeoutMs​(long offsetCommitTimeoutMs)
        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. Default: 5s Group: consumer
      • offsetCommitTimeoutMs

        default DebeziumMySqlEndpointBuilderFactory.DebeziumMySqlEndpointBuilder offsetCommitTimeoutMs​(String offsetCommitTimeoutMs)
        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 will be converted to a long type. Default: 5s Group: consumer
      • offsetStoragePartitions

        default DebeziumMySqlEndpointBuilderFactory.DebeziumMySqlEndpointBuilder offsetStoragePartitions​(int offsetStoragePartitions)
        The number of partitions used when creating the offset storage topic. Required when offset.storage is set to the 'KafkaOffsetBackingStore'. The option is a: int type. Group: consumer
      • offsetStoragePartitions

        default DebeziumMySqlEndpointBuilderFactory.DebeziumMySqlEndpointBuilder offsetStoragePartitions​(String offsetStoragePartitions)
        The number of partitions used when creating the offset storage topic. Required when offset.storage is set to the 'KafkaOffsetBackingStore'. The option will be converted to a int type. Group: consumer
      • offsetStorageReplicationFactor

        default DebeziumMySqlEndpointBuilderFactory.DebeziumMySqlEndpointBuilder offsetStorageReplicationFactor​(int offsetStorageReplicationFactor)
        Replication factor used when creating the offset storage topic. Required when offset.storage is set to the KafkaOffsetBackingStore. The option is a: int type. Group: consumer
      • offsetStorageReplicationFactor

        default DebeziumMySqlEndpointBuilderFactory.DebeziumMySqlEndpointBuilder offsetStorageReplicationFactor​(String offsetStorageReplicationFactor)
        Replication factor used when creating the offset storage topic. Required when offset.storage is set to the KafkaOffsetBackingStore. The option will be converted to a int type. Group: consumer
      • bigintUnsignedHandlingMode

        default DebeziumMySqlEndpointBuilderFactory.DebeziumMySqlEndpointBuilder bigintUnsignedHandlingMode​(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. The option is a: java.lang.String type. Default: long Group: mysql
      • binaryHandlingMode

        default DebeziumMySqlEndpointBuilderFactory.DebeziumMySqlEndpointBuilder binaryHandlingMode​(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) string. The option is a: java.lang.String type. Default: bytes Group: mysql
      • binlogBufferSize

        default DebeziumMySqlEndpointBuilderFactory.DebeziumMySqlEndpointBuilder binlogBufferSize​(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). The option is a: int type. Default: 0 Group: mysql
      • binlogBufferSize

        default DebeziumMySqlEndpointBuilderFactory.DebeziumMySqlEndpointBuilder binlogBufferSize​(String 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). The option will be converted to a int type. Default: 0 Group: mysql
      • databaseHistory

        default DebeziumMySqlEndpointBuilderFactory.DebeziumMySqlEndpointBuilder databaseHistory​(String databaseHistory)
        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. The option is a: java.lang.String type. Default: io.debezium.relational.history.FileDatabaseHistory Group: mysql
      • databaseHistoryKafkaBootstrapServers

        default DebeziumMySqlEndpointBuilderFactory.DebeziumMySqlEndpointBuilder databaseHistoryKafkaBootstrapServers​(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. This should point to the same Kafka cluster used by the Kafka Connect process. The option is a: java.lang.String type. Group: mysql
      • databaseHistoryKafkaRecoveryAttempts

        default DebeziumMySqlEndpointBuilderFactory.DebeziumMySqlEndpointBuilder databaseHistoryKafkaRecoveryAttempts​(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). The option is a: int type. Default: 100 Group: mysql
      • databaseHistoryKafkaRecoveryAttempts

        default DebeziumMySqlEndpointBuilderFactory.DebeziumMySqlEndpointBuilder databaseHistoryKafkaRecoveryAttempts​(String 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). The option will be converted to a int type. Default: 100 Group: mysql
      • databaseHistoryKafkaRecoveryPollIntervalMs

        default DebeziumMySqlEndpointBuilderFactory.DebeziumMySqlEndpointBuilder databaseHistoryKafkaRecoveryPollIntervalMs​(int databaseHistoryKafkaRecoveryPollIntervalMs)
        The number of milliseconds to wait while polling for persisted data during recovery. The option is a: int type. Default: 100ms Group: mysql
      • databaseHistoryKafkaRecoveryPollIntervalMs

        default DebeziumMySqlEndpointBuilderFactory.DebeziumMySqlEndpointBuilder databaseHistoryKafkaRecoveryPollIntervalMs​(String databaseHistoryKafkaRecoveryPollIntervalMs)
        The number of milliseconds to wait while polling for persisted data during recovery. The option will be converted to a int type. Default: 100ms Group: mysql
      • databaseHistorySkipUnparseableDdl

        default DebeziumMySqlEndpointBuilderFactory.DebeziumMySqlEndpointBuilder databaseHistorySkipUnparseableDdl​(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. The option is a: boolean type. Default: false Group: mysql
      • databaseHistorySkipUnparseableDdl

        default DebeziumMySqlEndpointBuilderFactory.DebeziumMySqlEndpointBuilder databaseHistorySkipUnparseableDdl​(String 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. The option will be converted to a boolean type. Default: false Group: mysql
      • databaseHistoryStoreOnlyMonitoredTablesDdl

        default DebeziumMySqlEndpointBuilderFactory.DebeziumMySqlEndpointBuilder databaseHistoryStoreOnlyMonitoredTablesDdl​(boolean databaseHistoryStoreOnlyMonitoredTablesDdl)
        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. The option is a: boolean type. Default: false Group: mysql
      • databaseHistoryStoreOnlyMonitoredTablesDdl

        default DebeziumMySqlEndpointBuilderFactory.DebeziumMySqlEndpointBuilder databaseHistoryStoreOnlyMonitoredTablesDdl​(String databaseHistoryStoreOnlyMonitoredTablesDdl)
        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. The option will be converted to a boolean type. Default: false Group: mysql
      • databaseInitialStatements

        default DebeziumMySqlEndpointBuilderFactory.DebeziumMySqlEndpointBuilder databaseInitialStatements​(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. 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. The option is a: java.lang.String type. Group: mysql
      • databaseServerId

        default DebeziumMySqlEndpointBuilderFactory.DebeziumMySqlEndpointBuilder databaseServerId​(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. The option is a: long type. Group: mysql
      • databaseServerId

        default DebeziumMySqlEndpointBuilderFactory.DebeziumMySqlEndpointBuilder databaseServerId​(String 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. The option will be converted to a long type. Group: mysql
      • databaseServerIdOffset

        default DebeziumMySqlEndpointBuilderFactory.DebeziumMySqlEndpointBuilder databaseServerIdOffset​(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. The option is a: long type. Default: 10000 Group: mysql
      • databaseServerIdOffset

        default DebeziumMySqlEndpointBuilderFactory.DebeziumMySqlEndpointBuilder databaseServerIdOffset​(String 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. The option will be converted to a long type. Default: 10000 Group: mysql
      • databaseServerName

        default DebeziumMySqlEndpointBuilderFactory.DebeziumMySqlEndpointBuilder databaseServerName​(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. Each distinct installation should have a separate namespace and be monitored by at most one Debezium connector. The option is a: java.lang.String type. Required: true Group: mysql
      • databaseSslKeystorePassword

        default DebeziumMySqlEndpointBuilderFactory.DebeziumMySqlEndpointBuilder databaseSslKeystorePassword​(String databaseSslKeystorePassword)
        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). The option is a: java.lang.String type. Group: mysql
      • databaseSslMode

        default DebeziumMySqlEndpointBuilderFactory.DebeziumMySqlEndpointBuilder databaseSslMode​(String databaseSslMode)
        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. The option is a: java.lang.String type. Default: disabled Group: mysql
      • databaseSslTruststorePassword

        default DebeziumMySqlEndpointBuilderFactory.DebeziumMySqlEndpointBuilder databaseSslTruststorePassword​(String databaseSslTruststorePassword)
        Password to unlock the keystore file (store password) specified by 'ssl.trustore' configuration property or the 'javax.net.ssl.trustStore' system or JVM property. The option is a: java.lang.String type. Group: mysql
      • decimalHandlingMode

        default DebeziumMySqlEndpointBuilderFactory.DebeziumMySqlEndpointBuilder decimalHandlingMode​(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. The option is a: java.lang.String type. Default: precise Group: mysql
      • enableTimeAdjuster

        default DebeziumMySqlEndpointBuilderFactory.DebeziumMySqlEndpointBuilder enableTimeAdjuster​(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. The option is a: boolean type. Default: true Group: mysql
      • enableTimeAdjuster

        default DebeziumMySqlEndpointBuilderFactory.DebeziumMySqlEndpointBuilder enableTimeAdjuster​(String 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. The option will be converted to a boolean type. Default: true Group: mysql
      • eventDeserializationFailureHandlingMode

        default DebeziumMySqlEndpointBuilderFactory.DebeziumMySqlEndpointBuilder eventDeserializationFailureHandlingMode​(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. The option is a: java.lang.String type. Default: fail Group: mysql
      • eventProcessingFailureHandlingMode

        default DebeziumMySqlEndpointBuilderFactory.DebeziumMySqlEndpointBuilder eventProcessingFailureHandlingMode​(String eventProcessingFailureHandlingMode)
        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. The option is a: java.lang.String type. Default: fail Group: mysql
      • gtidNewChannelPosition

        default DebeziumMySqlEndpointBuilderFactory.DebeziumMySqlEndpointBuilder gtidNewChannelPosition​(String gtidNewChannelPosition)
        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. The option is a: java.lang.String type. Default: earliest Group: mysql
      • gtidSourceFilterDmlEvents

        default DebeziumMySqlEndpointBuilderFactory.DebeziumMySqlEndpointBuilder gtidSourceFilterDmlEvents​(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. The option is a: boolean type. Default: true Group: mysql
      • gtidSourceFilterDmlEvents

        default DebeziumMySqlEndpointBuilderFactory.DebeziumMySqlEndpointBuilder gtidSourceFilterDmlEvents​(String 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. The option will be converted to a boolean type. Default: true Group: mysql
      • heartbeatIntervalMs

        default DebeziumMySqlEndpointBuilderFactory.DebeziumMySqlEndpointBuilder heartbeatIntervalMs​(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. The option is a: int type. Default: 0ms Group: mysql
      • heartbeatIntervalMs

        default DebeziumMySqlEndpointBuilderFactory.DebeziumMySqlEndpointBuilder heartbeatIntervalMs​(String 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. The option will be converted to a int type. Default: 0ms Group: mysql
      • includeQuery

        default DebeziumMySqlEndpointBuilderFactory.DebeziumMySqlEndpointBuilder includeQuery​(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'. The option is a: boolean type. Default: false Group: mysql
      • includeQuery

        default DebeziumMySqlEndpointBuilderFactory.DebeziumMySqlEndpointBuilder includeQuery​(String 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'. The option will be converted to a boolean type. Default: false Group: mysql
      • includeSchemaChanges

        default DebeziumMySqlEndpointBuilderFactory.DebeziumMySqlEndpointBuilder includeSchemaChanges​(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. The option is a: boolean type. Default: true Group: mysql
      • includeSchemaChanges

        default DebeziumMySqlEndpointBuilderFactory.DebeziumMySqlEndpointBuilder includeSchemaChanges​(String 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. The option will be converted to a boolean type. Default: true Group: mysql
      • inconsistentSchemaHandlingMode

        default DebeziumMySqlEndpointBuilderFactory.DebeziumMySqlEndpointBuilder inconsistentSchemaHandlingMode​(String inconsistentSchemaHandlingMode)
        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. The option is a: java.lang.String type. Default: fail Group: mysql
      • maxQueueSize

        default DebeziumMySqlEndpointBuilderFactory.DebeziumMySqlEndpointBuilder maxQueueSize​(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. The option is a: int type. Default: 8192 Group: mysql
      • maxQueueSize

        default DebeziumMySqlEndpointBuilderFactory.DebeziumMySqlEndpointBuilder maxQueueSize​(String 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. The option will be converted to a int type. Default: 8192 Group: mysql
      • messageKeyColumns

        default DebeziumMySqlEndpointBuilderFactory.DebeziumMySqlEndpointBuilder messageKeyColumns​(String messageKeyColumns)
        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. The option is a: java.lang.String type. Group: mysql
      • skippedOperations

        default DebeziumMySqlEndpointBuilderFactory.DebeziumMySqlEndpointBuilder skippedOperations​(String skippedOperations)
        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. The option is a: java.lang.String type. Group: mysql
      • snapshotLockingMode

        default DebeziumMySqlEndpointBuilderFactory.DebeziumMySqlEndpointBuilder snapshotLockingMode​(String snapshotLockingMode)
        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. The option is a: java.lang.String type. Default: minimal Group: mysql
      • snapshotMode

        default DebeziumMySqlEndpointBuilderFactory.DebeziumMySqlEndpointBuilder snapshotMode​(String snapshotMode)
        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. The option is a: java.lang.String type. Default: initial Group: mysql
      • snapshotNewTables

        default DebeziumMySqlEndpointBuilderFactory.DebeziumMySqlEndpointBuilder snapshotNewTables​(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. 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. The option is a: java.lang.String type. Default: off Group: mysql
      • snapshotSelectStatementOverrides

        default DebeziumMySqlEndpointBuilderFactory.DebeziumMySqlEndpointBuilder snapshotSelectStatementOverrides​(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 . 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. The option is a: java.lang.String type. Group: mysql
      • tableBlacklist

        default DebeziumMySqlEndpointBuilderFactory.DebeziumMySqlEndpointBuilder tableBlacklist​(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). The option is a: java.lang.String type. Group: mysql
      • timePrecisionMode

        default DebeziumMySqlEndpointBuilderFactory.DebeziumMySqlEndpointBuilder timePrecisionMode​(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. The option is a: java.lang.String type. Default: adaptive_time_microseconds Group: mysql
      • tombstonesOnDelete

        default DebeziumMySqlEndpointBuilderFactory.DebeziumMySqlEndpointBuilder tombstonesOnDelete​(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. The option is a: boolean type. Default: false Group: mysql
      • tombstonesOnDelete

        default DebeziumMySqlEndpointBuilderFactory.DebeziumMySqlEndpointBuilder tombstonesOnDelete​(String 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. The option will be converted to a boolean type. Default: false Group: mysql