Thanks for the reply Joe. Just a thought – do you think it would be a good idea for every Get processor (GetMongo, GetHBase etc.) to have 2 additional properties like:
1. Result in Content or Result in Attribute 2. Result Attribute Name (only applicable when “Result in Attribute” is selected). But then all such processors should be able to accept incoming flowfile (which they don’t as of now – being a “Get”). May be ExecuteSQL and FetchDistributeMapCache can be enhanced that way i.e. have an option to specify the destination – content or attribute? Regards, Manish From: Joe Witt [mailto:[email protected]] Sent: Friday, September 02, 2016 5:58 PM To: [email protected] Subject: Re: Processor to enrich attribute from external service You would need to make a custom process for now. I think we should have a nice controller service to generalize jdbc lookups which supports caching. And then a processor which leverages it. This comes up fairly often and is pretty straightforward from a design POV. Anyone want to take a stab at this? On Sep 2, 2016 4:47 PM, "Manish Gupta 8" <[email protected]<mailto:[email protected]>> wrote: Hello Everyone, Is there a processor that we can use for updating/adding an attribute of an incoming flow file from some external service (say MongoDB or Couchbase or any RDBMS)? The processor will use the attribute of incoming flow file, query the external service, and simply modify/add an additional attribute of flow-file (without touching the flow file content). If we have to achieve this kind of “lookup” operation (but only to update attribute and not the content), what are the options in NiFi? Should we create a custom processor (may be by taking GetMongo processor and modifying its code to update an attribute with query result)? Thanks, Manish
