[jira] [Created] (NIFI-8262) Make ExecuteSQL and PutSQL behavior consistent for connection errors (retry, e.g.)

["Matt Burgess (Jira)" <ji...@apache.org>]

Matt Burgess created NIFI-8262:
----------------------------------

             Summary: Make ExecuteSQL and PutSQL behavior consistent for connection errors (retry, e.g.)
                 Key: NIFI-8262
                 URL: https://issues.apache.org/jira/browse/NIFI-8262
             Project: Apache NiFi
          Issue Type: Improvement
          Components: Extensions
            Reporter: Matt Burgess


Currently if there is an error when getting a connection to the target database, ExecuteSQL will route an incoming flowfile to failure and PutSQL will rollback the session with a ProcessException. For use cases where PutSQL needs to "fail fast", there should be the capability to route the flowfile rather than returning it to the input queue via rollback. Likewise the user may want to rollback or retry the flowfile rather than having it routed to failure.

This could be propert(ies) to define the behavior, or perhaps adding a "retry" relationship to ExecuteSQL, and ensure in PutSQL any connection errors cause the flowfile to be sent to retry. The latter can cause issues with backwards compatibility and expected behavior, so care must be taken to get a prudent solution.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)