[
https://issues.apache.org/jira/browse/NIFI-1423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15111303#comment-15111303
]
ASF GitHub Bot commented on NIFI-1423:
--------------------------------------
GitHub user ledor473 opened a pull request:
https://github.com/apache/nifi/pull/183
NIFI-1423 Allow to penalize FlowFiles to No Retry
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ledor473/nifi penalize-http-no-retry
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/183.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #183
----
commit 8f0d5419477706433df6200ea97c7e588fd422a7
Author: Louis-Etienne Dorval <[email protected]>
Date: 2016-01-21T21:08:07Z
NIFI-1423 Allow to penalize FlowFiles that are routed to No Retry
relationship
----
> InvokeHTTP ability to penalize on No Retry
> ------------------------------------------
>
> Key: NIFI-1423
> URL: https://issues.apache.org/jira/browse/NIFI-1423
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Affects Versions: 0.4.1
> Reporter: Louis-Etienne Dorval
> Priority: Minor
>
> InvokeHTTP currently penalize FlowFiles on {{Failure}} (Exception) and
> {{Retry}} (5xx) but not on {{No Retry}} (1xx, 3xx, 4xx)
> As there is probably a reason for not penalizing it, there could be a way to
> opt-in for that behavior rather than forcing it.
> My usecase is discussed a bit more in the mailing list:
> http://mail-archives.apache.org/mod_mbox/nifi-users/201512.mbox/%3CCADSFSqHzCjxNNzJdbBAPS2x_iALVWL6zwR%2B8_Ecg%3DvUqpw9EgQ%40mail.gmail.com%3E
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
