[jira] [Updated] (NIFI-4948) MongoDB Lookup Service throws an exception if there is no match
[ https://issues.apache.org/jira/browse/NIFI-4948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess updated NIFI-4948: --- Resolution: Fixed Status: Resolved (was: Patch Available) > 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)
[jira] [Updated] (NIFI-4948) MongoDB Lookup Service throws an exception if there is no match
[ https://issues.apache.org/jira/browse/NIFI-4948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess updated NIFI-4948: --- Fix Version/s: 1.6.0 > 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)
[jira] [Updated] (NIFI-4948) MongoDB Lookup Service throws an exception if there is no match
[ https://issues.apache.org/jira/browse/NIFI-4948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Villard updated NIFI-4948: - Description: 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. (was: The LookupRecord processor states that in case of no match in the lookup the 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.) > 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 > > 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)
[jira] [Updated] (NIFI-4948) MongoDB Lookup Service throws an exception if there is no match
[ https://issues.apache.org/jira/browse/NIFI-4948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Villard updated NIFI-4948: - Status: Patch Available (was: Open) > 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 > > The LookupRecord processor states that in case of no match in the lookup the > 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)