MongoDB Change Streams Overview
  • 3 Minutes to read
  • Dark
  • PDF

MongoDB Change Streams Overview

  • Dark
  • PDF

Article Summary

What is Change Streams Extraction?

Rivery's Log-Based extraction mode provides a real-time stream of any changes made to the databases and tables configured, eliminating the need to implement and maintain incremental fields or retrieve data via select queries. It also allows you to retrieve schema changes from the database.

How Does Change Streams Extraction Work?

Rivery uses the Change Data Capture architecture to continuously pull new rows from the Change Streams in order to retrieve data.

Change Streams is a fast and effective method of continuously fetching data from databases using the database transaction log.

Rivery uses the Overwrite loading mode to take a full snapshot (or migration) of the chosen table(s) in order to align the data and metadata as it was on the first run. Rivery takes the existing 'Change Stream' records and performs an Upsert-Merge to the target table(s) after the migration is complete, while continuing to fetch new records from the log as they are created.

Rivery's MongoDB connection reads the 'Change Stream' records and generates change events in the FileZone files for row-level INSERT and UPDATE commands. Each file represents a set of database actions performed over a period of time. The data from the log is continuously streamed into the FileZone path established in the River and pushed into the target by the River's scheduled frequency. This method saves the data first in the FileZone, and then it may be pushed into the target DWH at any moment.

FileZone is covered in further detail in the Target documentation.

For further information about Change Streams Metadata Fields, please refer to our Database Overview document.

How to Enable Change Streams Extraction?

After you've established a connection, go to the Source tab and do the following:

  1. Choose the Multi-Collection as the River mode.

  2.  select the Change Streams as the extraction mode.

  3. A brief reminder appears, encouraging you to check your connection and set up your Source and Target, which will happen next. Select 'Got It' to proceed.

  4. Turn the 'Enable Stream' toggle to true at the bottom of the page. 

  5.  A new window pops up, guiding you on the following steps. Select 'Target'.

  6.  You'll be directly sent to the Target tab, where you can choose your data target.

  7.  Define your Target Connection, then choose a Database and a Schema to load into.

  8. To make sure the operation is complete, click the Enable Log toggle once more. 

  9.  To navigate to the Collections, click the Schema tab.

  10.  A minimum of one Collection must be chosen. 

  11. To use CDC, the table must contain a key, which is defined as the Source Column _id. 

  12.  Navigate to the 'Enable Stream' toggle and select the number of hours you want to run the River, then click 'I'm Sure'. 

  13.  Wait for the Initiation Log to complete its processing. 

  14.  You're all set to run your log-based River now.

  15. Following the completion of the River Run, return to the Schema tab and check that the Collections you selected are Streaming


  • There are some limitations when it comes to connecting to MongoDB (click the URI and SSH to get to their documentation):


If you're using Change Streams with Atlas, leave the analytics node out of the connection URI.

You can only connect to the Primary Node with MongoDB Atlas. We'll be able to connect to the Analytics Node, but we won't be able to get any messages from it due to Atlas' implementation.


  • We currently only enable SSH tunneling to a single DNS (host). This means that the SSH tunnel method does not support multiple DNSs in replicas as shown here:,
  • If you're using Atlas with Log-Based, employ Private Endpoint to connect to several hosts.

  • MongoDB will not send any documents that are more than 16MB in size, including all metadata in the change stream.

  • Any special character will be replaced with an underscore. As a result, if you wish to edit the table name, go to: 

         1. The 'Schema' tab

         2. Select a collection

         3. Click 'Table Settings'

         4. Choose 'Edit' to change the table name manually.

Was this article helpful?