This sounds like a good candidate for the `ExecuteScript` processor. Matt Burgess has written some good tutorials on using that here [1] [2]. You could also write a custom processor that extends `InvokeHTTP` and uses the new state management features [3] to keep a counter value, an iteration limit, and the known values.
[1] http://funnifi.blogspot.com/2016/02/writing-reusable-scripted-processors-in.html <http://funnifi.blogspot.com/2016/02/writing-reusable-scripted-processors-in.html> [2] http://funnifi.blogspot.com/2016/03/executescript-json-to-json-revisited_14.html <http://funnifi.blogspot.com/2016/03/executescript-json-to-json-revisited_14.html> [3] https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#state_management <https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#state_management> Andy LoPresto [email protected] PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > On Mar 30, 2016, at 3:25 PM, kkang <[email protected]> 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.
signature.asc
Description: Message signed with OpenPGP using GPGMail
