[
https://issues.apache.org/jira/browse/NIFI-10646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17618019#comment-17618019
]
Peter Kimberley commented on NIFI-10646:
----------------------------------------
This processor also does not behave as expected, in that each record field
specified for enrichment, must already exist in the source record in order for
the corresponding geoip value to be written.
A better approach would be to update the schema to include all required geo
fields. This would save the user having to `UpdateRecord` with blank fields
before invoking this processor.
> 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
>
> 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)
