I'm trying to set up TLS for a service using /InvokeHTTP/ against an
external-to-NiFi Tomcat-based service and I have configured
/StandardRestrictedSSLContextService/ thus:
https://www.javahotchocolate.com/notes/nifi-images/mdmi-standard-ssl-context-service.png
...which results in the errors
Greg,
Whether the output goes to “nonzero status” or “output stream”, the original
FlowFile should still be sent to the “original” relationship.
Now, if you set retries to say 3 for “nonzero status” and a FlowFile is routed
to that relationship, what will happen is that the FlowFile is
Mark:
Thank you for the explanation, yes it helps. I made the changes and everything
worked with one exception: preserving the original content. The non-zero
status will replace the flowfile content with whatever came through the output
stream, so the original content is lost. When the file
Greg,
You wouldn’t want to retry the “original” relationship. The processor has 3
relationships: original, output stream, and nonzero status. It should always
send the incoming FlowFile to original. So if you retry that relationship
you’ll always retry the flowfile, regardless of whether it
Hello:
The ExecuteStreamCommand processor has 3 relationships. To trap processing
failures, I capture flowfiles from the original relationship, inspect the cmd
exit status, and reroute to a RetryFlowFile processor if the exit status is not
0. I wanted to see if this could be simplified with
Hi Max,
Having a quick look through the PR, it looks like it was closed due to
inactivity.
All that probably needs to happen is for someone to check that the change
is still good and then re-open the PR.
If someone can pick this up, the contributor guidelines, (
