Question 1

How does writing into MongoDB work?

Accepted Answer

As a model sync with mapped document fields and paths rather than bulk table replication, since MongoDB is not available as a bulk sync destination. You decide the document shape and map Redshift columns onto it, including nested paths. The collection can be created for you and arbitrary fields added, so the destination structure does not have to exist in full before the first run.

Question 2

How are existing documents matched?

Accepted Answer

By the document identifier where you map one, which is the most reliable route, and serialized ObjectID values are converted rather than treated as plain strings. Without one, matching falls back to whichever destination field you nominated as the identity. Inserts and updates are grouped into bulk write calls, and classification into insert or update work happens before the write rather than relying on an upsert flag.

Question 3

How should I model the data first?

Accepted Answer

In Redshift SQL, before it reaches the sync. Warehouse tables are flat and wide by nature, so the useful work is deciding which columns become top level document fields and which belong under a nested path, then producing one row per document you intend to write. Doing that in the model keeps the mapping legible and means changing the document shape later is a SQL change rather than a remapping exercise.

Question 4

Is there anything to watch on types?

Accepted Answer

Datetimes mainly. Values mapped to a datetime field are strictly coerced, so a malformed value becomes a record level error rather than being quietly written as a string. That surfaces the problem rows rather than hiding them, but it does mean loosely formatted timestamps produce errors on a first run. Normalising them in the Redshift model is faster than diagnosing them afterwards.

Question 5

How do I connect Redshift to MongoDB?

Accepted Answer

Connect Redshift with cluster details, credentials and an S3 staging bucket, using an SSH tunnel if the cluster is private, and connect MongoDB with an Atlas connection string or explicit host details. Because this runs as a model sync, the next step is deciding the document shape rather than choosing a table to copy. Map Redshift columns onto document fields and paths, map an identifier so existing documents are matched, then set a schedule.

Connect Redshift with MongoDB

Connect Redshift and MongoDB with Polytomic

You define the document

Matches on document ID

Grouped bulk writes

Trusted by businesses worldwide

Step-by-step integration guide

Connect Redshift in Polytomic

Connect MongoDB in Polytomic

Create a sync between Redshift and MongoDB

Map fields and enable the sync

Frequently asked questions

The sync and ETL platform that does it all

Powerful data sync

Advanced analytics

Enterprise security

Easy setup

Ready to connect Redshift with MongoDB?