You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Mark Payne (Jira)" <ji...@apache.org> on 2020/06/11 22:03:00 UTC

[jira] [Commented] (NIFI-7524) Add retry relationship to ExecuteSQL

    [ https://issues.apache.org/jira/browse/NIFI-7524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17133733#comment-17133733 ] 

Mark Payne commented on NIFI-7524:
----------------------------------

I would recommend a name like "comms.failure" or something of that nature, that describes the failure condition. A name such as "retry" is too prescriptive - it leaves the decision of what to do in such a case in the hands of a flow designer but at the same time names the relationship in such a way that presumes it knows how the condition should be handled.

> Add retry relationship to ExecuteSQL
> ------------------------------------
>
>                 Key: NIFI-7524
>                 URL: https://issues.apache.org/jira/browse/NIFI-7524
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>            Reporter: Matt Burgess
>            Priority: Major
>
> Currently ExecuteSQL has success and failure relationships, where all errors/failures are routed to failure. However for transient exceptions such as "Connection refused", it would be better to have a retry relationship to indicate that the flow file could be processed successfully in the future, rather than invalid SQL errors, e.g.  The retry relationship exists in other RDBMS processors such as PutSQL and PutDatabaseRecord, and would be helpful for ExecuteSQL as well.



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