Support Questions
Find answers, ask questions, and share your expertise

NiFi Records - Best practice for InvokeHTTP from an array of URLs in Records?

Explorer

I am curious what the best practice is for using InvokeHTTP on an array of URLs stored in a singular Record set content file. I thought maybe it would be best to QueryRecord and store the individual URLs to be fed into InvokeHTTP one-by-one, but I'm looking for the optimal way to do this (without creating excessive content/attributes/provenance data.

Is it possible, or ever a good idea to create individual attributes of each URL (with little-to-no content) to be fed into InvokeHTTP?