Camel Spring Boot

Debezium DB2 Connector

Capture changes from a DB2 database.

What’s inside

Please refer to the above links for usage and configuration details.

Maven coordinates

<dependency>
    <groupId>org.apache.camel.springboot</groupId>
    <artifactId>camel-debezium-db2-starter</artifactId>
</dependency>

Spring Boot Auto-Configuration

The starter supports 123 options, which are listed below.

Name Description Default Type

camel.component.debezium-db2.additional-properties

Additional properties for debezium components in case they can’t be set directly on the camel configurations (e.g: setting Kafka Connect properties needed by Debezium engine, for example setting KafkaOffsetBackingStore), the properties have to be prefixed with additionalProperties.. E.g: additionalProperties.transactional.id=12345&additionalProperties.schema.registry.url=http://localhost:8811/avro. This is a multi-value option with prefix: additionalProperties.

Object>

camel.component.debezium-db2.autowired-enabled

Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.

true

Boolean

camel.component.debezium-db2.bridge-error-handler

Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions (if possible) occurred while the Camel consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. Important: This is only possible if the 3rd party component allows Camel to be alerted if an exception was thrown. Some components handle this internally only, and therefore bridgeErrorHandler is not possible. In other situations we may improve the Camel component to hook into the 3rd party component and make this possible for future releases. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored.

false

Boolean

camel.component.debezium-db2.cdc-change-tables-schema

The name of the schema where CDC change tables are located; defaults to 'ASNCDC'

ASNCDC

String

camel.component.debezium-db2.cdc-control-schema

The name of the schema where CDC control structures are located; defaults to 'ASNCDC'

ASNCDC

String

camel.component.debezium-db2.column-exclude-list

Regular expressions matching columns to exclude from change events

String

camel.component.debezium-db2.column-include-list

Regular expressions matching columns to include in change events

String

camel.component.debezium-db2.column-propagate-source-type

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.

String

camel.component.debezium-db2.configuration

Allow pre-configured Configurations to be set. The option is a org.apache.camel.component.debezium.db2.configuration.Db2ConnectorEmbeddedDebeziumConfiguration type.

Db2ConnectorEmbeddedDebeziumConfiguration

camel.component.debezium-db2.connection-validation-timeout-ms

The maximum time in milliseconds to wait for connection validation to complete. Defaults to 60 seconds. The option is a long type.

60000

Long

camel.component.debezium-db2.converters

Optional list of custom converters that would be used instead of default ones. The converters are defined using '.type' config option and configured using options '.'

String

camel.component.debezium-db2.custom-metric-tags

A comma-separated list of key-value pairs that are appended to the MBean object name. Keys must be valid JMX ObjectName property keys. For example: k1=v1,k2=v2

String

camel.component.debezium-db2.custom-sanitize-pattern

Regular expression identifying configuration keys whose values should be masked. When set, this custom pattern replaces Debeziums default password masking pattern.

\.jaas.config$|.*basic.auth.user.info|.*registry.auth.client-secret|.*credentials.json$|.*connectionstring$|.*connection.string$

String

camel.component.debezium-db2.database-dbname

The name of the database from which the connector should capture changes

String

camel.component.debezium-db2.database-exclude-list

A comma-separated list of regular expressions that match database names to be excluded from monitoring

String

camel.component.debezium-db2.database-hostname

Resolvable hostname or IP address of the database server.

String

camel.component.debezium-db2.database-include-list

The databases for which changes are to be captured

String

camel.component.debezium-db2.database-password

Password of the database user to be used when connecting to the database.

String

camel.component.debezium-db2.database-port

Port of the database server.

50000

Integer

camel.component.debezium-db2.database-query-timeout-ms

Time to wait for a query to execute, given in milliseconds. Defaults to 600 seconds (600,000 ms); zero means there is no limit. The option is a int type.

600000

Integer

camel.component.debezium-db2.database-user

Name of the database user to be used when connecting to the database.

String

camel.component.debezium-db2.datatype-propagate-source-type

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.

String

camel.component.debezium-db2.db2-platform

Informs connector which Db2 implementation platform it is connected to. The default is 'LUW', which means Windows, UNIX, Linux. Using a value of 'Z' ensures that the Db2 for z/OS specific SQL statements are used.

LUW

String

camel.component.debezium-db2.decimal-handling-mode

Specify how DECIMAL and NUMERIC columns should be represented in change events, including: 'precise' (the default) uses java.math.BigDecimal to represent values, which are encoded in the change events using a binary representation and Kafka Connect’s 'org.apache.kafka.connect.data.Decimal' type; 'string' uses string to represent values; 'double' represents values using Java’s 'double', which may not offer the precision but will be far easier to use in consumers.

precise

String

camel.component.debezium-db2.enabled

Whether to enable auto configuration of the debezium-db2 component. This is enabled by default.

Boolean

camel.component.debezium-db2.errors-max-retries

The maximum number of retries on connection errors before failing (-1 = no limit, 0 = disabled, 0 = num of retries).

-1

Integer

camel.component.debezium-db2.event-converting-failure-handling-mode

Specify how failures during converting of event should be handled, including: 'fail' throw an exception that the column of event conversion is failed with unmatched schema type, causing the connector to be stopped. it could need schema recovery to covert successfully; 'warn' (the default) the value of column of event that conversion failed will be null and be logged with warn level; 'skip' the value of column of event that conversion failed will be null and be logged with debug level.

warn

String

camel.component.debezium-db2.event-processing-failure-handling-mode

Specify how failures during processing of events (i.e. when encountering a corrupted event) should be handled, including: 'fail' (the default) an exception indicating the problematic event and its position is raised, causing the connector to be stopped; 'warn' the problematic event and its position will be logged and the event will be skipped; 'ignore' the problematic event will be skipped.

fail

String

camel.component.debezium-db2.executor-shutdown-timeout-ms

The maximum time in milliseconds to wait for task executor to shut down. The option is a long type.

4000

Long

camel.component.debezium-db2.extended-headers-enabled

Enable/Disable Debezium context headers that provides essential metadata for tracking and identifying the source of CDC events in downstream processing systems.

true

Boolean

camel.component.debezium-db2.field-name-adjustment-mode

Specify how field 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; 'avro_unicode' replaces the underscore or characters that cannot be used in the Avro type name with corresponding unicode like _uxxxx. Note: _ is an escape sequence like backslash in Java;'none' does not apply any adjustment (default)

none

String

camel.component.debezium-db2.guardrail-collections-limit-action

Specify the action to take when a guardrail collections limit is exceeded: 'warn' (the default) logs a warning message and continues processing; 'fail' stops the connector with an error.

warn

String

camel.component.debezium-db2.guardrail-collections-max

The maximum number of collections or tables that can be captured by the connector. When this limit is exceeded, the action specified by 'guardrail.collections.limit.action' will be taken. Set to 0 to disable this guardrail.

0

Integer

camel.component.debezium-db2.heartbeat-interval-ms

Length of an interval in milli-seconds in in which the connector periodically sends heartbeat messages to a heartbeat topic. Use 0 to disable heartbeat messages. Disabled by default. The option is a int type.

0

Integer

camel.component.debezium-db2.heartbeat-topics-prefix

The prefix that is used to name heartbeat topics.Defaults to __debezium-heartbeat.

__debezium-heartbeat

String

camel.component.debezium-db2.include-schema-changes

Whether the connector should publish changes in the database schema to a Kafka topic with the same name as the database server ID. Each schema change will be recorded using a key that contains the database name and whose value include logical description of the new schema and optionally the DDL statement(s). The default is 'true'. This is independent of how the connector internally records database schema history.

true

Boolean

camel.component.debezium-db2.incremental-snapshot-chunk-size

The maximum size of chunk (number of documents/rows) for incremental snapshotting

1024

Integer

camel.component.debezium-db2.incremental-snapshot-watermarking-strategy

Specify the strategy used for watermarking during an incremental snapshot: 'insert_insert' both open and close signal is written into signal data collection (default); 'insert_delete' only open signal is written on signal data collection, the close will delete the relative open signal;

INSERT_INSERT

String

camel.component.debezium-db2.internal-key-converter

The Converter class that should be used to serialize and deserialize key data for offsets. The default is JSON converter.

org.apache.kafka.connect.json.JsonConverter

String

camel.component.debezium-db2.internal-value-converter

The Converter class that should be used to serialize and deserialize value data for offsets. The default is JSON converter.

org.apache.kafka.connect.json.JsonConverter

String

camel.component.debezium-db2.legacy-snapshot-max-threads

When enabled, uses the legacy table-per-thread parallel snapshot algorithm. When set to false (the default), tables are split into chunks and processed across all snapshot threads, allowing for higher concurrency for snapshots.

false

Boolean

camel.component.debezium-db2.max-batch-size

Maximum size of each batch of source records. Defaults to 2048.

2048

Integer

camel.component.debezium-db2.max-queue-size

Maximum size of the queue for change events read from the database log but not yet recorded or forwarded. Defaults to 8192, and should always be larger than the maximum batch size.

8192

Integer

camel.component.debezium-db2.max-queue-size-in-bytes

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

0

Long

camel.component.debezium-db2.memory-management-schemas-class

The fully-qualified class name of the storage implementation for schema metadata. The class must implement io.debezium.relational.TableMappingStorage. Defaults to io.debezium.relational.ConcurrentMapTableMappingStorage for in-memory storage.

io.debezium.relational.ConcurrentMapTableMappingStorage

String

camel.component.debezium-db2.memory-management-tables-class

The fully-qualified class name of the storage implementation for table metadata. The class must implement io.debezium.relational.TableMappingStorage. Defaults to io.debezium.relational.ConcurrentMapTableMappingStorage for in-memory storage.

io.debezium.relational.ConcurrentMapTableMappingStorage

String

camel.component.debezium-db2.message-key-columns

A semicolon-separated list of expressions that match fully-qualified tables and column(s) to be used as message key. Each expression must match the pattern ':', where the table names could be defined as (DB_NAME.TABLE_NAME) or (SCHEMA_NAME.TABLE_NAME), depending on the specific connector, and the key columns are a comma-separated list of columns representing the custom key. For any table without an explicit key configuration the table’s primary key column(s) will be used as message key. Example: dbserver1.inventory.orderlines:orderId,orderLineId;dbserver1.inventory.orders:id

String

camel.component.debezium-db2.notification-enabled-channels

List of notification channels names that are enabled.

String

camel.component.debezium-db2.notification-http-allow-private-networks

When true, the SSRF guard permits notification URLs that resolve to loopback, site-local or link-local addresses (e.g. an in-cluster Service). Defaults to false so only public addresses are allowed.

false

Boolean

camel.component.debezium-db2.notification-http-retries

Number of retries after the first failed HTTP notification delivery attempt. Terminal notifications (COMPLETED/ABORTED/SKIPPED) are always retried at least 3 times.

2

Integer

camel.component.debezium-db2.notification-http-timeout-ms

Connect and read timeout, in milliseconds, for HTTP notification delivery. The option is a int type.

5000

Integer

camel.component.debezium-db2.notification-http-url

The URL to which notifications are POSTed as JSON. Required when 'http' is in the list of enabled channels.

String

camel.component.debezium-db2.notification-sink-topic-name

The name of the topic for the notifications. This is required in case 'sink' is in the list of enabled channels

String

camel.component.debezium-db2.offset-commit-policy

The name of the Java class of the commit policy. It defines when offsets commit has to be triggered based on the number of events processed and the time elapsed since the last commit. This class must implement the interface 'OffsetCommitPolicy'. The default is a periodic commit policy based upon time intervals.

String

camel.component.debezium-db2.offset-commit-timeout-ms

Maximum number of milliseconds to wait for records to flush and partition offset data to be committed to offset storage before cancelling the process and restoring the offset data to be committed in a future attempt. The default is 5 seconds. The option is a long type.

5000

Long

camel.component.debezium-db2.offset-flush-interval-ms

Interval at which to try committing offsets. The default is 1 minute. The option is a long type.

60000

Long

camel.component.debezium-db2.offset-storage

The name of the Java class that is responsible for persistence of connector offsets.

org.apache.kafka.connect.storage.FileOffsetBackingStore

String

camel.component.debezium-db2.offset-storage-file-name

Path to file where offsets are to be stored. Required when offset.storage is set to the FileOffsetBackingStore.

String

camel.component.debezium-db2.offset-storage-partitions

The number of partitions used when creating the offset storage topic. Required when offset.storage is set to the 'KafkaOffsetBackingStore'.

Integer

camel.component.debezium-db2.offset-storage-replication-factor

Replication factor used when creating the offset storage topic. Required when offset.storage is set to the KafkaOffsetBackingStore

Integer

camel.component.debezium-db2.offset-storage-topic

The name of the Kafka topic where offsets are to be stored. Required when offset.storage is set to the KafkaOffsetBackingStore.

String

camel.component.debezium-db2.openlineage-integration-config-file-path

Path to OpenLineage file configuration. See https://openlineage.io/docs/client/java/configuration

./openlineage.yml

String

camel.component.debezium-db2.openlineage-integration-dataset-kafka-bootstrap-servers

The Kafka bootstrap server address used as input/output namespace/

String

camel.component.debezium-db2.openlineage-integration-enabled

Enable Debezium to emit data lineage metadata through OpenLineage API

false

Boolean

camel.component.debezium-db2.openlineage-integration-job-description

The job’s description emitted by Debezium

Debezium change data capture job

String

camel.component.debezium-db2.openlineage-integration-job-namespace

The job’s namespace emitted by Debezium

String

camel.component.debezium-db2.openlineage-integration-job-owners

The job’s owners emitted by Debezium. A comma-separated list of key-value pairs.For example: k1=v1,k2=v2

String

camel.component.debezium-db2.openlineage-integration-job-tags

The job’s tags emitted by Debezium. A comma-separated list of key-value pairs.For example: k1=v1,k2=v2

String

camel.component.debezium-db2.poll-interval-ms

Time to wait for new change events to appear after receiving no events, given in milliseconds. Defaults to 500 ms. Values will be capped at 5000 ms. The option is a long type.

500

Long

camel.component.debezium-db2.post-processors

Optional list of post processors. The processors are defined using '.type' config option and configured using options ''

String

camel.component.debezium-db2.provide-transaction-metadata

Enables transaction metadata extraction together with event counting

false

Boolean

camel.component.debezium-db2.query-fetch-size

The maximum number of records that should be loaded into memory while streaming. A value of '0' uses the default JDBC fetch size. The default value is '10000'.

10000

Integer

camel.component.debezium-db2.retriable-restart-connector-wait-ms

Time to wait before restarting connector after retriable exception occurs. Defaults to 10000ms. The option is a long type.

10000

Long

camel.component.debezium-db2.schema-history-internal

The name of the SchemaHistory class that should be used to store and recover database schema changes. The configuration properties for the history are prefixed with the 'schema.history.internal.' string.

io.debezium.storage.kafka.history.KafkaSchemaHistory

String

camel.component.debezium-db2.schema-history-internal-file-filename

The path to the file that will be used to record the database schema history

String

camel.component.debezium-db2.schema-history-internal-memory-optimization

Controls how Debezium deduplicates identical schema objects (tables, columns, attributes) in memory using an interner.

off

String

camel.component.debezium-db2.schema-history-internal-skip-unparseable-ddl

Controls the action Debezium will take when it meets a DDL statement in binlog, that it cannot parse.By default the connector will stop operating but by changing the setting it can ignore the statements which it cannot parse. If skipping is enabled then Debezium can miss metadata changes.

false

Boolean

camel.component.debezium-db2.schema-history-internal-store-only-captured-databases-ddl

Controls what DDL will Debezium store in database schema history. By default (false) Debezium will store all incoming DDL statements. If set to true, then only DDL that manipulates a table from captured schema/database will be stored.

false

Boolean

camel.component.debezium-db2.schema-history-internal-store-only-captured-tables-ddl

Controls what DDL will Debezium store in database schema 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.

false

Boolean

camel.component.debezium-db2.schema-name-adjustment-mode

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; 'avro_unicode' replaces the underscore or characters that cannot be used in the Avro type name with corresponding unicode like _uxxxx. Note: _ is an escape sequence like backslash in Java;'none' does not apply any adjustment (default)

none

String

camel.component.debezium-db2.signal-data-collection

The name of the data collection that is used to send signals/commands to Debezium. For multi-partition mode connectors, multiple signal data collections can be specified as a comma-separated list. Signaling is disabled when not set.

String

camel.component.debezium-db2.signal-emit-failure-backoff-ms

Duration to sleep for after encountering an error emitting a window event, given in milliseconds. Defaults to 10 seconds. The option is a long type.

10000

Long

camel.component.debezium-db2.signal-emit-failure-max-retries

The maximum number of retries after encountering an error emitting a window event (-1 = no limit, 0 = disabled, 0 = num of retries). Defaults to 0.

0

Integer

camel.component.debezium-db2.signal-enabled-channels

List of channels names that are enabled. Source channel is enabled by default

source

String

camel.component.debezium-db2.signal-poll-interval-ms

Interval for looking for new signals in registered channels, given in milliseconds. Defaults to 5 seconds. The option is a long type.

5000

Long

camel.component.debezium-db2.skip-messages-without-change

Enable to skip publishing messages when there is no change in included columns.This would essentially filter messages to be sent when there is no change in columns included as per column.include.list/column.exclude.list.For Postgres - this would require REPLICA IDENTITY of table to be FULL.

false

Boolean

camel.component.debezium-db2.skipped-operations

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, only truncate operations will be skipped.

t

String

camel.component.debezium-db2.snapshot-delay-ms

A delay period before a snapshot will begin, given in milliseconds. Defaults to 0 ms. The option is a long type.

0

Long

camel.component.debezium-db2.snapshot-fetch-size

The maximum number of records that should be loaded into memory while performing a snapshot.

Integer

camel.component.debezium-db2.snapshot-include-collection-list

This setting must be set to specify a list of tables/collections whose snapshot must be taken on creating or restarting the connector.

String

camel.component.debezium-db2.snapshot-isolation-mode

Controls which transaction isolation level is used and how long the connector locks the monitored tables. The default is 'repeatable_read', which means that repeatable read isolation level is used. In addition, exclusive locks are taken only during schema snapshot. Using a value of 'exclusive' ensures that the connector holds the exclusive lock (and thus prevents any reads and updates) for all monitored tables during the entire snapshot duration. In 'read_committed' mode no table locks or any long-lasting* row-level locks are acquired, but connector does not guarantee snapshot consistency.In 'read_uncommitted' mode neither table nor row-level locks are acquired, but connector does not guarantee snapshot consistency.

repeatable_read

String

camel.component.debezium-db2.snapshot-lock-timeout-ms

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. The option is a long type.

10000

Long

camel.component.debezium-db2.snapshot-locking-mode

Controls how the connector holds locks on tables while performing the schema snapshot when snapshot.isolation.mode is REPEATABLE_READ or EXCLUSIVE. The 'exclusive' which means the connector will hold a table lock for exclusive table access 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 is done using a flashback query that requires no locks. However, in some cases it may be desirable to avoid locks entirely which can be done by specifying 'none'. This mode is only safe to use if no schema changes are happening while the snapshot is taken.

exclusive

String

camel.component.debezium-db2.snapshot-max-threads-multiplier

The factor used to scale the number of snapshot chunks per table. The default behavior is to take 'row_count/snapshot.max.threads' to compute the number of rows per chunks. This may not be ideal for larger tables, and using the multiplier, the formula is adjusted to increase the number of chunks by using 'row_count/(snapshot.max.threads * snapshot.max.threads.multiplier).

1

Integer

camel.component.debezium-db2.snapshot-mode

The criteria for running a snapshot upon startup of the connector. Options include: 'initial' (the default) to specify the connector should run a snapshot only when no offsets are available for the logical server name; 'schema_only' to specify the connector should run a snapshot of the schema when no offsets are available for the logical server name.

initial

String

camel.component.debezium-db2.snapshot-mode-configuration-based-snapshot-data

When 'snapshot.mode' is set as configuration_based, this setting permits to specify whenever the data should be snapshotted or not.

false

Boolean

camel.component.debezium-db2.snapshot-mode-configuration-based-snapshot-on-data-error

When 'snapshot.mode' is set as configuration_based, this setting permits to specify whenever the data should be snapshotted or not in case of error.

false

Boolean

camel.component.debezium-db2.snapshot-mode-configuration-based-snapshot-on-schema-error

When 'snapshot.mode' is set as configuration_based, this setting permits to specify whenever the schema should be snapshotted or not in case of error.

false

Boolean

camel.component.debezium-db2.snapshot-mode-configuration-based-snapshot-schema

When 'snapshot.mode' is set as configuration_based, this setting permits to specify whenever the schema should be snapshotted or not.

false

Boolean

camel.component.debezium-db2.snapshot-mode-configuration-based-start-stream

When 'snapshot.mode' is set as configuration_based, this setting permits to specify whenever the stream should start or not after snapshot.

false

Boolean

camel.component.debezium-db2.snapshot-mode-custom-name

When 'snapshot.mode' is set as custom, this setting must be set to specify a the name of the custom implementation provided in the 'name()' method. The implementations must implement the 'Snapshotter' interface and is called on each app boot to determine whether to do a snapshot.

String

camel.component.debezium-db2.snapshot-select-statement-overrides

This property contains a comma-separated list of fully-qualified tables (DB_NAME.TABLE_NAME) or (SCHEMA_NAME.TABLE_NAME), depending on the specific connectors. Select statements for the individual tables are specified in further configuration properties, one for each table, identified by the id 'snapshot.select.statement.overrides.[DB_NAME].[TABLE_NAME]' or 'snapshot.select.statement.overrides.[SCHEMA_NAME].[TABLE_NAME]', respectively. The value of those properties is the select statement to use when retrieving data from the specific table during snapshotting. A possible use case for large append-only tables is setting a specific point where to start (resume) snapshotting, in case a previous snapshotting was interrupted.

String

camel.component.debezium-db2.snapshot-tables-order-by-row-count

Controls the order in which tables are processed in the initial snapshot. A descending value will order the tables by row count descending. A ascending value will order the tables by row count ascending. A value of disabled (the default) will disable ordering by row count.

disabled

String

camel.component.debezium-db2.sourceinfo-struct-maker

The name of the SourceInfoStructMaker class that returns SourceInfo schema and struct.

io.debezium.connector.db2.Db2SourceInfoStructMaker

String

camel.component.debezium-db2.statistics-metrics-enabled

Enable to collect various kind of statistics, like latencies in record processing, and derived data like quantiles. By default collecting statistics is enabled.

true

Boolean

camel.component.debezium-db2.streaming-delay-ms

A delay period after the snapshot is completed and the streaming begins, given in milliseconds. Defaults to 0 ms. The option is a long type.

0

Long

camel.component.debezium-db2.streaming-query-timespan-seconds

The maximum number of seconds for a streaming query to include that query’s result set, starting from the earliest row in this query. Used to limit the size of queries when the change table is large to avoid excessive resource usage. If 0, no timespan limit will apply.

0

Integer

camel.component.debezium-db2.table-exclude-list

A comma-separated list of regular expressions that match the fully-qualified names of tables to be excluded from monitoring

String

camel.component.debezium-db2.table-ignore-builtin

Flag specifying whether built-in tables should be ignored.

true

Boolean

camel.component.debezium-db2.table-include-list

The tables for which changes are to be captured

String

camel.component.debezium-db2.time-precision-mode

Time, date, and timestamps can be represented with different kinds of precisions, including: 'adaptive' (the default) bases the precision of time, date, and timestamp values on the database column’s precision; 'adaptive_time_microseconds' like 'adaptive' mode, 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; 'isostring' represents time, date, and timestamp values as ISO-8601 formatted strings at the UTC time zone; 'structured' represents time, date, timestamp, and datetime values as Kafka Connect structs with separate calendar and clock components; 'microseconds' always represents time, date, and timestamp values using microsecond precision; 'nanoseconds' always represents time, date, and timestamp values using nanosecond precision.

adaptive

String

camel.component.debezium-db2.tombstones-on-delete

Whether delete operations should be represented by a delete event and a subsequent tombstone event (true) or only by a delete event (false). Emitting the tombstone event (the default behavior) allows Kafka to completely delete all events pertaining to the given key once the source record got deleted.

false

Boolean

camel.component.debezium-db2.topic-naming-strategy

The name of the TopicNamingStrategy class that should be used to determine the topic name for data change, schema change, transaction, heartbeat event etc.

io.debezium.schema.SchemaTopicNamingStrategy

String

camel.component.debezium-db2.topic-prefix

Topic prefix that identifies and provides a namespace for the particular database server/cluster is capturing changes. The topic prefix should be unique across all other connectors, since it is used as a prefix for all Kafka topic names that receive events emitted by this connector. Only alphanumeric characters, hyphens, dots and underscores must be accepted.

String

camel.component.debezium-db2.transaction-metadata-factory

Class to make transaction context & transaction struct/schemas

io.debezium.pipeline.txmetadata.DefaultTransactionMetadataFactory

String

camel.component.debezium-db2.update-capture-table-prune-apply-qual

The apply_qual name that represents the apply agent (this instance) to the subscription set.

String

camel.component.debezium-db2.update-capture-table-prune-ind

A switch to control if the connector instance is responsible for updating the prune table (usually done by IBM Apply agent) which will cause the IBM Capture agent to prune read data from the change tables. default false.

false

Boolean

camel.component.debezium-db2.update-capture-table-prune-lsn-decrement

An switch to decrement the prune lsn/syncpoint by one to avoid allowing the last lsn processed to get pruned to avoid the risk of an unnecessary snapshot due to the last processed lsn not being present in the change table.

true

Boolean

camel.component.debezium-db2.update-capture-table-prune-min-interval-ms

The minimum number of milliseconds between the connector instance’s update of the prune point for the subscription set. Default is 10000 (10 seconds). The option is a int type.

10000

Integer

camel.component.debezium-db2.update-capture-table-prune-procedure-override-name

The name of a prepared statement in the database that will be used instead of direct sql to allow for DBA control of the update code where needed.

String

camel.component.debezium-db2.update-capture-table-prune-set-name

If set to update the prune table, this will identify the prune set name that should be used when updating the table for this instance.

String

camel.component.debezium-db2.update-capture-table-prune-target-server

The target_server name that represents the apply agent’s target (where the data is going) for the subscription set.

String

camel.component.debezium-db2.z-stop-lsn-ignore

If true, causes the connector to ignore the stop LSN value from the IBMSNAP_REGISTER.CD_OLD_SYNCHPOINT column when polling. Apply this if events are getting dropped due to the stop LSN being smaller than the current range of LSNs. Only applies to z/OS platform.

false

Boolean