Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]
Created 07-06-2022 01:10 AM
I am trying to learn how to use the RestLookupService to make REST API calls. But since it is a controller service, not a processor.. so I need some guidance on which processor I should use.. where I can configure this service. I want to save the response that this service returns to somewhere else..let's say to the local file system...using PutFile.
Created 07-06-2022 04:50 AM
@sayak17 ,
You need to configure your RestLookupService with the details of the external REST service that you want to use for lookups and then use the LookupRecord processor in your flow to perform the actual lookups.
The LookupRecord processor takes a reference to the RestLookupService controller service.
Cheers,
André
Created 07-06-2022 04:50 AM
@sayak17 ,
You need to configure your RestLookupService with the details of the external REST service that you want to use for lookups and then use the LookupRecord processor in your flow to perform the actual lookups.
The LookupRecord processor takes a reference to the RestLookupService controller service.
Cheers,
André
Created 07-07-2022 08:51 AM
@sayak17
If you are simply looking to GET from a REST API endpoint and take the response and write to a local file on the server where your NiFi service is running, you'll want to use the InvokeHTTP processor and feed that to your putFile processor.
If you found this response assisted with your query, please take a moment to login and click on "Accept as Solution" below this post.
Thank you,
Matt