MongoDB - Find

MongoDB - Find

On this Page

Snap type:

Read


Description:

This Snap executes a MongoDB find command and outputs the results as documents.


Prerequisites:

[None]


Support and limitations:

Works in Ultra Tasks.


Account: 

This Snap uses account references created on the Accounts page of SnapLogic Manager to handle access to this endpoint. See MongoDB Account for information on setting up this type of account.


Views:
InputThis Snap has at most one document input view. If the input view is defined, then values will be used to evaluate the expression in the query condition.
OutputThis Snap has exactly one document output view.
ErrorThis Snap has at most one document error view and produces zero or more documents in the view.

Settings

Label


Required. The name for the Snap. You can modify this to be more specific, especially if you have more than one of the same Snap in your pipeline.
Database name

The database that the collection is defined in. If not specified, then the MongoDB account database will be used.

Default value: None
Example: assets


Collection name



Required. The MongoDB collection name to execute the find on.

Default value: None
Exampleusers

Query Condition


The query condition represents the find query parameter. It is an expression that evaluates to an object or JSON string. If no query condition is defined, then all records of the collection will be retrieved. When the expression evaluates to an object, only strict mode is supported. When the expression evaluates to a JSON string, both strict mode and mongo shell mode are supported. More information about MongoDB Extended JSON can be found here.

Example(with '=' button pressed/expression enabled) 

$id represents an integer in this example.

{"id": {$lte: $id}}

 or

'{"id": {$lte:' + $id + '}}'

To support date/time strings and to correctly parse dates, the current version of the MongoDB requires a timezone.

Example: 2013-08-29T17:56:44.161<Z>, where "Z" is the time offset.

Default value: [None]

Projection Condition

Specifies which fields must be returned in the matching documents. You can include or exclude fields. You can use the following values:

  • 1 or true to include the field
  • 0 or false to exclude the field

Default value: N/A

Example{age:0, status:0}

A Projection Condition cannot contain both include and exclude specifications.

Sort Condition

Orders the documents in the result set. To use multiple sort orders, enter comma-separated sort conditions.

Default value: N/A
Example{age: = -1}

Batch Size


Required. This property limits the number of documents returned in a batch. More can be read here. 
The definition of this property is different from the same property in other DB Snaps.
Assume Batch size is n,

  • if n > 1, get all documents in the collection that match (returns n documents at a time, or as many that can fit in the batch buffer)
  • if n = 1, get only one document in the collection that matches
  • if n = 0, get all documents in the collection that match (returns as many documents that can fit in the batch buffer at a time)
  • if n < 0, get n documents in the collection that match (e.g. if n = -10, get only 10 documents that match)

In MongoDB 3.4, the batch buffer size is 16MB. In previous versions, the batch buffer size is 4MB. The initial batch will always return a maximum of 101 documents. More can be read here.

Default value0
Example: 0

Offset

The starting document for the query. The result set starts from this document.

Default value: N/A
Example: 100

Limit

The number of documents the query must return.

Default value: N/A
Example: 20

Timezone Offset

Hours Offset


The hours to offset for timezone. MongoDB returns dates in UTC timezone. If another timezone is desired, then an hours offset can be used. If a negative value is used for the hours, then the timezone offset will be in the format -7:00.

Default value0
Example:  -7

Minutes Offset


The minutes to use for the time zone offset in the date returned by MongoDB.

Default value0
Example: 1

Group result

Select to group the output result in a single array.

When Group result is checked, the documents will now be grouped inside an array instead of individual documents.

Default value: Deselected

Pass through

If selected, the input document will be passed through to the output view under the key 'original'.

Default value: Selected

Number of retries

Specify the maximum number of attempts to be made to receive a response. The request is terminated if the attempts do not result in a response.

  • If the Number of retries value is set to 0 (the default value), the retry option is disabled, and the Snap does not initiate a retry. The pipeline will not attempt to retry the operation in case of a failure—any failure encountered during the database operation will immediately result in the pipeline failing without any retry attempts to recover from the errors.

  • If the Snap fails on all retries, it routes the last occurred exception to the error view.

Default Value0

Example: 4

Retry interval (seconds)

Specify the time interval between two retry requests.

Default Value: 1
Example: 5

Ignore empty result

If selected, no document will be written to the output view when the FIND operation does not produce any result. If this property is not selected and the Pass through property is selected, the input document will be passed through to the output view.

Default value: Deselected

Snap Execution

Select one of the following three modes in which the Snap executes:

  • Validate & Execute: Performs limited execution of the Snap, and generates a data preview during Pipeline validation. Subsequently, performs full execution of the Snap (unlimited records) during Pipeline runtime.

  • Execute only: Performs full execution of the Snap during Pipeline execution without generating preview data.

  • Disabled: Disables the Snap and all Snaps that are downstream from it.

Default value: Validate & Execute
Example: Execute only

Troubleshooting

Running queries using a UUID

The current version of the MongoDB driver for Java does not correctly handle queries with UUIDs and as a result, such queries fail. However, you can use the latest version of the MongoDB driver and pass queries with UUIDs. 

To run a query using UUIDs, perform the following:

  1. As the current MongoDB JAR does not support UUIDs in a query, you must use the latest version of the MongoDB driver. Navigate to your MongoDB account settings and select the latest available JAR:
  2. The new versions of the MongoDB driver do not support date/time strings without timezones. To correctly parse dates, enter a timezone in the Snap Time Zone Offset settings. For example, 2013-08-29T17:56:44.161<Z>, where "Z" is the time offset.
  3. Enter the following query in the Query Condition field of the Snap settings:

    "{\"user_id\": new BinData(3,\""+ Base64.encode(Uint8Array.of(...$user_id.replaceAll('-', '').match(/(\w\w)/g).map(x => parseInt(x, 16)))) + "\")}"

Example


In this example, we shall search the documents from a collection using the MongoDB Snap and write them to a binary input view using the JSON Formatter Snap and the File Writer Snap respectively.

The MongoDB Find Snap searches the documents from the Collection Name, mongotable with the Query Condition as '{num:1}' and a default Batch Size 0. This will retrieve all the documents satisfying the query conditions.

Below is the output preview from the MongoDB Find Snap retrieving all the documents:

 

We shall write the documents to a binary output view using the JSON Formatter and File Writer Snaps respectively.

Successful Execution of the pipeline displays the below output preview:

Snap Pack History

 Click to view/expand

Release 

Snap Pack Version

Date

Type

  Updates

November 2025

main33142

Stable

Updated and certified against the current SnapLogic Platform release.

Aug 2025

main32088

13 Aug 2025

Stable

Enhanced the MongoDB Account and MongoDB Dynamic Account to support MongoDB SRV connection strings to ensure compatibility with MongoDB Atlas.

May 2025

main31019

 

Stable

Fixed an issue with the Mongo DB Execute Snap where the queries did not get executed on secondary nodes when the Read preference was set to Secondary preferred or Secondary.

Behavior change

Previously, when you used the Write command in the MongoDB Execute Snap, the Snap was executed at the Primary node by default, regardless of the Read preference configuration. With the main31019 Snap Pack version, when you use the Write command in the MongoDB Execute Snap, it does not execute the command and displays an error depending on the Read preference set in the account. When the Read preference is:

    • Secondary: It always displays an error.

    • Secondary preferred: It most likely displays an error.

    • Nearest: It might error out depending on the network latency between the client and the MongoDB server.

    • Primary preferred and Primary: Has lower chances of error.

February 2025

440patches29949

 

Latest

Upgraded the Spring Framework version to 5.3.39.

February 2025

main29887

 

Stable

Updated and certified against the current SnapLogic Platform release.

November 2024

main29029

 

Stable

Enhanced the MongoDB Replica and Mongo ReplicaSet Dynamic Accounts to define read preference options when querying data. The default option is Primary, so you cannot allocate read load to the secondary node. Note that the Secondary preferred mode is not supported for the MongoDB Execute Snap.

August 2024

main27765

 

Stable

Updated and certified against the current SnapLogic Platform release.

May 2024

437patches27343

 

Latest

The MongoDB - Atlas Vector Search Snap now supports the following:

  • Suggestions for the Search index field that enables the Snap to populate the associated indices in the list.

  • The input schema displays the mandatory vector field and optional filter suggestion (if the Search index contains a filter type query) in alignment with the fields expected by the Snap.

May 2024

437patches26832

 

Latest

  • Fixed the inconsistency in ObjectId and Date representation in the output preview between MongoDB - Execute and MongoDB - Find snaps.

  • Enhanced the MongoDB Execute Snap with the Timezone Offset field set that enables you to apply the timezone offset on the date fields.

May 2024

437patches26721

 

Latest

  • Added Number of retries and Retry interval (seconds) fields, to MongoDB Delete, Update, Find, Group, Insert, and Atlas Vector Search Snaps that enable you to handle retries during a connection failure.

  • Fixed an issue with the MongoDB - Execute Snap, where data was missing when the database server restarted and the error view was enabled.

  • Fixed an issue with the MongoDB - Execute Snap where the log file missed the retry attempts information.

May 2024

main26341

 

Stable

  • Enhanced the MongoDB Update Snap with the Array Filters field, which enables you to use array filters in the update operation. Additionally, the Update Query field is modified into a text box for visibility and usability of input queries.

  • Upgraded Spring dependencies to the latest supported Java 11 version for MongoDB Snap Pack.

February 2024

436patches26244

 

Latest

Added the following Snap to the MongoDB Snap Pack:

  • MongoDB - Atlas Vector Search: Performs advanced vector-based queries, such as Similarity searches, Approximate Nearest Neighbor (ANN) queries, and Range queries on vector data stored in MongoDB Atlas.

February 2024

436patches25893

 

Latest

Added MongoDB Execute Snap to the MongoDB Snap Pack.

February 2024

main25112

 

Stable

Updated and certified against the current SnapLogic Platform release.

November 2023

main23721

 

Stable

Updated and certified against the current SnapLogic Platform release.

August 2023

main22460

 


Stable

Updated and certified against the current SnapLogic Platform release.

May 2023

main21015

 

Stable

Upgraded with the latest SnapLogic Platform release.

February 2023

main19844

 

Stable

Upgraded with the latest SnapLogic Platform release.

November 2022

main18944

 

Stable

Upgraded with the latest SnapLogic Platform release.

September 2022

430patches18223

 

Latest

The MongoDB Update Snap in a low-latency feed Ultra Pipeline now correctly acknowledges the requests.

August 2022

430patches17472

 

Latest

The MongoDB Account with Encryption type set to TLS/SSL does not fail with the "URL cannot be null" error.

August 2022

main17386

 

Stable

Upgraded with the latest SnapLogic Platform release.

4.29Patches

429patches15807

 

Latest

Updated the expected output for the MongoDB - Update Snap that is changed because of the upgrade of Spring Core framework version.

4.29

main15993

  

Stable

Upgraded with the latest SnapLogic Platform release.

4.28

main14627

 

Stable

Upgraded with the latest SnapLogic Platform release.

4.27

main12833

 

Stable

Upgraded with the latest SnapLogic Platform release.

4.26

main11181

 

Stable

Upgraded with the latest SnapLogic Platform release.

4.25

main9554

 

Stable

Upgraded with the latest SnapLogic Platform release.

4.24

main8556

Stable

Fixed an issue in the MongoDB accounts to connect to Atlas Free Tier and Shared Cluster database using the Use cursor timeout checkbox in the MongoDB cursor properties. If selected, this option enables the server to close a cursor automatically after a period of inactivity. For the existing accounts that does not have this field, the value for this checkbox returns false, which is backward compatible.

4.23

main7430

 

Stable

Upgraded with the latest SnapLogic Platform release.

4.22

main6403

 

Stable

Upgraded with the latest SnapLogic Platform release.

4.21 Patch

421patches6272

 

Latest

Fixes the issue where /wiki/spaces/AP/pages/615284852 Snap generates two output documents despite no changes to Cause-historization fields with DATE, TIME and TIMESTAMP Snowflake data types, and with Ignore unchanged rows field selected.

4.21 Patch

421patches6144

 

Latest

Fixes the following issues with DB Snaps:

  • The connection thread waits indefinitely causing the subsequent connection requests to become unresponsive.

  • Connection leaks occur during Pipeline execution.

4.21 Patch

MULTIPLE8841

 

Latest

Fixes the connection issue in Database Snaps by detecting and closing open connections after the Snap execution ends. 

4.21

snapsmrc542

 

Stable

Upgraded with the latest SnapLogic Platform release.

4.20

snapsmrc535

 

Stable

Upgraded with the latest SnapLogic Platform release.

4.19

snaprsmrc528

 

Stable

Upgraded with the latest SnapLogic Platform release.

4.18

snapsmrc523

 

Stable

  • Added the following fields to the Mongo DB Find Snap: Projection Condition, Sort ConditionOffset, Limit, and Group result.

  • Added a new Snap, MongoDB Group, which enables you to group input documents by a specified expression, and output to the next stage, one document for each distinct grouping.

  • Added a new field to the Mongo DB Update Snap, Update operation and Exclude list, which enable you to update operations and exclude a list of JSON properties before sending the updated documents to MongoDB.

4.17

ALL7402

 

Latest

Pushed automatic rebuild of the latest version of each Snap Pack to SnapLogic UAT and Elastic servers.

4.17 Patch

 db/mongo7331

 

Latest

  • Fixed an issue with the MongoDB - Update Snap wherein the Snap converts all non-updated integer and float data types to string data type.

  • Fixed a Null Pointer Exception for old MongoDB accounts that did not have driver jars.

4.17

snapsmrc515

 

Latest

Added the Snap Execution field to all Standard-mode Snaps. In some Snaps, this field replaces the existing Execute during preview check box.

4.16

snapsmrc508

 

Stable

Upgraded with the latest SnapLogic Platform release.

4.15 Patch 

db/mongo6783

 

Latest

Fixed connection timeout issue with MongoDB.

4.15 Patch 

db/mongo6465

 

Latest

Fixed an issue wherein REST calls to Ultra tasks returned an error message.

4.15

snapsmrc500

 

Stable

Upgraded with the latest SnapLogic Platform release.

4.14 Patch 

db/mongo5666

 

Latest

Fixed the Update, Delete, and Find Snaps to populate input view schema for a given table, similar to the Insert Snap.

4.14

snapsmrc490

 

Stable

Upgraded with the latest SnapLogic Platform release.

4.13 Patch

mongo5537

 

Latest

Fixed the Update, Delete, and Find Snaps to populate input view schema for a given table, similar to the Insert Snap.

4.13

snapsmrc486

 

Stable

Upgraded with the latest SnapLogic Platform release.

4.12

snapsmrc480

 

Stable

Added the SSl certification properties to all the MongoDB Accounts to ensure the validation of the certificate.

4.11

snapsmrc465

 

Stable

Upgraded with the latest SnapLogic Platform release.

4.10 Patch

mongo3978

 

Latest

Resolved an issue where the NumberFormatException was not handled properly for some of the valid Number Types like "NaN"/ "+Infinity"/ "-Infinity".


4.10

snapsmrc414

 

Stable

Upgraded with the latest SnapLogic Platform release.

4.9.0 Patch

mongodb3259

 

Latest

  • Addressed an issue in MongoDB Update where Upsert Date failed with "Can't find a codec for class org.joda.time".

  • MongoDB Insert Snap - Collectio name expression evaluate fixed.

4.9

snapsmrc405

 

Stable

  • Query Condition property is now an expression that evaluates to an object or JSON string.

  • Updated the Snap with Database name property to support the users defined in an authentication database.

4.8.0 Patch

mongodb2735

 

Latest

Added SSL encryption type to all MongoDB accounts and Replica set Accounts and removed the MongoDB SSL account.

4.8

snapsmrc398

 

Stable

  • The MongoDB Delete Snap and MongoDB Update Snap were introduced in this release.

  • Enhanced the MongoDB Snap account with SSL Account type.

  • Updated the Batch Size property in MongoDB Find with the default value of 0.

  • Enhanced the MongoDB Find Snap documentation with an example.

  • Info tab added to accounts.

  • Database accounts now invalidate connection pools if account properties are modified and login attempts fail.

4.7 Patch

mongo2375

 

Latest

  • Update the MongoDB java driver to 3.0.4; Add exception handling to each record processing.

  • MongoDB SSL Account removed and replaced with the new configuration for all the Accounts (Encryption type Property).

4.7 Patch

mongo2338

 

Latest

Add an account for MongoDB SSL connection without certificates validation

4.7 Patch

mongo2200

 

Latest

Fixed an issue for database Select Snaps regarding Limit rows not supporting an empty string from a pipeline parameter.

4.7

snapsmrc382

 

Stable

Updated the Snap account with the LDAP Authentication type.

4.6

snapsmrc362

 

Stable

Resolved an issue in MongoDB Insert Snap that processed and inserted all numeric fields as strings.

4.5.1

snapsmrc344

 

Stable

  • Resolved and issue with MongoDB Insert with an empty input view failed.

  • Resolved an issue with MongoDB Insert that changed a numeric type field in MongoDB as String.

  • Resolved an issue that caused Snap execution failures when accessing MongoDB using a Replica Set account.

4.3.2


 

Stable

Resolved an issue with MongoDB Find returning nothing when nothing was found.


4.3



Stable

  • Resolved an issue with an incorrect resolution displaying during account validation if the username was blank.

  • Resolved an issue in the MongoDB Find Snap with nested arrays.

  • Resolved an issue in MongoDB Find with data not being usable be other Snaps.

4.2.2



Stable

  • Username and Password are no longer required fields when creating a MongoDB account because it is possible to configure an instance where that information is not required.

  • MongoDB Aaccount now supports Mongo Java Driver 3.0.2.

  • MongoDB Find

    • Resolved an issue with MongoDB Find not properly supporting the expression language.

    • Resolved an issue with MongoDB Find returning "Current context not an ARRAY but OBJECT" for a deep nested ObjectId object.

    • Resolved an issue with MongoDB Find when data had built-in datatype.

    • Resolved a null pointer exception in MongoDB Find.

    • Resolved an issue with MongoDB Find not routing failed documents to the error view.

  • Resolved an issue with MongoDB error handling when maximum number of documents reached.

  • Improved the error message presented when MongoDB database could not reach the JCC.

4.2.1



Stable

  • MongoDB - Find: Resolved Error- Failure: java.util.HashMap cannot be cast to java.lang.String when in query condition passes without single quotes.

  • MongoDB - Find: Resolved failure with Query Using Operators.

  • Resolved MongoDB driver and account do not support current version of MongoDB.

  • Resolved a failure MongoDB Insert with custom _id.