Hi Tim,
Sorry for the late reply.
It seems the ScrollElasticsearchHttp processor is designed to run a
one-shot query to import query results from Elasticsearch.
The description says "The state must be cleared before another query
can be run."
It tracks progress using managed state, not via
Hello,
I would like to use the existing ScrollElasticsearchHttp to perform a search
that returns a potentially large number of hits. The parameters of the search
need to reference one or more flow file attributes.
Looking at the source code for this processor it appears that the QUERY