In this Article

Table of Contents

maxLevel	2
absoluteUrl	true

Overview

Use this Snap to consolidate multiple input streams into a single output document, where each input stream is displayed as a label containing the records that were received by that input view.

It is also important to note that this Snap does not complete executing until the execution of all upstream Snaps is done.

Image RemovedImage Added650

Prerequisites

Because this This Snap collects multiple input documents into a single output document, ; hence there are system memory limitations, and this Snap it should not be used for massive data propagation. If large amounts of data are required, offload your data prior to before Snap execution. Instead, You can also write your data to a file or database; then, after Snap execution completes, you can use a Reader Snap (File Reader, S3 Reader, and so on) to read from the offloaded data source.

...

This Snap does not have error views. If the Snap fails during validation or execution, documents are not passed through, and you receive an error message.
Ultra pipelines: Not supported in

Support for Ultra Pipelines

Does not support Ultra Pipelines.

...

N/A

Snap Input and Output

...

Snap Views

Type

Format

Number of Views

Examples of Compatible Upstream and Downstream Snaps

Description

Input

Document

Min: 1
Max: ∞

Mapper
JSON Parser
Join

One or more documents containing records that must be passed on to downstream Snaps for further processing.

Output

Document

Min: 1
Max: 1

Copy
Join
Common Words

A single document that contains all the records received from the various upstream Snaps.

Error

Error handling is a generic way to handle errors without losing data or failing the Snap execution. You can handle the errors that the Snap might encounter when running the pipeline by choosing one of the following options from the When errors occur list under the Views tab:

Stop Pipeline Execution: Stops the current pipeline execution if the Snap encounters an error.
Discard Error Data and Continue: Ignores the error, discards that record, and continues with the remaining records.
Route Error Data to Error View: Routes the error data to an error view without stopping the Snap execution.

Learn more about Error handling in Pipelines.

Snap Settings

...

Info
Asterisk ( * ): Indicates a mandatory field.
Suggestion icon (Image Added): Indicates a list that is dynamically populated based on the configuration.
Expression icon (Image Added ): Indicates the value is an expression (if enabled) or a static value (if disabled). Learn more about Using Expressions in SnapLogic.
Add icon ( Image Added ): Indicates that you can add fields in the field set.
Remove icon ( Image Added): Indicates that you can remove fields from the field set.
Upload icon (Image Added ): Indicates that you can upload files.

Field Name Field Type Description
Label*

Default Value: Gate
Example: Ensure Complete Execution
String 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.
N/AEnsure Complete Execution
Snap Execution
String
Ignore Empty Stream

Default Value: Deselected
Example: Ensure Complete Execution
Checkbox
Select this checkbox if you do not want this Snap to produce any output document.
When you deselect this checkbox, the Snap writes an empty document to the output view.
Output Document Content*

Default Value: All input documents
Example: Document count and first document for each input
Dropdown list
Choose one of the following options to determine the content of the output document:
All inputs documents
Document count and first document for each input:
Document count and final document for each input

Snap Execution

Default Value: Validate & Execute
Example: Execute only
Dropdown list
Specifies the execution type:
Validate & Execute: Performs limited execution of the Snap (up to 50 records) during Pipeline validation; performs full execution of the Snap (unlimited records) during Pipeline execution.
Execute only: Performs full execution of the Snap during Pipeline execution; does not execute the Snap during Pipeline validation.
Disabled: Disables the Snap and, by extension, its downstream Snaps.
Validate & ExecuteN/A

Examples

Combining Completed Upstream Execution Output Using the Gate Snap

This example demonstrates how you can use the Gate Snap to combine the complete output of multiple upstream Snaps into a single document. This example also shows how the Gate Snap doesn't offer any output until all upstream Snaps have completed executingare executed.

Download this Pipeline

Understanding the Pipeline

You add a Configure the File Reader Snap to the Pipeline pipeline and configure it to read a CSV file containing contact information:
You add Configure a CSV Parser Snap to read the input binary data as CSV. Once this Snap executes, you can view the contents of the file that the File Reader Snap read:
You create a separate branch of the Pipeline by adding an unconnected REST Get Snap. You configure the Snap to retrieve contact data from HubSpot, which typically offers data in pages of 20 records each. You use the Has next and Next URL fields to specify how the Snap can retrieve additional pages of data. For step-by-step information on how to use the REST Get Snap to perform this task, see Retrieving Contact Information from HubSpot.

The REST Get Snap retrieves the data in pages of 20 as requested until the value of the has-more variable changes to false:
Info
Note that until the REST Snap completes executing, the Gate Snap doesn't start reading data from any of its input views.
You create another branch of the Pipeline by adding a JSON Generator Snap that provides customer information:
You add a Gate Snap and configure it to have three input views:

You make
Make no further changes to the Gate Snap and connect its three inputs to each of the branches branch you created in the steps above.
You save Save and run the Pipeline. The Gate Snap now collects the completed inputs from all upstream branches and offers them all as separate arrays in a single output document:
To check how the Gate Snap behaves when one of the Snaps does not offer any output, you introduce an error into the REST Get Snap:
You now save Save and re-execute the Pipeline. The Gate Snap now offers an output which that contains all the data received from the File Reader and JSON Generator branches; , but in the output associated with the REST Get Snap, it outputs a null record: