[
https://issues.apache.org/jira/browse/NIFI-1423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15123042#comment-15123042
]
ASF GitHub Bot commented on NIFI-1423:
--------------------------------------
Github user apiri commented on the pull request:
https://github.com/apache/nifi/pull/183#issuecomment-176597280
Agree with @JPercivall regarding the rollback to be able to get a full
handle on rolled back files for a given session/execution to understand how the
processor behaved. Scanning through the codebase, these are a minority of
usages and typically would only get invoked when there is a dev issue causing
exceptions, but could see it getting more usage within
AbstractionSessionFactory based processors where that functionality could be
preferred. Seems like a quick effort for consistency.
> 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)
