In this Article
Use this Snap to consolidate multiple input streams into a single output document, where each input stream is displayed as a 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.
650
This Snap collects multiple input documents into a single output document; hence there are system memory limitations, and it should not be used for massive data propagation. If large amounts of data are required, offload your data before Snap execution. 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.
Does not support Ultra Pipelines.
Type | Format | Number of Views | Examples of Compatible Upstream and Downstream Snaps | Description |
---|---|---|---|---|
Input | Document |
|
| One or more documents containing records that must be passed on to downstream Snaps for further processing. |
Output | Document |
|
| 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:
Learn more about Error handling in Pipelines. |
|
Field Name | Field Type | Description |
---|---|---|
Label*
| 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. |
Ignore Empty Stream Default Value: Deselected | 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 | Dropdown list | Choose one of the following options to determine the content of the output document:
|
Snap Execution
| Dropdown list | Select one of the following three modes in which the Snap executes:
|
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 are executed.
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:
Note that until the REST Snap completes executing, the Gate Snap doesn't start reading data from any of its input views. |