- Introduction
- Getting Started
- Creating an Account in Hevo
- Subscribing to Hevo via AWS Marketplace
-
Connection Options
- Connecting Through SSH
- Connecting Through Reverse SSH Tunnel
- Connecting Through VPN
- Connecting Through Mongo PrivateLink
- Connecting Through AWS Transit Gateway
- Connecting Through AWS VPC Endpoint
- Connecting Through AWS VPC Peering
- Using Google Account Authentication
- How Hevo Authenticates Sources and Destinations using OAuth
- Reauthorizing an OAuth Account
- Familiarizing with the UI
- Creating your First Pipeline
- Data Loss Prevention and Recovery
- Data Ingestion
- Data Loading
- Loading Data in a Database Destination
- Loading Data to a Data Warehouse
- Optimizing Data Loading for a Destination Warehouse
- Deduplicating Data in a Data Warehouse Destination
- Manually Triggering the Loading of Events
- Scheduling Data Load for a Destination
- Loading Events in Batches
- Data Loading Statuses
- Data Spike Alerts
- Name Sanitization
- Table and Column Name Compression
- Parsing Nested JSON Fields in Events
- Pipelines
- Data Flow in a Pipeline
- Familiarizing with the Pipelines UI
- Working with Pipelines
- Managing Objects in Pipelines
- Pipeline Jobs
-
Transformations
-
Python Code-Based Transformations
- Supported Python Modules and Functions
-
Transformation Methods in the Event Class
- Create an Event
- Retrieve the Event Name
- Rename an Event
- Retrieve the Properties of an Event
- Modify the Properties for an Event
- Fetch the Primary Keys of an Event
- Modify the Primary Keys of an Event
- Fetch the Data Type of a Field
- Check if the Field is a String
- Check if the Field is a Number
- Check if the Field is Boolean
- Check if the Field is a Date
- Check if the Field is a Time Value
- Check if the Field is a Timestamp
-
TimeUtils
- Convert Date String to Required Format
- Convert Date to Required Format
- Convert Datetime String to Required Format
- Convert Epoch Time to a Date
- Convert Epoch Time to a Datetime
- Convert Epoch to Required Format
- Convert Epoch to a Time
- Get Time Difference
- Parse Date String to Date
- Parse Date String to Datetime Format
- Parse Date String to Time
- Utils
- Examples of Python Code-based Transformations
-
Drag and Drop Transformations
- Special Keywords
-
Transformation Blocks and Properties
- Add a Field
- Change Datetime Field Values
- Change Field Values
- Drop Events
- Drop Fields
- Find & Replace
- Flatten JSON
- Format Date to String
- Format Number to String
- Hash Fields
- If-Else
- Mask Fields
- Modify Text Casing
- Parse Date from String
- Parse JSON from String
- Parse Number from String
- Rename Events
- Rename Fields
- Round-off Decimal Fields
- Split Fields
- Examples of Drag and Drop Transformations
- Effect of Transformations on the Destination Table Structure
- Transformation Reference
- Transformation FAQs
-
Python Code-Based Transformations
-
Schema Mapper
- Using Schema Mapper
- Mapping Statuses
- Auto Mapping Event Types
- Manually Mapping Event Types
- Modifying Schema Mapping for Event Types
- Schema Mapper Actions
- Fixing Unmapped Fields
- Resolving Incompatible Schema Mappings
- Resizing String Columns in the Destination
- Schema Mapper Compatibility Table
- Limits on the Number of Destination Columns
- File Log
- Troubleshooting Failed Events in a Pipeline
- Mismatch in Events Count in Source and Destination
- Audit Tables
- Activity Log
-
Pipeline FAQs
- Can multiple Sources connect to one Destination?
- What happens if I re-create a deleted Pipeline?
- Why is there a delay in my Pipeline?
- Can I change the Destination post-Pipeline creation?
- Why is my billable Events high with Delta Timestamp mode?
- Can I drop multiple Destination tables in a Pipeline at once?
- How does Run Now affect scheduled ingestion frequency?
- Will pausing some objects increase the ingestion speed?
- Can I see the historical load progress?
- Why is my Historical Load Progress still at 0%?
- Why is historical data not getting ingested?
- How do I set a field as a primary key?
- How do I ensure that records are loaded only once?
- Events Usage
- Sources
- Free Sources
-
Databases and File Systems
- Data Warehouses
-
Databases
- Connecting to a Local Database
- Amazon DocumentDB
- Amazon DynamoDB
- Elasticsearch
-
MongoDB
- Generic MongoDB
- MongoDB Atlas
- Support for Multiple Data Types for the _id Field
- Example - Merge Collections Feature
-
Troubleshooting MongoDB
-
Errors During Pipeline Creation
- Error 1001 - Incorrect credentials
- Error 1005 - Connection timeout
- Error 1006 - Invalid database hostname
- Error 1007 - SSH connection failed
- Error 1008 - Database unreachable
- Error 1011 - Insufficient access
- Error 1028 - Primary/Master host needed for OpLog
- Error 1029 - Version not supported for Change Streams
- SSL 1009 - SSL Connection Failure
- Troubleshooting MongoDB Change Streams Connection
- Troubleshooting MongoDB OpLog Connection
-
Errors During Pipeline Creation
- SQL Server
-
MySQL
- Amazon Aurora MySQL
- Amazon RDS MySQL
- Azure MySQL
- Generic MySQL
- Google Cloud MySQL
- MariaDB MySQL
-
Troubleshooting MySQL
-
Errors During Pipeline Creation
- Error 1003 - Connection to host failed
- Error 1006 - Connection to host failed
- Error 1007 - SSH connection failed
- Error 1011 - Access denied
- Error 1012 - Replication access denied
- Error 1017 - Connection to host failed
- Error 1026 - Failed to connect to database
- Error 1027 - Unsupported BinLog format
- Failed to determine binlog filename/position
- Schema 'xyz' is not tracked via bin logs
- Errors Post-Pipeline Creation
-
Errors During Pipeline Creation
- MySQL FAQs
- Oracle
-
PostgreSQL
- Amazon Aurora PostgreSQL
- Amazon RDS PostgreSQL
- Azure PostgreSQL
- Generic PostgreSQL
- Google Cloud PostgreSQL
- Heroku PostgreSQL
-
Troubleshooting PostgreSQL
-
Errors during Pipeline creation
- Error 1003 - Authentication failure
- Error 1006 - Connection settings errors
- Error 1011 - Access role issue for logical replication
- Error 1012 - Access role issue for logical replication
- Error 1014 - Database does not exist
- Error 1017 - Connection settings errors
- Error 1023 - No pg_hba.conf entry
- Error 1024 - Number of requested standby connections
- Errors Post-Pipeline Creation
-
Errors during Pipeline creation
- PostgreSQL FAQs
- Troubleshooting Database Sources
- File Storage
- Engineering Analytics
- Finance & Accounting Analytics
-
Marketing Analytics
- ActiveCampaign
- AdRoll
- Amazon Ads
- Apple Search Ads
- AppsFlyer
- CleverTap
- Criteo
- Drip
- Facebook Ads
- Facebook Page Insights
- Firebase Analytics
- Freshsales
- Google Campaign Manager
- Google Ads
- Google Analytics
- Google Analytics 4
- Google Analytics 360
- Google Play Console
- Google Search Console
- HubSpot
- Instagram Business
- Klaviyo v2
- Lemlist
- LinkedIn Ads
- Mailchimp
- Mailshake
- Marketo
- Microsoft Ads
- Onfleet
- Outbrain
- Pardot
- Pinterest Ads
- Pipedrive
- Recharge
- Segment
- SendGrid Webhook
- SendGrid
- Salesforce Marketing Cloud
- Snapchat Ads
- SurveyMonkey
- Taboola
- TikTok Ads
- Twitter Ads
- Typeform
- YouTube Analytics
- Product Analytics
- Sales & Support Analytics
- Source FAQs
- Destinations
- Familiarizing with the Destinations UI
- Cloud Storage-Based
- Databases
-
Data Warehouses
- Amazon Redshift
- Amazon Redshift Serverless
- Azure Synapse Analytics
- Databricks
- Firebolt
- Google BigQuery
- Hevo Managed Google BigQuery
- Snowflake
-
Destination FAQs
- Can I change the primary key in my Destination table?
- How do I change the data type of table columns?
- Can I change the Destination table name after creating the Pipeline?
- How can I change or delete the Destination table prefix?
- Why does my Destination have deleted Source records?
- How do I filter deleted Events from the Destination?
- Does a data load regenerate deleted Hevo metadata columns?
- How do I filter out specific fields before loading data?
- Transform
- Alerts
- Account Management
- Activate
- Glossary
Releases- Release 2.28.2 (Oct 07-14, 2024)
- Release 2.28.1 (Sep 30-Oct 07, 2024)
- Release 2.28 (Sep 02-30, 2024)
- 2024 Releases
-
2023 Releases
- Release 2.19 (Dec 04, 2023-Jan 15, 2024)
- Release Version 2.18
- Release Version 2.17
- Release Version 2.16 (with breaking changes)
- Release Version 2.15 (with breaking changes)
- Release Version 2.14
- Release Version 2.13
- Release Version 2.12
- Release Version 2.11
- Release Version 2.10
- Release Version 2.09
- Release Version 2.08
- Release Version 2.07
- Release Version 2.06
-
2022 Releases
- Release Version 2.05
- Release Version 2.04
- Release Version 2.03
- Release Version 2.02
- Release Version 2.01
- Release Version 2.00
- Release Version 1.99
- Release Version 1.98
- Release Version 1.97
- Release Version 1.96
- Release Version 1.95
- Release Version 1.93 & 1.94
- Release Version 1.92
- Release Version 1.91
- Release Version 1.90
- Release Version 1.89
- Release Version 1.88
- Release Version 1.87
- Release Version 1.86
- Release Version 1.84 & 1.85
- Release Version 1.83
- Release Version 1.82
- Release Version 1.81
- Release Version 1.80 (Jan-24-2022)
- Release Version 1.79 (Jan-03-2022)
-
2021 Releases
- Release Version 1.78 (Dec-20-2021)
- Release Version 1.77 (Dec-06-2021)
- Release Version 1.76 (Nov-22-2021)
- Release Version 1.75 (Nov-09-2021)
- Release Version 1.74 (Oct-25-2021)
- Release Version 1.73 (Oct-04-2021)
- Release Version 1.72 (Sep-20-2021)
- Release Version 1.71 (Sep-09-2021)
- Release Version 1.70 (Aug-23-2021)
- Release Version 1.69 (Aug-09-2021)
- Release Version 1.68 (Jul-26-2021)
- Release Version 1.67 (Jul-12-2021)
- Release Version 1.66 (Jun-28-2021)
- Release Version 1.65 (Jun-14-2021)
- Release Version 1.64 (Jun-01-2021)
- Release Version 1.63 (May-19-2021)
- Release Version 1.62 (May-05-2021)
- Release Version 1.61 (Apr-20-2021)
- Release Version 1.60 (Apr-06-2021)
- Release Version 1.59 (Mar-23-2021)
- Release Version 1.58 (Mar-09-2021)
- Release Version 1.57 (Feb-22-2021)
- Release Version 1.56 (Feb-09-2021)
- Release Version 1.55 (Jan-25-2021)
- Release Version 1.54 (Jan-12-2021)
-
2020 Releases
- Release Version 1.53 (Dec-22-2020)
- Release Version 1.52 (Dec-03-2020)
- Release Version 1.51 (Nov-10-2020)
- Release Version 1.50 (Oct-19-2020)
- Release Version 1.49 (Sep-28-2020)
- Release Version 1.48 (Sep-01-2020)
- Release Version 1.47 (Aug-06-2020)
- Release Version 1.46 (Jul-21-2020)
- Release Version 1.45 (Jul-02-2020)
- Release Version 1.44 (Jun-11-2020)
- Release Version 1.43 (May-15-2020)
- Release Version 1.42 (Apr-30-2020)
- Release Version 1.41 (Apr-2020)
- Release Version 1.40 (Mar-2020)
- Release Version 1.39 (Feb-2020)
- Release Version 1.38 (Jan-2020)
- Early Access New
- Upcoming Features
MongoDB Atlas
On This Page
After you have selected MongoDB Atlas as the Source for creating the Pipeline, provide the connection settings and data replication details listed here in the Configure your MongoDB Atlas Source page. You can fetch the database settings from your MongoDB Atlas account.
You can connect to the MongoDB database in one of the following ways:
-
By specifying the individual connection fields such as database host, database port, username, and password.
-
By entering the connection URI to connect to your MongoDB replica set or sharded cluster.
Connection URIs are of two types:
-
DNS Seedlist: This type of connection URI has the prefix
mongodb+srv://
.For example,
mongodb+srv://Jerome:Hevo123@cluster0.t7l5k.mongodb.net/test
.The
+srv
part indicates that the hostname corresponds to a DNS SRV record. The hostnames and port values for your MongoDB database are fetched from the DNS SRV record. -
Standard Connection String: This type of connection URI has the prefix
mongodb://
. This contains a comma-separated list of host:port combinations.For example,
mongodb://Jerome:Hevo123@cluster0-shard-00-00.t7l5k.mongodb.net:27017,cluster0-shard-00-01.t7l5k.mongodb.net:27017,cluster0-shard-00-02.t7l5k.mongodb.net:27017/test?replicaSet=atlas-uax6f3-shard-0&ssl=true&authSource=admin
.In the above example,
Jerome
is the database user andHevo123
is the password for the database user.
-
Prerequisites
-
The MongoDB version is 3.4 or higher.
-
Database settings of your MongoDB Atlas account are available.
-
You are assigned the Team Administrator, Team Collaborator, or Pipeline Administrator role in Hevo, to create the Pipeline.
Perform the following steps to configure your MongoDB Atlas Source:
Set up Permissions to Read MongoDB Atlas Databases (Optional)
You need to assign the required permissions to the database user to access the different MongoDB Atlas databases.
To do this, you can create a custom role and assign it to the database user. Or, you can provide pre-defined MongoDB roles to the database user.
1. Create a custom role
To create a custom role:
-
Log in to the MongoDB Atlas console.
-
In the left navigation pane, under Security, click Database Access.
-
In the Database Access page, click the Custom Roles tab.
-
Click +ADD NEW CUSTOM ROLE.
-
In the Add Custom Role pop-up window, specify the Custom Role Name.
-
Assign the required action or role:
-
If want to use the Change Streams ingestion mode for your Pipeline:
-
Assign either the
read
role or thelistCollections
action on thelocal
database. -
Assign either the
read
role or thefind
andchangeStream
actions on the database(s) you want to ingest. -
Assign either the
readAnyDatabase
role or thelistDatabases
action on theadmin
database. This is mandatory if you want to load data from all the databases, which is indicated by selecting the Load All Databases option during MongoDB Atlas Source configuration.
-
-
If want to use the OpLog ingestion mode for your Pipeline:
-
Assign either the
read
role or thefind
,listCollections
, andlistIndexes
actions on the database(s) you want to ingest. -
Assign the
read
role on thelocal
database.
-
-
-
Click Add Custom Role.
2. Create a database user
To create a database user:
-
Log in to the MongoDB Atlas console.
-
In the left navigation pane, under Security, click Database Access.
-
Click + ADD NEW DATABASE USER.
-
Select Password as the Authentication Method.
-
Under Password Authentication, specify the new username and password.
-
In the Database User Privileges section, do the following:
-
For custom roles created in the previous step:
-
Click Custom Roles.
-
Click Add Custom Role and select the role that you created above.
-
-
For specific MongoDB privileges:
-
Select Specific Privileges.
-
In the Select Role drop-down, assign the read role to the local Database.
-
Click Add Specific Privilege, and do one of the following:
-
Assign readAnyDatabase to the admin database. This is mandatory if you want to load data from all the databases; as indicated by selecting the Load All Databases option during MongoDB Atlas Source configuration.
-
Assign read privileges to the database(s) you want to ingest and listDatabases privileges on the admin database.
-
-
-
-
Click Add User.
Note: After you create or modify a user in the MongoDB Atlas console, you must wait five minutes for the changes to take effect.
Whitelist Hevo’s IP Addresses
To whitelist Hevo’s IP address:
-
Log in to the MongoDB Atlas console.
-
In the left navigation pane, under Security, click Network Access.
-
In the IP Access List tab, click + ADD IP ADDRESS.
-
In the Add IP Access List Entry pop-up window, Access List Entry field, specify the Hevo IP address you want to whitelist.
Note: To provide access to all IPs, specify 0.0.0.0.
-
Click Confirm.
Retrieve Database Settings
Perform the following steps to retrieve your MongoDB Atlas database settings:
-
Log in to the MongoDB Atlas console.
-
In the drop-down on the top left corner of the page, select the project for which you want to replicate the data.
-
In the Overview page, Database Deployments section, click CONNECT.
-
In the Connect to <Cluster Name> pop-up window, under Access your data through tools, click Compass.
-
In the Connecting with MongoDB Compass section, do the following:
-
Click I have MongoDB Compass Installed. Note: Select this option even if you do not have MongoDB Compass. You do not need MongoDB Compass to configure MongoDB Atlas as a Source in Hevo.
-
Select the version of the compass:
-
If your MongoDB version is 3.6 or later, select 1.12 or later.
-
If your MongoDB version is earlier than 3.6, select 1.11 or earlier.
-
-
-
Copy the connection string that appears in the code block. The connection string varies as per the Compass version you select.
Note: Replace the
<username>
and<password>
in the connection string above with your database username and password. For example, in the following connection string for MongoDB Compass version 1.11 or earlier, theusername
is replaced with jerome and thepassword
with Hevo123:mongodb://jerome:Hevo123@cluster0-shard-00-00.t7l5k.mongodb.net:27017,cluster0-shard-00-01.t7l5k.mongodb.net:27017,cluster0-shard-00-02.t7l5k.mongodb.net:27017/test?replicaSet=atlas-uax6f3-shard-0&ssl=true&authSource=admin
-
Refer to section, Configure MongoDB Atlas Connection Settings for the steps to configure the Source in Hevo.
Configure MongoDB Atlas Connection Settings
Perform the following steps to configure MongoDB Atlas as a Source in Hevo:
-
Click PIPELINES in the Navigation Bar.
-
Click + CREATE PIPELINE in the Pipelines List View.
-
In the Select Source Type page, select MongoDB Atlas.
-
In the Configure your MongoDB Atlas Source page, specify the following:
-
Pipeline Name: A unique name for the Pipeline, not exceeding 255 characters.
-
General Connection Settings:
-
Paste Connection String:
-
Connection URI: The unique identifier for connecting to a MongoDB replica set or a sharded cluster.
Note: If you are connecting to a sharded cluster, Hevo automatically extracts all the shards of the cluster.
-
-
Enter Connection Fields Manually:
-
Database Host: The MongoDB DNS name fetched from your MongoDB Atlas account.
Note: To connect to a sharded cluster, specify only the parent cluster name. For example, if your host is the sharded cluster, cluster0-shard-00-00.t7l5k.mongodb.net, cluster0-shard-00-01.t7l5k.mongodb.net, cluster0-shard-00-02.t7l5k.mongodb.net, the parent hostname would be cluster0.t7l5k.mongodb.net. Hevo automatically extracts all the shards of the cluster.
-
Database User: The authenticated user who has permission to read collections in your database. Read Setting up Permissions to Read MongoDB Atlas Databases
Note: It is recommended that only the
read-only
permission be provided to the user. -
Database Password: The password for the database user.
-
-
-
Select an Ingestion Mode: The desired mode by which you want to ingest data from the Source. You can expand this section by clicking SEE MORE to view the list of ingestion modes to choose from. Default value: OpLog.
The following ingestion modes are applicable to MongoDB Source:
Note: If you are connecting to a sharded cluster, select Change Streams as the ingestion mode.
-
OpLog: Data is ingested using MongoDB’s OpLog. The OpLog contains individual, transaction-level details which helps replicas sync data from the primary instance.
Note: OpLogs are present in data or standalone primary instances and replicas.
-
Change Streams: MongoDB’s Change Streams enables applications to stream real-time data changes without the complexity and risk of tailing the OpLog, for a single collection, a database, or an entire deployment. Change Streams are supported for all MongoDB configurations. However, for the clustered configuration, Change Streams works only if set up against a shard router (mongos).
By default, in both Change Streams and OpLog modes, the data is read at the mongo instance level. To read data at the database level in Change Streams mode, disable the Load All Databases option while creating the Pipeline.
-
-
Connection Settings:
-
Connect through SSH: Enable this option to connect to Hevo using an SSH tunnel, instead of directly connecting your MongoDB Atlas database host to Hevo. This provides an additional level of security by not exposing your MongoDB setup to the public. Read Connecting Through SSH.
If this option is disabled, you must whitelist Hevo’s IP addresses to allow Hevo to connect to your MongoDB host.
-
-
Advanced Settings:
-
Load All Databases: If enabled, Hevo fetches data from all the databases you have access to on the specified database host(s). Ensure that you have assigned the
readAnyDatabase
role or thelistDatabases
action on theadmin
database. Refer to Step 5 of section, Create a custom role above.If disabled, Hevo fetches the list of all the databases you have access to on the specified database host(s). From this list, you must select the databases you want to fetch data from.
Warning! Once the Pipeline is created, if you drop any of these databases from your MongoDB Source, the Pipeline will fail.
-
Merge Collections: If enabled, collections with the same name across different databases are merged into a single Destination table. If disabled, separate tables are created and prefixed with the respective database name. Read Example - Merge Collections Feature.
-
Load Historical Data: If disabled, Hevo loads data written in your database after the time of creation of the Pipeline. If enabled, the entire table data is fetched during the first run of the Pipeline.
-
Include New Tables in the Pipeline:
If enabled, Hevo automatically ingests data from tables created in the Source after the Pipeline has been built. These may include completely new tables or previously deleted tables that have been re-created in the Source.
If disabled, new and re-created tables are not ingested automatically. They are added in SKIPPED state in the objects list, in the Pipeline Overview page. You can update their status to INCLUDED to ingest data.
You can change this setting later.
-
-
-
Click TEST CONNECTION. This button is enabled once you specify all the mandatory fields. Hevo’s underlying connectivity checker validates the connection settings you provide.
-
Click TEST & CONTINUE to proceed for setting up the Destination. This button is enabled once you specify all the mandatory fields.
Data Replication
For Teams Created | Default Ingestion Frequency | Minimum Ingestion Frequency | Maximum Ingestion Frequency | Custom Frequency Range (in Hrs) |
---|---|---|---|---|
Before Release 2.21 | 5 Mins | 5 Mins | 1 Hr | NA |
After Release 2.21 | 30 Mins | 30 Mins | 12 Hrs | 1-24 |
Note: The custom frequency must be set in hours as an integer value. For example, 1, 2, or 3 but not 1.5 or 1.75.
-
Historical Data: In the first run of the Pipeline, Hevo ingests all available data for the selected objects from your Source database.
-
Incremental Data: Once the historical load is complete, data is ingested as per the ingestion frequency.
Additional Information
Read the detailed Hevo documentation for the following related topics:
Source Considerations
- MongoDB does not allow data ingestion from the OpLog in sharded clusters. As a result, Hevo cannot support OpLog as the ingestion mode when connecting to such clusters. Hence, you must select the Change Streams mode while configuring your Pipeline.
Limitations
- Hevo does not support configuring a standalone instance of MongoDB without a replica.
See Also
Revision History
Refer to the following table for the list of key updates made to this page:
Date | Release | Description of Change |
---|---|---|
Oct-09-2024 | NA | Updated the Prerequisites section to reflect that Hevo only supports MongoDB version 3.4 and higher. |
Apr-29-2024 | NA | Updated section, Configure MongoDB Atlas Connection Settings to include more detailed steps. |
Mar-05-2024 | 2.21 | - Added the Data Replication and Source Considerations sections. - Updated the Configure MongoDB Atlas Connection Settings section to add information about selecting Change Streams as the ingestion mode for sharded clusters. |
Sep-04-2023 | NA | Updated the page as per the latest MongoDB UI. |
Mar-16-2023 | NA | Added a warning in the Advance Settings in section, Configure MongoDB Atlas Connection Settings about dropping databases from the Source after the Pipeline is created. |
Mar-09-2023 | 2.09 | Updated section, Configure MongoDB Atlas Connection Settings to mention about SEE MORE in the Select an Ingestion Mode section. |
Dec-19-2022 | 2.04 | Updated section, Configure MongoDB Atlas Connection Settings to add information that you must specify all fields to create a Pipeline. |
Dec-07-2022 | 2.03 | Updated section, Configure MongoDB Atlas Connection Settings to mention about the connectivity checker. |
Jul-12-2022 | 1.92 | Updated section, Configure MongoDB Atlas Connection Settings to include information about the drop-down to select databases in the Load All Databases option. |
Apr-21-2022 | 1.86 | Updated section, Configure MongoDB Atlas Connection Settings. |
Jan-03-2022 | 1.79 | Updated the description of the Include New Tables in the Pipeline advance setting in the Configure MongoDB Atlas Connection Settings section. |
Jul-12-2021 | 1.67 | Added the field Include New Tables in the Pipeline under Source configuration settings. |
Jun-28-2021 | 1.66 | - Updated the page overview section. - Updated the section Retrieve Database Settings to include latest steps. - Updated the section Set up Permissions to Read MongoDB Atlas Databases to include latest steps. - Updated the section Configure MongoDB Atlas Connection Settings to include the option to connect to the MongoDB Atlas database using connection string. - Added section, Limitations. |