Debezium PostgresSQL Connector

camel.component.debezium-postgres.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-postgres.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.

Boolean

camel.component.debezium-postgres.binary-handling-mode

Specify how binary (blob, binary, etc.) columns should be represented in change events, including: 'bytes' represents binary data as byte array (default); 'base64' represents binary data as base64-encoded string; 'base64-url-safe' represents binary data as base64-url-safe-encoded string; 'hex' represents binary data as hex-encoded (base16) string

String

camel.component.debezium-postgres.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.

Boolean

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

Regular expressions matching columns to exclude from change events

String

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

Regular expressions matching columns to include in change events

String

camel.component.debezium-postgres.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-postgres.configuration

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

PostgresConnectorEmbeddedDebeziumConfiguration

camel.component.debezium-postgres.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.

Long

camel.component.debezium-postgres.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-postgres.custom-metric-tags

The custom metric tags will accept key-value pairs to customize the MBean object name which should be appended the end of regular name, each key would represent a tag for the MBean object name, and the corresponding value would be the value of that tag the key is. For example: k1=v1,k2=v2

String

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

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

.*basic.auth.user.info

.*registry.auth.client-secret

.*credentials.json$

camel.component.debezium-postgres.database-dbname

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

camel.component.debezium-postgres.database-hostname

Resolvable hostname or IP address of the database server.

camel.component.debezium-postgres.database-initial-statements

A semicolon separated list of SQL statements to be executed when a JDBC 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.

camel.component.debezium-postgres.database-password

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

camel.component.debezium-postgres.database-port

Port of the database server.

5432

camel.component.debezium-postgres.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

camel.component.debezium-postgres.database-sslcert

File containing the SSL Certificate for the client. See the Postgres SSL docs for further information

camel.component.debezium-postgres.database-sslfactory

A name of class to that creates SSL Sockets. Use org.postgresql.ssl.NonValidatingFactory to disable SSL validation in development environments

camel.component.debezium-postgres.database-sslkey

File containing the SSL private key for the client. See the Postgres SSL docs for further information

camel.component.debezium-postgres.database-sslmode

Whether to use an encrypted connection to Postgres. Options include: 'disable' (the default) to use an unencrypted connection; 'allow' to try and use an unencrypted connection first and, failing that, a secure (encrypted) connection; 'prefer' (the default) to try and use a secure (encrypted) connection first and, failing that, an unencrypted connection; 'require' 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-full' like 'verify-ca' but additionally verify that the server certificate matches the host to which the connection is attempted.

prefer

camel.component.debezium-postgres.database-sslpassword

Password to access the client private key from the file specified by 'database.sslkey'. See the Postgres SSL docs for further information

camel.component.debezium-postgres.database-sslrootcert

File containing the root certificate(s) against which the server is validated. See the Postgres JDBC SSL docs for further information

camel.component.debezium-postgres.database-tcpkeepalive

Enable or disable TCP keep-alive probe to avoid dropping TCP connection

true

camel.component.debezium-postgres.database-user

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

camel.component.debezium-postgres.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.

camel.component.debezium-postgres.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

camel.component.debezium-postgres.enabled

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

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

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

-1

camel.component.debezium-postgres.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

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

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

4000

camel.component.debezium-postgres.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

camel.component.debezium-postgres.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

camel.component.debezium-postgres.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

camel.component.debezium-postgres.heartbeat-action-query

The query executed with every heartbeat.

camel.component.debezium-postgres.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

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

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

__debezium-heartbeat

camel.component.debezium-postgres.hstore-handling-mode

Specify how HSTORE columns should be represented in change events, including: 'json' represents values as string-ified JSON (default); 'map' represents values as a key/value map

json

camel.component.debezium-postgres.include-schema-comments

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'.

false

camel.component.debezium-postgres.include-unknown-datatypes

Specify whether the fields of data type not supported by Debezium should be processed: 'false' (the default) omits the fields; 'true' converts the field into an implementation dependent binary representation.

false

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

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

1024

camel.component.debezium-postgres.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

camel.component.debezium-postgres.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

camel.component.debezium-postgres.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

camel.component.debezium-postgres.interval-handling-mode

Specify how INTERVAL columns should be represented in change events, including: 'string' represents values as an exact ISO formatted string; 'numeric' (default) represents values using the inexact conversion into microseconds

numeric

camel.component.debezium-postgres.lsn-flush-mode

Determines the LSN flushing strategy. Options include: 'connector' (default) for Debezium managed LSN flushing (replaces deprecated flush.lsn.source=true); 'manual' for externally managed LSN flushing (replaces deprecated flush.lsn.source=false); 'connector_and_driver' for Debezium managed LSN flushing with the pgjdbc driver flushing unmonitored LSNsusing server keepalive LSN, which prevents WAL growth on low-activity databases.

camel.component.debezium-postgres.lsn-flush-timeout-action

Action to take when an LSN flush timeout occurs. Options include: 'fail' (default) to fail the connector; 'warn' to log a warning and continue processing; 'ignore' to continue processing and ignore the timeout.

fail

camel.component.debezium-postgres.lsn-flush-timeout-ms

Maximum time in milliseconds to wait for LSN flush operation to complete. If the flush operation does not complete within this timeout, the action specified by lsn.flush.timeout.action will be taken. Defaults to 30 seconds. The option is a long type.

30000

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

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

2048

camel.component.debezium-postgres.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

camel.component.debezium-postgres.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

camel.component.debezium-postgres.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

camel.component.debezium-postgres.message-prefix-exclude-list

A comma-separated list of regular expressions that match the logical decoding message prefixes to be excluded from monitoring.

camel.component.debezium-postgres.message-prefix-include-list

A comma-separated list of regular expressions that match the logical decoding message prefixes to be monitored. All prefixes are monitored by default.

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

List of notification channels names that are enabled.

camel.component.debezium-postgres.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

camel.component.debezium-postgres.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.

camel.component.debezium-postgres.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

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

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

60000

camel.component.debezium-postgres.offset-storage

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

org.apache.kafka.connect.storage.FileOffsetBackingStore

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

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

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

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

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

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

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

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

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

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

./openlineage.yml

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

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

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

Enable Debezium to emit data lineage metadata through OpenLineage API

false

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

The job’s description emitted by Debezium

Debezium change data capture job

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

The job’s namespace emitted by Debezium

camel.component.debezium-postgres.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

camel.component.debezium-postgres.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

camel.component.debezium-postgres.plugin-name

The name of the Postgres logical decoding plugin installed on the server. Supported values are 'decoderbufs' and 'pgoutput'. Defaults to 'decoderbufs'.

decoderbufs

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

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

500

camel.component.debezium-postgres.post-processors

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

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

Enables transaction metadata extraction together with event counting

false

camel.component.debezium-postgres.publication-autocreate-mode

Applies only when streaming changes using pgoutput.Determine how creation of a publication should work, the default is all_tables.DISABLED - The connector will not attempt to create a publication at all. The expectation is that the user has created the publication up-front. If the publication isn’t found to exist upon startup, the connector will throw an exception and stop.ALL_TABLES - If no publication exists, the connector will create a new publication for all tables. Note this requires that the configured user has access. If the publication already exists, it will be used. i.e CREATE PUBLICATION FOR ALL TABLES;FILTERED - If no publication exists, the connector will create a new publication for all those tables matchingthe current filter configuration (see table/database include/exclude list properties). If the publication already exists, it will be used. i.e CREATE PUBLICATION FOR TABLE

all_tables

camel.component.debezium-postgres.publication-name

The name of the Postgres 10 publication used for streaming changes from a plugin. Defaults to 'dbz_publication'

dbz_publication

camel.component.debezium-postgres.publish-via-partition-root

A boolean that determines whether the connector should publish changes via the partition root. When true, changes are published through partition root. When false, changes are published directly.

false

camel.component.debezium-postgres.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.

0

camel.component.debezium-postgres.replica-identity-autoset-values

Applies only when streaming changes using pgoutput.Determines the value for Replica Identity at table level. This option will overwrite the existing value in databaseA comma-separated list of regular expressions that match fully-qualified tables and Replica Identity value to be used in the table. Each expression must match the pattern ':', where the table names could be defined as (SCHEMA_NAME.TABLE_NAME), and the replica identity values are: DEFAULT - Records the old values of the columns of the primary key, if any. This is the default for non-system tables.INDEX index_name - Records the old values of the columns covered by the named index, that must be unique, not partial, not deferrable, and include only columns marked NOT NULL. If this index is dropped, the behavior is the same as NOTHING.FULL - Records the old values of all columns in the row.NOTHING - Records no information about the old row. This is the default for system tables.

camel.component.debezium-postgres.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

camel.component.debezium-postgres.schema-exclude-list

The schemas for which events must not be captured

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

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

camel.component.debezium-postgres.schema-include-list

The schemas for which events should be captured

camel.component.debezium-postgres.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

camel.component.debezium-postgres.schema-refresh-mode

Specify the conditions that trigger a refresh of the in-memory schema for a table. 'columns_diff' (the default) is the safest mode, ensuring the in-memory schema stays in-sync with the database table’s schema at all times. 'columns_diff_exclude_unchanged_toast' instructs the connector to refresh the in-memory schema cache if there is a discrepancy between it and the schema derived from the incoming message, unless unchanged TOASTable data fully accounts for the discrepancy. This setting can improve connector performance significantly if there are frequently-updated tables that have TOASTed data that are rarely part of these updates. However, it is possible for the in-memory schema to become outdated if TOASTable columns are dropped from the table.

columns_diff

camel.component.debezium-postgres.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.

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

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

source

camel.component.debezium-postgres.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

camel.component.debezium-postgres.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

camel.component.debezium-postgres.slot-drop-on-stop

Whether or not to drop the logical replication slot when the connector finishes orderly. By default the replication is kept so that on restart progress can resume from the last recorded location

false

camel.component.debezium-postgres.slot-failover

Whether or not to create a failover slot. This is only supported when connecting to a primary server of a Postgres cluster, version 17 or newer. When not specified, or when not connecting to a Postgres 17 primary, no failover slot will be created.

false

camel.component.debezium-postgres.slot-max-retries

How many times to retry connecting to a replication slot when an attempt fails.

6

camel.component.debezium-postgres.slot-name

The name of the Postgres logical decoding slot created for streaming changes from a plugin. Defaults to 'debezium

debezium

camel.component.debezium-postgres.slot-retry-delay-ms

Time to wait between retry attempts when the connector fails to connect to a replication slot, given in milliseconds. Defaults to 10 seconds (10,000 ms). The option is a long type.

10000

camel.component.debezium-postgres.slot-stream-params

Any optional parameters used by logical decoding plugin. Semi-colon separated. E.g. 'add-tables=public.table,public.table2;include-lsn=true'

camel.component.debezium-postgres.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

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

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

camel.component.debezium-postgres.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.

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

Controls which transaction isolation level is used. The default is 'serializable', which means that serializable isolation level is used. When 'repeatable_read' is specified, connector runs the initial snapshot in REPEATABLE READ isolation level. When 'read_committed' is specified, connector runs the initial snapshot in READ COMMITTED isolation level. In 'read_uncommitted' is specified, connector runs the initial snapshot in READ UNCOMMITTED isolation level.

serializable

camel.component.debezium-postgres.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

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

Controls how the connector holds locks on tables while performing the schema snapshot. The 'shared' which means the connector will hold a table lock that prevents 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.

none

camel.component.debezium-postgres.snapshot-locking-mode-custom-name

When 'snapshot.locking.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 'SnapshotterLocking' interface and is called to determine how to lock tables during schema snapshot.

camel.component.debezium-postgres.snapshot-max-threads

The maximum number of threads used to perform the snapshot. Defaults to 1.

1

camel.component.debezium-postgres.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

camel.component.debezium-postgres.snapshot-mode

The criteria for running a snapshot upon startup of the connector. Select one of the following snapshot options: 'always': The connector runs a snapshot every time that it starts. After the snapshot completes, the connector begins to stream changes from the transaction log.; 'initial' (default): If the connector does not detect any offsets for the logical server name, it runs a snapshot that captures the current full state of the configured tables. After the snapshot completes, the connector begins to stream changes from the transaction log. 'initial_only': The connector performs a snapshot as it does for the 'initial' option, but after the connector completes the snapshot, it stops, and does not stream changes from the transaction log.; 'never': The connector does not run a snapshot. Upon first startup, the connector immediately begins reading from the beginning of the transaction log. 'exported': This option is deprecated; use 'initial' instead.; 'custom': The connector loads a custom class to specify how the connector performs snapshots. For more information, see Custom snapshotter SPI in the PostgreSQL connector documentation.

initial

camel.component.debezium-postgres.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

camel.component.debezium-postgres.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

camel.component.debezium-postgres.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

camel.component.debezium-postgres.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

camel.component.debezium-postgres.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

camel.component.debezium-postgres.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.

camel.component.debezium-postgres.snapshot-query-mode

Controls query used during the snapshot

select_all

camel.component.debezium-postgres.snapshot-query-mode-custom-name

When 'snapshot.query.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 'SnapshotterQuery' interface and is called to determine how to build queries during snapshot.

camel.component.debezium-postgres.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.

camel.component.debezium-postgres.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

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

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

io.debezium.connector.postgresql.PostgresSourceInfoStructMaker

camel.component.debezium-postgres.status-update-interval-ms

Frequency for sending replication connection status updates to the server, given in milliseconds. Defaults to 10 seconds (10,000 ms). The option is a int type.

10000

camel.component.debezium-postgres.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

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

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

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

Flag specifying whether built-in tables should be ignored.

true

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

The tables for which changes are to be captured

camel.component.debezium-postgres.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.

adaptive

camel.component.debezium-postgres.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

camel.component.debezium-postgres.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

camel.component.debezium-postgres.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.

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

Class to make transaction context & transaction struct/schemas

io.debezium.pipeline.txmetadata.DefaultTransactionMetadataFactory

camel.component.debezium-postgres.unavailable-value-placeholder

Specify the constant that will be provided by Debezium to indicate that the original value is a toasted value not provided by the database. If starts with 'hex:' prefix it is expected that the rest of the string represents hexadecimal encoded octets.

__debezium_unavailable_value

camel.component.debezium-postgres.xmin-fetch-interval-ms