You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 4
Next »
In this article
Overview
You can use this Snap to copy a binary stream to the Snap’s output views. Use this Snap if you want to send the same information to multiple endpoints.
Prerequisites
None.
Support for Ultra Pipelines
Works in Ultra Pipelines.
Limitations and Known Issues
None.
Input/Output | Type of View | Number of Views | Examples of Upstream and Downstream Snaps | Description |
---|
Input | Binary | | File Reader S3 File Reader Zip File Read
| |
Output | Binary | | | |
Snap Settings
Field Name | Field Dependency | Description |
---|
Label* | None. | 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. Default Value: Binary Copy Example: Copy Binary Data |
Snap Execution | None. | Select one of the three modes in which the Snap executes. Available options are: 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 |
Examples
Download this Pipeline.
Downloads
Click here to expand...
4.25 (main9554)
4.24 (main8556)
4.23 (main7430)
Introduces a new Snap, HTTP Router Snap, that enables API developers to route multiple HTTP requests appropriately based on the request method (GET, PUT, PATCH, etc.) when executing Pipelines as Triggered Tasks.
Fixed the Head Snap issue by closing the output view after writing the last output document so that downstream snaps can complete, even while the Head Snap continues to consume any available input.
4.22 (422patches6648)
4.22 (main6403)
4.21 Patch flow8855
4.21 (snapsmrc542)
4.20 (snapsmrc535)
Adds a new Snap, Gate, which enables you to consolidate multiple input streams into a single output document where each input stream is displayed as a label containing the list of records that were received by that input view.
The Pipeline Execute Snap now provides the following capabilities:
Specify the Snaplex on which to run child Pipelines. You can now select the Snaplex on which to run the child Pipelines through the Execute On and Snaplex Path fields. The default option is executing the child Pipeline on the same Snaplex node as the Parent, but you can also specify a different Snaplex through the drop-down list, which includes the option to manually enter a Snaplex name.
Configure retry logic for child Pipeline executions. You can now configure retry logic for child Pipeline executions though the following fields: Number of Retries, Retry Interval, and Timeout fields.
4.19 (snaprsmrc528)
4.18 Patch flow7743
4.18 (snapsmrc523)
4.17 Patch flow7637
4.17 Patch ALL7402
4.17 (snapsmrc515)
4.16 (snapsmrc508)
4.15 Patch flow6263
4.15 (snapsmrc500)
4.14 (snapsmrc490)
4.13 (snapsmrc486)
4.12 Patch flow4895
4.12 (snapsmrc480)
4.11 Patch flow4461
4.11 Patch flow4292
4.11 [snapsmrc465]
4.10 (snapsmrc414)
4.9.0 Patch flow3320
4.9.0 Patch flow3094
4.9 (snapsmrc405)
4.8.0 (snapsmrc398)
4.7.0 Patch flow2598
4.7.0 Patch flow2297
4.7.0 (snapsmrc382)
Recommendation: The Pipeline Execute Snap is meant to eventually replace ForEach and Task Execute. It is suggested you use Pipeline Execute for all new pipelines and update existing pipelines at your earliest convenience.
Updated the Pipeline Execute Snap with Execute during preview field.
4.6.0 Patch flow1909
4.6.0 (snapsmrc362)
The following Snaps now support error view in Spark mode: Copy, Union.
ForEach: The value for the Maximum instances property is limited to a maximum of 100. A value higher than 100 will automatically be limited down to 100 during pipeline execution.
Pipeline Execute: Snaplex property added to let you specify the Snaplex on which to run the child pipeline.
Resolved an issue in Task Execute Snap that caused an internal server error (status code: 500).
Resolved an issue in Pipeline Execute Snap that did not show parameter suggestions when the pipeline is selected from another project.
Resolved an issue in Copy Snap that showed errors on the UI while the Javascript was being executed.
Resolved an issue in Filter Snap that failed with "could not filter the document" if upstream data for ServiceNow Query.
4.5.1 (flow1574)
Resolved an issue with Pipeline Execute not able to load pipeline selected from the pipeline picker property.
Enhanced error handling in Pipeline Execute for when Reuse is enabled and the pipeline path is an expression whose result is not constant.
Resolved an issue in Pipeline Execute not including the runtime ID and state in error documents.
4.5.0 (snapsmrc344)
NEW! Pipeline Execute introduced in this release. This Snap provides a way to flexibly and efficiently execute pipelines and flowing documents into and out of these executions.
Resolved an issue in Task Execute Snap to ensure JAVA 7 and JAVA 8 Snaplex give the same output.
Resolved an issue with the Router Snap routing to the wrong output when used in Spark mode.
4.4.0
Resolved an issue with Exit Snap hanging during validation if threshold is not met.
Spark support added to the Copy, Filter, Router, and Union Snaps.
4.3.2
Resolved an issue with Task Execute where java.math.BigInteger cannot be cast to java.lang.String exception if input document variable was a numeric type.
Resolved an issue with Task Execute failing with expression enabled.
Resolved an issue with data preview not working in the ForEach Snap.
Resolved an issue with Execute during Preview functionality broken in the ForEach Snap.
Resolved an issue with ForEach Snap not representing the output schema correctly during preview.
4.3.1
4.3.0
In Data Validator, the pattern option now works with partial matches.
Exit Snap
ForEach Snap now generates output documents when run. Output documents will also be produced if a child pipeline called by the ForEach is manually stopped.
4.2.2
August 7, 2015 (2015.25/4.2.1)
NEW! Exit Snap introduced in this release. This Snap forces a pipeline to stop with a failed status if it receives more records than the user-defined threshold.
Resolved error in ForEach Snap where an exposed error view triggered a pipeline failure.
June 27, 2015 (2015.22)
June 6, 2015 (2015.20)
May 15, 2015
May 2, 2015
December 20, 2014
Updated Snaps may include new or changed functionality or be otherwise improved.
July/Summer 2014
June 30, 2014
April 2014
January 2014
November 2013
Initial Release (June 2013)
Router Snap introduced in this release.
Copy Snap introduced in this release.
Union Snap introduced in this release.
Filter Snap introduced in this release.
See Also
https://docs-snaplogic.atlassian.net/wiki/spaces/SD/pages/1439233/Glossary
https://docs-snaplogic.atlassian.net/wiki/spaces/SD/pages/1438341/Getting+Started
https://docs-snaplogic.atlassian.net/wiki/spaces/SD/pages/1439233/Glossary