[ https://issues.apache.org/jira/browse/NIFI-10646 ]


    Daniel Stieglitz deleted comment on NIFI-10646:
    -----------------------------------------

was (Author: JIRAUSER294662):
[~p-kimberley] I think you should click "Submit Patch" above in order for the 
NIFI team to review and merge.

> GeoEnrichIPRecord fails to route flowfile if IP lookup fails
> ------------------------------------------------------------
>
>                 Key: NIFI-10646
>                 URL: https://issues.apache.org/jira/browse/NIFI-10646
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Extensions
>    Affects Versions: 1.18.0
>            Reporter: Peter Kimberley
>            Priority: Major
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> There is a difference in behaviour with {{GeoEnrichIPRecord}} vs 
> {{{}GeoEnrichIP{}}}, in that failed lookups are not routed to the {{not 
> found}} relationship for {{{}GeoEnrichIPRecord{}}}, but are for 
> {{{}GeoEnrichIP{}}}.
> For instance, an IP of {{127.0.0.1}} when passed to {{{{GeoEnrichIP}}}} gets 
> routed to {{{}not found{}}}, however with {{{}GeoEnrichIPRecord{}}}, the 
> record causes the processor to bail out and the entire flowfile gets stuck in 
> the queue as a result.
> The root cause appears to be the lack of exception handling in 
> {{{}GeoEnrichIPRecord.java{}}}: 
> https://github.com/apache/nifi/blob/04c0df172329c8a5dfc865c4a8cab866f18e91a9/nifi-nar-bundles/nifi-enrich-bundle/nifi-enrich-processors/src/main/java/org/apache/nifi/processors/GeoEnrichIPRecord.java#L230



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to