Ensure serial child pipeline execution
On the Pipeline Execute snap, if I have the Reuse checkbox unchecked and the pool size =1, does that ensure the executions of the child pipelines are serial and not parallel? I want to ensure only on...
Forum Discussion
But the drawback is you can’t leverage the parameters dynamically in this particular scenario.
Can you elaborate? The OP mentioned that reuse was off, so the parameters passed to the child pipeline can change for each execution.
Actually we’ve developed a reusable component - service to reprocess failed transaction and then individual interface pipelines. In case of failures with interface pipelines, we will use the re-processing service to resend the failed transactions. By using pipeline execute in the reprocess service we want to achieve parallel execution on different failed pipelines with each failed transaction calling individual interface pipeline sequentially.
We get parallel execution of each pipeline and sequential processing of documents in the order of input (with reuse option set to 1), but this does not support change in pipeline parameter values. Hence we will have to send the payload, runid and parameters as input documents instead of pipeline parameters.
We’ve raised a ticket 20085 for this issue. If you’ve a solution for our situation please share will be really helpful.
The documentation is clear in this aspect. If it is not, please mention what to improve upon.
If Reuse is enabled, pipeline parameter values cannot change between execution instances.
If Reuse is disabled, you can pass different parameter values.If you want the parameters to be changed with reuse checked, then that is something an enhancement which may not be possible just by the design of this; which Product Management can elaborate.
Hope that makes sense.
That’s precisely our requirement is, just a minor follow up question - can for each snap help us here .
