[
https://issues.apache.org/jira/browse/NIFI-13860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17890430#comment-17890430
]
ASF subversion and git services commented on NIFI-13860:
--------------------------------------------------------
Commit 1625679baea907fc40d7c285437d392d094100e7 in nifi's branch
refs/heads/support/nifi-1.x from Tamas Palfy
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=1625679bae ]
NIFI-13860 Avoid Throwing Exceptions for Failures in IPLookupService
This closes #9404.
Signed-off-by: Peter Turcsanyi <[email protected]>
> IPLookupService throws exception when lookup fails
> --------------------------------------------------
>
> Key: NIFI-13860
> URL: https://issues.apache.org/jira/browse/NIFI-13860
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Reporter: Tamas Palfy
> Assignee: Tamas Palfy
> Priority: Major
> Fix For: 2.0.0-M5
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> The
> {code:java}
> Optional<Record> lookup
> {code}
> in {{IPLookupService}} calls into {{com.maxmind.geoip2.DatabaseReader}}
> methods that throw {{AddressNotFoundException}} when an IP lookup fails.
> When used in the {{LookupRecord}} processor a single unrecognized entry in a
> list of IPs can cause an error and the entire flowfile is routed to the
> _failure_ relationship instead of routing the unfound records to _unmatched_
> and keep routing the found ones to _matched_.
> The {{DatabaseReader}} has {{tryX}} methods that return an {{Optional}}
> instead of throwing an exception when the IP is not found in the DB. All
> lookups should use this variant.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
