Hi Otto and Mike, The LookupRecord does look fruitful, although I don't have a defined schema for the JsonTreeReader. Is there a way to just keep it generic? I know I have valid JSON already, I just want to add the result of the MongoQuery to a specific Json Path in the FlowFile.
The LookupAttribute also seems like it could be another avenue, but it doesn't have the MongoDBLookupService in the list of Compatible Controller Services. Ryan On Fri, Nov 30, 2018 at 10:24 AM Mike Thomsen <[email protected]> wrote: > LookupAttribute + the MongoDBLookupService should be able to do that. > > On Thu, Nov 29, 2018 at 8:05 PM Otto Fowler <[email protected]> > wrote: > >> Sounds like you want to look at enrichment with the LookupRecord >> processors and Mongo. >> >> https://community.hortonworks.com/articles/146198/data-flow-enrichment-with-nifi-part-3-lookuprecord.html >> >> >> On November 29, 2018 at 17:12:38, Ryan Hendrickson ( >> [email protected]) wrote: >> >> Hi all, >> I'm curious if the GetMongo processor can allow you can pass in a >> FlowFile Document and enrich the original FlowFile document with the >> results from the Query Result - or more generally store the result as a >> NiFi Attribute, instead of replacing the content in the FlowFile. >> >> I really want to "enrich" my results with data from Mongo, not replace >> my FlowFile with the database record that matches. >> >> I had thought I had figured out a way to do this in the past, but >> can't seem to replicate it, so I figured I'd ask the community. >> >> Thanks, >> Ryan >> >>
