One (possibly bad) idea would be to try and loop your flow around the UpdateAttribute processor using RouteOnAttribute. UpdateAttribute has an "advanced" mode which would let you do logic something like:
if $foo == "" then set $foo = "step 1"; if $foo == "step 1" then set $foo = "step 2"; if $foo == "step 2" then set $foo = "step 3"; ... if $foo == "step n" then set $foo = "finished"; The next part would be RouteOnAttribute, which would read the value of $foo and if set to "finished" break the loop. Otherwise it would pass to InvokeHTTP and then back to UpdateAttribute. The setup for this would be tedious, but I think it would technically work. Just putting this out there for brainstorming purposes. On Wed, Mar 30, 2016 at 6:25 PM, kkang <ki.k...@ds-iq.com> wrote: > I have been able to figure out how to GenerateFlowFile -> UpdateAttribute > -> > InvokeHttp to dynamically send a URL (example: > https://somedomain.com?parameterx=${foo}); however, I need to do this N > number of times and replace ${foo} with a known set of values. Is there a > way to call InvokeHttp multiple times and use the next value for ${foo} > automatically? > > > > -- > View this message in context: > http://apache-nifi-developer-list.39713.n7.nabble.com/Dynamic-URLs-using-InvokeHttp-from-an-array-tp8638.html > Sent from the Apache NiFi Developer List mailing list archive at > Nabble.com. >
