May 2022link
We now automatically reschedule the connector’s sync when oplog or change stream cursors expire. For more information about cursor expiry, see our documentation.
April 2022link
For new MongoDB connectors, we now sync UUID in the STANDARD representation, which means that binary data is synced in binary format instead of transformed to VARCHAR. We will roll this change out to existing connectors on August 1, 2022. We will notify you before we apply this change to your connector so you can update your downstream queries.
December 2021link
We now support MongoDB database versions 4.4 to 5.0. To learn more, read MongoDB’s 5.0 changelog.
We now support Read-Only and Analytics nodes. You must configure read preference and tags based on the node type. For more information, see Specify Read Preference for a MongoDB Cluster.
September 2021link
We have introduced packed mode, a new sync mode for MongoDB tables. Previously, we only supported unpacked mode. For more details, see our MongoDB documentation.
October 2020link
We have improved incremental sync performance for databases which have many changes in collections that are not included in the sync.
April 2020link
We now support SRV host records.
You can now configure your MongoDB Sharded Cluster connector through the Fivetran REST API. This feature is in BETA and available only for Standard and Enterprise accounts.
February 2020link
Fivetran has updated our MongoDB connector to improve sync reliability. As a part of this update, we have begun rolling out support for BINARY and BSONBINARY data types.
We have updated our MongoDB connector to support syncing data from MongoDB versions 2.6 to 4.2.
September 2019link
If you have a logging service connected to your Fivetran account, the import progress of your tables in the event logs will be visible in your logs as an import_progress event. Table names will be in either the COMPLETE or IN_PROGRESS state, depending on their sync status. Tables that are not reported in the event have not started their import.
August 2019link
We fixed a bug that prevented our connector from syncing some of our MongoDB and MongoDB Sharded customers who use multiple hosts with Fivetran. The bug prevented us from syncing using standard Mongo drivers. To work around it, we now connect to the first host you list in the setup form, and if it fails, we try the next one. If needed, we continue in this manner through all of your listed hosts.
You do not need to take any action to take advantage of this improvement. If your connector was unaffected by the original bug, we will continue to use standard Mongo drivers method.
December 2018link
You can now assign multiple hosts (master and replicas) for the MongoDB connector.
October 2018link
We have optimized the way we do incremental updates from the oplog of nested updates. Previously, when you updated deeply nested fields, we had to fetch the entire document using collection.find({_id:?}). This process can be extremely slow and delay syncs for hours, especially when deeply nested fields are frequently updated. We can now fetch these documents in batches, making our MongoDB syncs ten times faster.
September 2018link
We have fixed a bug that caused BSON INT32 types to not sync during our initial syncs.
June 2018link
Sync a Sharded MongoDB cluster with automatic node discovery and roll-over.
Link to Sharded MongoDB documentation
April 2018link
During setup, we now verify that we have the correct permissions to list all your tables.