[
https://issues.apache.org/jira/browse/NIFI-7851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17451799#comment-17451799
]
Mahieddine Cherif commented on NIFI-7851:
-----------------------------------------
Thanks for creating this ticket, we faced the same issue, i think one simple
approach to tackle this issue would be to :
1 - Route all records which failed (HTTP response code 4xx or 5xx or even
timeout potentially) to failure/unmatched relationship pretty easy this one.
2 - While executing the response reader, enrich the context with some
attributes (response message, response code same as InvokeHttp basically) that
can be used into a JsonPathReader for example to create new fields containing
this response headers. The user will be able after to partition the failed
records and reprocess them or not based on the error or even log errors if
needed.
> RestLookupService does not throw a LookupFailureException when the rest
> endpoint response-code is not successful.
> -----------------------------------------------------------------------------------------------------------------
>
> Key: NIFI-7851
> URL: https://issues.apache.org/jira/browse/NIFI-7851
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Reporter: Esteban Capoccetti
> Assignee: Nadeem
> Priority: Blocker
>
> RestLookupService does not throw a LookupFailureException when the rest
> endpoint response-code is not successful.
> Lookup Processor using a "Lookup Service" of type "RestLookupService" do not
> send the flowFile into a Failure Connections when the rest service
> http-response-code is not a successful one; it sends those flowfiles to the
> "success/matched" connections instead.
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
