nifi-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (NIFI-6387) RetryFlowFile
Date Fri, 05 Jul 2019 06:03:00 GMT


ASF subversion and git services commented on NIFI-6387:

Commit 44b84a678f0c0c9769351e0418ec71ab42e966da in nifi's branch refs/heads/master from Travis
[;h=44b84a6 ]

NIFI-6387 RetryFlowFile

NIFI-6387 RetryFlowFile

NIFI-6387 Maximum Retries support FLOWFILE_ATTRIBUTES scope

NIFI-6387 Fixed reuses descriptions for clarity

This closes #3541.

Signed-off-by: Koji Kawamura <>

> RetryFlowFile
> -------------
>                 Key: NIFI-6387
>                 URL:
>             Project: Apache NiFi
>          Issue Type: Improvement
>            Reporter: Travis Neeley
>            Priority: Minor
>   Original Estimate: 2h
>          Time Spent: 4h
>  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 message was sent by Atlassian JIRA

View raw message