[NIFI-6387] RetryFlowFile

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 1.10.0
• Assignee: Travis Neeley
• Reporter: Travis Neeley
• Created: 20/Jun/19 02:31
• Updated: 05/Jul/19 06:06
• Resolved: 05/Jul/19 06:06

Description

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.

Issue Links

• links to: GitHub Pull Request #3541