Release Notes
November 2024
If your MongoDB server version is less than 4.0, you must upgrade to a supported version by March 1, 2025. Otherwise, the MongoDB drivers will no longer be compatible with your server version. Learn more in MongoDB's MongoDB's software lifecycle schedules documentation.
August 2024
We now sync BSON_NULL and BSON_UNDEFINED data types. Learn more in our Type Transformations and Mapping documentation.
November 2023
You can now choose to sync your BINARY data with either Base64 or UUID representations in your MongoDB connector setup form. We are gradually rolling this change out first for existing connectors, then for new connectors. Learn more in our Type Transformations and Mapping documentation.
October 2023
MongoDB connectors created on or after October 18, 2023, support two pack modes, Packed mode and Unpacked mode, at the connector level. We have now updated the default option of the Pack mode feature to Packed mode. When you select a pack mode on the Connector Details page, the selected behavior applies to all the tables enabled for the sync.
For MongoDB connectors created before October 18, 2023, we continue to support both the pack modes at the table level.
To learn more, see our MongoDB pack mode documentation.
July 2023
We now support multithreading for the connector's initial sync for MongoDB 4.2 or later. We now use multiple parallel database calls to sync data from your MongoDB database to your destination, which makes your sync faster.
February 2023
We now use Change Streams as the default incremental sync strategy. For more information about change streams, see our documentation.
January 2023
We now sync BSON_TIMESTAMP data type as INSTANT. For more details, see our documentation.
November 2022
We now support the configuration of the read preference during the connector setup using connection tags in the connection string. For more information, see either the MongoDB sharded cluster or the MongoDB replica set setup guide.
October 2022
We now convert UUID data type to STRING (Base64-decoded) in the destination. Previously, we didn't convert UUID data type. This functionality is enabled by default for new connectors created after October 10, 2022. We are gradually rolling out the feature to all the existing connectors.
September 2022
We have extended packed mode support to our REST API. You can now select the sync mode for your database tables and also specify the tables you want to sync using packed mode.
Our MongoDB Sharded Cluster connector now supports the following:
- SRV hosts. For example,
mongodb+srv://server.example.com/?readPreference=secondary&readPreferenceTags=nodeType:ANALYTICS - Connection strings. For example,
mongodb://query-router-00.example.com:27016,query-router-01.example.com:27016,query-router-02.example.com:27016/?readPreference=secondary&readPreferenceTags=workloadType:OPERATIONAL&readConcernLevel=local - Multiple mongos query routers. For example,
query-router-00.example.com:27016,query-router-01.example.com:27016,query-router-02.example.com:27016
For more information, see our setup instructions. We are gradually rolling out this feature to all existing connectors. If you'd like to enable this feature on your connector, contact our support team.
August 2022
Fivetran history mode is now in beta for the following connectors:
Learn more in our history mode documentation.
Our MongoDB Replica Set connector now supports the following:
- Connection tags with SRV hosts. For example,
mongodb+srv://server.example.com/?readPreference=secondary&readPreferenceTags=nodeType:ANALYTICS. - Connection strings. For example,
mongodb://mongodb0.example.com:27017,mongodb1.example.com:27017,mongodb2.example.com:27017/?replicaSet=myRepl&readPreference=secondary.
For more information, see our setup instructions. We are gradually rolling out this feature to all existing connectors. If you'd like to enable this feature on your connector, contact our support team.
We have added a new database setup test to our MongoDB Replica Set connector. Now, we verify if we can access your MongoDB change streams or oplog.
May 2022
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 2022
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 2021
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 2021
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 2020
We have improved incremental sync performance for databases which have many changes in collections that are not included in the sync.
April 2020
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 2020
We have updated our MongoDB connector to improve sync reliability. As a part of this update, we have begun rolling out support for BINARY and BSON_BINARY data types.
We have updated our MongoDB connector to support syncing data from MongoDB versions 2.6 to 4.2.
September 2019
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 2019
We fixed a bug that prevented our connector from syncing data of some of our MongoDB and MongoDB Sharded users 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 leverage this improvement. If your connector was unaffected by the original bug, we will continue to use standard Mongo drivers method.
March 2019
We are changing our architecture to allow for much higher data throughput. Starting on April 30, 2019, all Fivetran connectors will originate from a new set of fixed IP addresses. For the US region, these IPs are:
- 35.227.135.0/29
- 35.234.176.144/29
- 52.0.2.4/32.
Update your IP safelists for the following databases and destinations before April 30. Not doing so will result in a connection failure.
Databases:
- MariaDB
- MongoDB
- MySQL
- Oracle
- PostgreSQL
- SQL Server
Destinations:
- Redshift
- Azure Synapse
- Snowflake
If you don't use any of the above databases or destinations with Fivetran, you don't need to take any action.
December 2018
You can now assign multiple hosts (master and replicas) for the MongoDB connector.
November 2018
You can now trigger re-syncs of individual tables from your Fivetran dashboard:
The re-sync button appears when you hover your cursor over the row that contains the table name.
This feature is available for the following connectors:
- Amazon DynamoDB
- MongoDB
- MySQL
- NetSuite SuiteAnalytics
- Oracle
- PostgreSQL
- Salesforce
- SQL Server
- Zuora
October 2018
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 2018
We have fixed a bug that caused BSON_INT_32 data types to not sync during our initial syncs.
June 2018
We now support MongoDB sharded cluster.
For more information, see our MongoDB Sharded Cluster setup instructions.
April 2018
During connector setup, we now verify that we have the correct permissions to list all your tables.