In this article
Table of Contents | ||||||
---|---|---|---|---|---|---|
|
PipeLoop Snap
Demo slides: https://docs.google.com/presentation/d/1rTjUi9kRgcxrkQqkvsIOB0_C3jjahivTXNZ0qK9_Bcs/edit?usp=sharing
Table of Contents | ||
---|---|---|
|
Overview
You can use this Snap to enable looping on pipeline executions (do while loop) based on a stopping stop condition or a hard cutoff iteration limit. The output document of the snap will be each iteration is fed into the next round of document input for execution iteration as the input document, and execution continues until the stop condition is met or the cutoff iteration limit is reached. Learn more.
...
Snap Type
The PipeLoop Snap is a Flow-type Snap.
Prerequisites
Valid client ID.
A valid account with the required permissionsChild pipelines must have one input view and one output view.
Support for Ultra
...
Tasks
Does not support Ultra Tasks.
Limitations
Reuse is currently not currently supported because of needing the requirement to close an input view in order to force a flush of all documents out.
PipeLoop supports child pipelines with 1 and only 1 open input view and 1 and only 1 open output view.
PipeLoop will read Reads only the first output document for a given fed-in specific input document (all others will be the remaining documents are ignored and dropped).
We will be able to support expression Supports expressions on the pipeline specification, but it will only evaluate on evaluates the input document to PipeLoop, not for each iteration.
Known Issues
None.
Snap Views
Type | Format | Number of Views | Examples of Upstream and Downstream Snaps | Description |
---|---|---|---|---|
Input |
|
|
| The document or binary data to send to the child |
pipeline. For a single document input, only the first output document is captured in the output document and the remaining documents are ignored. | ||||
Output |
|
|
| If you select the Debug iterations output checkbox, an additional
|
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 |
Snap Settings
Info |
---|
Learn more about managing Filesthe icons in the Snap Settings dialog. |
Field Name | Field Type | Description | |
---|---|---|---|
Label*
Default Value: |
PipeLoop |
SimpleLoop | String |
Specify the name for the Snap. You can modify this to be more specific, especially if you have more than one of the same |
Snaps in your pipeline.
| |||
Pipeline*
Default Value: N/A | String/Expression | Specify the path of the pipeline to execute. | |
Pipeline Parameters | Use this field set to define child pipeline parameters to use for executing the pipeline. | ||
Parameter name Default Value: |
N/A |
tools | String/Suggestion | Specify |
the parameter's name. You can also select the Pipeline Parameters defined for the |
pipeline selected in the Pipeline field. |
Parameter value Default Value: |
N/A |
$tools | String/Expression | Specify the value for thepipeline parameter, which can be an expression based on incoming documents or a constant. If you configure the value as an expression based on the input, then each incoming document or binary data is evaluated against that expression when invoking the pipeline. The result of the expression is JSON-encoded if it is not a string. The child |
pipeline then needs to use the |
. | |||
Loop options | Define the iteration configuration. | ||
Stop condition Default Value: N/A | String/Expression | Specify the condition to be evaluated during execution that decides whether the execution should stop or continue. The |
iteration continues until the stop condition is met or the iteration limit is reached. The Snap errors out if the Stop condition cannot be evaluated at run time. The stop condition is evaluated on the output document from each iteration. | |||
Iteration limit Default Value: 10 | Integer/Expression | Specify the maximum limit for the number of iterations to run to avoid infinite loops. | |
Debug iteration outputs Default Value: |
Example:
Deselected | Checkbox | Select this checkbox to |
include the index, output document, and stop condition evaluation for |
each iteration as part of the output format.
| |||
Execution options | Define the child pipeline execution configuration. | ||
Execute on Default Value: LOCAL_NODE |
Dropdown list | Select |
one of the following Snaplex options to specify the target Snaplex for the child |
pipeline:
|
|
|
|
Snaplex path
Default Value: N/AExample:
String/Expression
Appears when you choose the SNAPLEX_WITH_PATH option.
Specify the Snaplex to execute on
| |||
Execution label Default Value: N/A | String/Expression | Specify the label to display in the Dashboard for the current execution. | |
Snap Execution Default Value: Validate & Execute |
Execute only | Dropdown list | Select one of the following three modes in which the Snap executes:
|
Troubleshooting
...
Error
...
Reason
...
Resolution
...
Account validation failed.
...
The Pipeline ended before the batch could complete execution due to a connection error.
...
Verify that the Refresh token field is configured to handle the inputs properly. If you are not sure when the input data is available, configure this field as zero to keep the connection always open.
Examples
Excluding Fields from the Input Data Stream
We can exclude the unrequired fields from the input data stream by omitting them in the Input schema fieldset. This example demonstrates how we can use the <Snap Name> to achieve this result:
<screenshot of Pipeline/Snap and description>
Download this Pipeline.
Downloads
Info |
---|
|
Attachments | ||||
---|---|---|---|---|
|
Snap Pack History
...
title | Click here to expand... |
---|
Example
Insert excerpt |
---|
|
|
...
links: