[
https://issues.apache.org/jira/browse/NIFI-4103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16061098#comment-16061098
]
ASF subversion and git services commented on NIFI-4103:
-------------------------------------------------------
Commit 8878d732dd4d6e862712aeaa5cc46e7c06d28892 in nifi's branch
refs/heads/master from [~markap14]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=8878d73 ]
NIFI-4103: Return an empty Optional if an IP address cannot be found
Signed-off-by: Matt Burgess <[email protected]>
This closes #1933
> IPLookupService returns a Record with all null fields if the given IP cannot
> be found
> -------------------------------------------------------------------------------------
>
> Key: NIFI-4103
> URL: https://issues.apache.org/jira/browse/NIFI-4103
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: Mark Payne
> Assignee: Mark Payne
> Fix For: 1.4.0
>
>
> If IPLookupService is used to lookup an IP address and the IP address cannot
> be found (for instance 10.0.1.2) then the service returns a Record object
> where all of the fields are null. Instead, it should return an empty
> Optional. As it is right now, if using the LookupRecord processor, all
> FlowFiles will be routed to 'matched' instead of 'unmatched' because even if
> the IP address isn't found, a Record is returned.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
