You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "Travis Neeley (JIRA)" <ji...@apache.org> on 2019/06/20 02:32:00 UTC

[jira] [Created] (NIFI-6387) RetryFlowFile

Travis Neeley created NIFI-6387:
-----------------------------------

             Summary: RetryFlowFile
                 Key: NIFI-6387
                 URL: https://issues.apache.org/jira/browse/NIFI-6387
             Project: Apache NiFi
          Issue Type: Improvement
            Reporter: Travis Neeley


Processor takes a FlowFile. It will then look for a retry attribute on the FlowFile. If none is present or if the designated retry attribute is set and not a number, the retry attribute is set to "1" and passed to a retry relationship.

A configurable PropertyDescriptor contains the maximum number of times the FlowFile can be retried before being passed to a separate retries exceeded relationship. This PropertyDescriptor should have a validator for allowable positive integers for the retry.

Processor may also conditionally penalize the FlowFile on the retry relationship.

 

Many interactions with NiFi request some information from a service and retry if the response isn't explicitly success. While it's quite common to use UpdateAttribute followed by a RouteOnAttribute to do this, there could be value in having a discreet processor for this.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)