MongoDB Source Connector
Source connector
MongoDB Source Connector
MongoDB replication uses the Debezium MongoDB connector and captures changes from replica sets or sharded deployments.
Connector Class
io.debezium.connector.mongodb.MongoDbConnector
Parameters
| Category | Parameter | Required | Recommended / Default | Description |
|---|---|---|---|---|
| Basic | name | Yes | User-defined | Unique connector name. GIFROST derives topic.prefix as <name>-server. |
| Basic | tasks.max | Yes | Deployment-specific | MongoDB can use multiple tasks depending on topology, but start conservatively. |
| Database Connection | mongodb.connection.string | Yes | From Database Store | MongoDB connection string. |
| Database Wizard | database.include.list / database.exclude.list | No | Generated | Database filters. |
| Database Wizard | collection.include.list / collection.exclude.list | No | Generated | Collection filters. |
| Database Wizard | field.exclude.list | No | Generated | Field exclusions. |
| Snapshot | snapshot.mode | No | initial | Initial loading behavior. |
| Snapshot | snapshot.fetch.size | No | Defaults | Batch size for snapshot reads. |
| Connector | capture.mode | No | Deployment-specific | Controls how update events and full documents are captured. |
| Connector | poll.interval.ms, max.batch.size, max.queue.size | No | Defaults | Runtime polling and buffering. |
| Notification | notification.sink.topic.name | No | <connector-name>-notifications | Topic for Debezium notifications. |
MongoDB Notes
MongoDB does not use relational schemas and tables. In GIFROST, the same workflow applies, but the scope is expressed as databases, collections, and fields.