[
https://issues.apache.org/jira/browse/NIFI-6387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Koji Kawamura resolved NIFI-6387.
---------------------------------
Resolution: Fixed
Fix Version/s: 1.10.0
Thanks [~tneeley] for your contribution! I've added NiFi Jira projects
'Contributor' role to your account. You can now assign yourself to NiFi Jira
issues.
> RetryFlowFile
> -------------
>
> Key: NIFI-6387
> URL: https://issues.apache.org/jira/browse/NIFI-6387
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Travis Neeley
> Assignee: Travis Neeley
> Priority: Minor
> Fix For: 1.10.0
>
> Original Estimate: 2h
> Time Spent: 4h 10m
> Remaining Estimate: 0h
>
> 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)
