@vincenr – as @koryknick pointed out, you don’t need an endpoint just to get the pipeline execute to work. However, you may eventually encounter a situation where you need to dump an output to /dev/null so to speak (for example, when IN a child pipeline, you can have only ONE document stream open at the end).
For this, use an “Exit” snap (found in the “Flow” menu), and set the Threshold Limit to a number that far exceeds the number of documents it might ever receive. Name the snap informatively: “End” or “Exit” or “Suppress Returned Documents”, etc. Put it at the end of a path in the pipeline where you need it:
Since you’ll never hit the threshold, you’ll never get an error.
It simply “eats” the documents, sending them to that great big bit bucket in the sky.
PS: Another way to end a chain of snaps is to simply delete the output view on the last snap:
Note that all of the above examples are actually from the same pipeline. This is a VERY good example of when you’d need both strategies. It’s a child pipeline and there is a different path (not shown) that is expected to pass documents back up to the parent pipeline. The purple-ish snap is a call to a stored procedure so there are two outputs, neither of which can be removed from the snap. In one case, there’s something we want to pass to a logging pipeline, but we don’t want the doc stream to go any further than that. The other output, we don’t want to do anything with, but we must supply a “terminator” because there can only be one output path from a child pipeline to it’s parent, and the SP doesn’t return a useful result set.
Whew! Longer reply than I’d expected!
Hope this helps!
