You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is sometimes useful to take advantage of the flush callback to step streams.
For example, I used the SHACL step in a way that pipeline does not fail immediately on error but stores reports in memory and only fails the pipeline at the end. Another use case that could be implemented with flush would be to call hooks when pipeline finishes
It is sometimes useful to take advantage of the
flush
callback to step streams.For example, I used the SHACL step in a way that pipeline does not fail immediately on error but stores reports in memory and only fails the pipeline at the end. Another use case that could be implemented with
flush
would be to call hooks when pipeline finishesMy current SHACL looks somewhat like this
The
failOnAnyViolations
stream is essentially aPassThrough
with the second callback.I would like to propose an optional property for steps, which would combine both:
The text was updated successfully, but these errors were encountered: