[
https://issues.apache.org/jira/browse/NIFI-4634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Villard resolved NIFI-4634.
----------------------------------
Resolution: Feedback Received
Apache NiFi 1.x is no longer maintained and no new release is planned on the
1.x release line. Marking as resolved as part of a cleanup operation. Please
open a new one with an updated description if this is still relevant for NiFi
2.x.
> MongoDBLookupService should support key in other format than String
> -------------------------------------------------------------------
>
> Key: NIFI-4634
> URL: https://issues.apache.org/jira/browse/NIFI-4634
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.4.0
> Reporter: Abdelkrim Hadjidj
> Priority: Major
>
> When using MongoDBLookupService, the Lookup works only if the key type is
> string in MongoDB. By using an integer key in mongoDB and an integer lookup
> key in NiFi, the LookupService is not able to match correctly.
> I tested it with the following scenario:
> https://community.hortonworks.com/articles/146198/data-flow-enrichment-with-nifi-part-3-lookuprecord.html
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
