Get started with a free trial today
Already have an account? Sign in
This version of MongoDB reached end of life onFebruary 2, 2020 and is no longer functioning.
Upgrade to the latest version (v3) to continue replicating data.
A high-level look at Stitch's MongoDB (v11-01-2016) integration, including release status, useful links, and the features supported in Stitch.
| STITCH | |||
| Release status | Sunset on February 2, 2020 | Supported by | |
| Stitch plan | Standard | Supported versions | 2.4 through 3.4 |
| API availability | Not available | Singer GitHub repository | Not applicable |
| CONNECTION METHODS | |||
| SSH connections | Supported | SSL connections | Supported |
| REPLICATION SETTINGS | |||
| Anchor Scheduling | Unsupported | Advanced Scheduling | Unsupported |
| Table-level reset | Unsupported | Configurable Replication Methods | Unsupported |
| REPLICATION METHODS | |||
| Log-based Replication | Unsupported | Key-based Replication | Supported |
| Full Table Replication | Unsupported | ||
| DATA SELECTION | |||
| Table selection | Supported | Column selection | Unsupported |
| View replication | Unsupported | Select all | Unsupported |
| TRANSPARENCY | |||
| Extraction Logs | Unsupported | Loading Reports | Supported |
Only Key-based Incremental Replication is supported for MongoDB integrations at this time. If a ever requires full replication - for example, to backfill existing rows with a new ‘s values - will require a full re-replication of the integration’s data. Refer to theReset Replication Keys guide for more info.
Unlike Replication Keys for other database integrations, those for MongoDB have special considerations due to MongoDB functionality. For example: MongoDB allows multiple data types in a single field, which can cause records to be skipped during replication.
Refer to theMongoDB Replication Keys guide before you define the Replication Keys for your s, as incorrectly defining Replication Keys can cause data discrepancies.
MongoDB data can only be tracked at the collection level. This means that when a collection is set to replicate in Stitch, all documents in the collection will also be selected.
MongoDB documents can contain heavily nested data, meaning an attribute can contain many other attributes.
If your destination doesn’t natively support nested data structures, Stitch will de-nest them to load them into the destination. Depending on how deeply nested the data is and the per table column limit of the destination, Stitch may encounter issues when loading heavily nested data.
Refer to theNested Data Structures guide for more info and examples.
If fields you expect to see are missing from a collection’s Replication Key menu, it may be that the fields aren’t indexed. Refer to theMongo Replication Keys guide for more info.
| Related | Troubleshooting |
Did this article help? If you have questions or feedback, feel free tosubmit a pull request with your suggestions,open an issue on GitHub, orreach out to us.