[ https://issues.apache.org/jira/browse/NIFI-6387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16878989#comment-16878989
]
ASF subversion and git services commented on NIFI-6387:
-------------------------------------------------------
Commit 44b84a678f0c0c9769351e0418ec71ab42e966da in nifi's branch refs/heads/master from Travis
Neeley
[ https://gitbox.apache.org/repos/asf?p=nifi.git;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 <ijokarumawak@apache.org>
> RetryFlowFile
> -------------
>
> Key: NIFI-6387
> URL: https://issues.apache.org/jira/browse/NIFI-6387
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
|