[
https://issues.apache.org/jira/browse/NIFI-4948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16391690#comment-16391690
]
ASF subversion and git services commented on NIFI-4948:
-------------------------------------------------------
Commit 1f8af1bde394e2ab4df4191fcb251555817e470a in nifi's branch
refs/heads/master from [~pvillard]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=1f8af1b ]
NIFI-4948 - MongoDB Lookup Service throws an exception if there is no match
Signed-off-by: Matthew Burgess <[email protected]>
This closes #2522
> MongoDB Lookup Service throws an exception if there is no match
> ---------------------------------------------------------------
>
> Key: NIFI-4948
> URL: https://issues.apache.org/jira/browse/NIFI-4948
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 1.5.0
> Reporter: Pierre Villard
> Assignee: Pierre Villard
> Priority: Major
> Fix For: 1.6.0
>
>
> The LookupRecord processor states that in case of no match in the lookup
> service, the FF will be routed either to success or to unmatched (depending
> on the strategy). At the moment the MongoDB lookup service throws an
> exception in case there is no match. It causes the FF to be routed to failure.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
