I can vouch for this method. I have two flows for a client that use GenerateFlowFile to build a JSON DSL query for ElasticSearch and are executed on a timer. Works quite well with InvokeHttp.
On Thu, Oct 19, 2017 at 11:41 PM, Mark Rachelski <[email protected]> wrote: > Thank you Bryan, > > That should fit my purposes well. > > BTW: That processor is not in the User Guide. > > As a follow on question, is there an easy way to ask NiFi for all > processors that can be used at the beginning of a flow? There are a lot of > other tagging that is done. But I spent a few hours last night googling for > an answer before posting this question into the mail group. > > Mark. > > On Fri, Oct 20, 2017 at 9:33 AM Bryan Bende <[email protected]> wrote: > >> Hi Mark, >> >> You can use GeneratFlowFile as the initial processor to trigger your flow. >> >> Make sure to change the run schedule appropriately otherwise you will get >> a lot of flow files generated. >> >> -Bryan >> >> On Thu, Oct 19, 2017 at 10:08 PM Mark Rachelski <[email protected]> >> wrote: >> >>> I have a scenario where I need to make an HTTP request to an API but >>> taking context into account from previous invocations. Specifically, one >>> query string parameter is a time where the API returns all records from >>> that time or later. Every day, I would issue a new request using the >>> previous time requested. >>> >>> I have worked out that I can store the last time requested in the state >>> store. And use an UpdateAttributes process to retrieve it or initialize it >>> on the first run. I can then feed that into the InvokeHTTP processor and >>> build a dynamic URL from that attribute. >>> >>> But my main problem is that I don't know what beginning processor to use >>> in this flow. UpdateAttribute needs an inbound connection. And there are no >>> obvious 'dummy' beginning processors that I can find in the vast array. The >>> only thing I need from the beginning processor is the schedule tab. >>> >>> Any ideas on what my first processor in this flow should be? >>> >>> Thank you in advance for any help, >>> Mark. >>> >> -- >> Sent from Gmail Mobile >> >
