[
https://issues.apache.org/jira/browse/NIFI-1423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15113812#comment-15113812
]
Louis-Etienne Dorval commented on NIFI-1423:
--------------------------------------------
Hi Joseph,
In my particular case, I'm trying to validate if the content of the FlowFile is
present in the datastore of a webapp. Since my Flow starts with the same input
as the persistence layer of the webapp (both listen on a JMS Topic), NiFi
sometimes ask for the document before it was persisted. The webapp response is
a 404 Not Found which is routed to the 'No Retry' relationship. Even so, I want
to retry as the data will probably be there the next time.
I would agree that the ControlRate might be a potential candidate to fix it if
I'm adding it to the 'No Retry' relationship. I only find it strange that if
the webapp would have returned 5xx, I would not need that additional processor.
Also, I would argue that the 'No Retry' might be misleading as there's a few
usecases (even in the RFC {{1}}) that a 3xx or 4xx response code could be retry
as-is. That includes 408 Request Timeout (that case it could be retried
immediately after but it's likely due to some load or factor that some wait
could help) or 304 Not Modified (validate a caching server until the cache has
changed) or 404 Not Found
Let me know if that helps you understand my case or if I've missed something
Thanks
{{1}} https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.9
> 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)
