Trigger

Wait for change data capture event on MongoDB server and create new execution.

If you would like to consume each message from change data capture in real-time and create one execution per message, you can use the io.kestra.plugin.debezium.mongodb.RealtimeTrigger instead.

yaml
type: "io.kestra.plugin.debezium.mongodb.Trigger"

Sharded connection

yaml
id: debezium-mongodb
namespace: company.team

tasks:
  - id: send_data
    type: io.kestra.plugin.core.log.Log
    message: "{{ trigger.data }}"

triggers:
  - id: trigger
    type: io.kestra.plugin.debezium.mongodb.Trigger
    snapshotMode: INITIAL
    connectionString: mongodb://mongo_user:mongo_passwd@mongos0.example.com:27017,mongos1.example.com:27017/

Replica set connection

yaml
id: debezium-mongodb
namespace: company.team

tasks:
  - id: send_data
    type: io.kestra.plugin.core.log.Log
    message: "{{ trigger.data }}"

triggers:
  - id: trigger
    type: io.kestra.plugin.debezium.mongodb.Trigger
    snapshotMode: INITIAL
    connectionString: mongodb://mongo_user:mongo_passwd@mongodb0.example.com:27017/?replicaSet=rs0

Dynamic YES

Defines connection string to mongodb replica set or sharded

Dynamic YES

Default deleted

The name of deleted field if deleted is ADD_FIELD.

Dynamic YES

Default

Hostname of the remote server.

Dynamic YES

Default ADD_FIELD

Possible Values

ADD_FIELDDROP

Specify how to handle key.

Possible settings are:

ADD_FIELD: Add key(s) merged with columns.
DROP: Drop keys.

Dynamic YES

Default metadata

The name of metadata field if metadata is ADD_FIELD.

Dynamic YES

Default INITIAL

Possible Values

INITIALINITIAL_ONLYNO_DATAWHEN_NEEDED

Specifies the criteria for running a snapshot when the connector starts.

Possible settings are:

INITIAL: The connector runs a snapshot only when no offsets have been recorded for the logical server name.
INITIAL_ONLY: The connector runs a snapshot only when no offsets have been recorded for the logical server name and then stops; i.e. it will not read change events from the binlog.
NO_DATA: The connector captures the structure of all relevant tables, performing all the steps described in the default snapshot workflow, except that it does not create READ events to represent the data set at the point of the connector’s start-up.
WHEN_NEEDED: The connector runs a snapshot upon startup whenever it deems it necessary. That is, when no offsets are available, or when a previously recorded offset specifies a binlog location or GTID that is not available in the server.

Dynamic YES

Default debezium-state

The name of the Debezium state file stored in the KV Store for that namespace.

SubType

Dynamic NO

List of conditions in order to limit the flow trigger.

Dynamic YES

Default ADD_FIELD

Possible Values

ADD_FIELDNULLDROP

Specify how to handle deleted rows.

Possible settings are:

ADD_FIELD: Add a deleted field as boolean.
NULL: Send a row with all values as null.
DROP: Don't send deleted row.

Dynamic YES

The name of the MongoDB database collection excluded from which to stream the changes.

A list of regular expressions that match the collection namespaces (for example, .) of all collections to be excluded

Dynamic YES

An optional, comma-separated list of regular expressions that match the fully-qualified names of columns to include in change event record values.

Fully-qualified names for columns are of the form databaseName.tableName.columnName. Do not also specify the includedColumns connector configuration property."

Dynamic YES

An optional, comma-separated list of regular expressions that match the names of databases for which you do not want to capture changes.

The connector captures changes in any database whose name is not in the excludedDatabases. Do not also set the includedDatabases connector configuration property.

Dynamic YES

An optional, comma-separated list of regular expressions that match fully-qualified table identifiers for tables whose changes you do not want to capture.

The connector captures changes in any table not included in excludedTables. Each identifier is of the form databaseName.tableName. Do not also specify the includedTables connector configuration property.

Dynamic YES

Default INLINE

Possible Values

RAWINLINEWRAP

The format of the output.

Possible settings are:

RAW: Send raw data from debezium.
INLINE: Send a row like in the source with only data (remove after & before), all the columns will be present for each row.
WRAP: Send a row like INLINE but wrapped in a record field.

Dynamic YES

Default true

Ignore DDL statement.

Ignore CREATE, ALTER, DROP and TRUNCATE operations.

Dynamic YES

The name of the MongoDB database collection included from which to stream the changes.

A list of regular expressions that match the collection namespaces (for example, .) of all collections to be monitored

Dynamic YES

An optional, comma-separated list of regular expressions that match the fully-qualified names of columns to exclude from change event record values.

Fully-qualified names for columns are of the form databaseName.tableName.columnName. Do not also specify the excludedColumns connector configuration property.

Dynamic YES

An optional, comma-separated list of regular expressions that match the names of the databases for which to capture changes.

The connector does not capture changes in any database whose name is not in includedDatabases. By default, the connector captures changes in all databases. Do not also set the excludedDatabases connector configuration property.

Dynamic YES

An optional, comma-separated list of regular expressions that match fully-qualified table identifiers of tables whose changes you want to capture.

The connector does not capture changes in any table not included in includedTables. Each identifier is of the form databaseName.tableName. By default, the connector captures changes in every non-system table in each database whose changes are being captured. Do not also specify the excludedTables connector configuration property.

Dynamic NO

Default 60

Format duration

Interval between polling.

The interval between 2 different polls of schedule, this can avoid to overload the remote system with too many calls. For most of the triggers that depend on external systems, a minimal interval must be at least PT30S. See ISO_8601 Durations for more information of available interval values.

Dynamic YES

Format duration

Dynamic YES

Default PT10S

Format duration

Dynamic YES

Default ADD_FIELD

Possible Values

ADD_FIELDDROP

Specify how to handle metadata.

Possible settings are:

ADD_FIELD: Add metadata in a column named metadata.
DROP: Drop metadata.

Dynamic YES

Password on the remote server.

Dynamic YES

Default

Port of the remote server.

SubType string

Dynamic YES

Additional configuration properties.

Any additional configuration properties that is valid for the current driver.

Dynamic YES

Default TABLE

Possible Values

OFFDATABASETABLE

Split table on separate output uris.

Possible settings are:

TABLE: This will split all rows by tables on output with name database.table
DATABASE: This will split all rows by databases on output with name database.
OFF: This will NOT split all rows resulting in a single data output.

SubType string

Dynamic NO

Possible Values

CREATEDRUNNINGPAUSEDRESTARTEDKILLINGSUCCESSWARNINGFAILEDKILLEDCANCELLEDQUEUEDRETRYINGRETRIEDSKIPPED

List of execution states after which a trigger should be stopped (a.k.a. disabled).

Dynamic YES

Username on the remote server.

The number of fetched rows

The KV Store key under which the state of the database history is stored

The KV Store key under which the state of the offset is stored

SubType string

URI of the generated internal storage file

​Trigger

Trigger