-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Declarative flush callback #71
Labels
Comments
Open
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: