Re: Getting Duplicate Flowfiles from InvokeHttp and QueryElasticsearchHttp

2019-03-20 Thread martin.cooley
Bryan, Thanks so much! I get it now, and was able to find the setting and change it to behave the way that makes the most sense for me. I appreciate all your help, Martin -- Sent from: http://apache-nifi-developer-list.39713.n7.nabble.com/

Re: Getting Duplicate Flowfiles from InvokeHttp and QueryElasticsearchHttp

2019-03-19 Thread Bryan Bende
Hi Martin, Since you have a 2 node cluster, when you start the processors they are likely running on both nodes doing the same thing twice and what you see in the stats and queues is the combined values across the cluster, so that is why you see either 2 or 4, instead of 1 or 2. Each processor

Re: Getting Duplicate Flowfiles from InvokeHttp and QueryElasticsearchHttp

2019-03-19 Thread martin.cooley
Hey Bryan, Indeed it is a 2 node cluster. I would like to say I see where this is going, but I don't. Thanks, Martin Bryan Bende wrote > Hello, > > Are you running a NiFi cluster of 2 nodes, or a standalone instance of > NiFi? > > -Bryan > > On Mon, Mar 18, 2019 at 12:21 PM Martin Cooley

Getting Duplicate Flowfiles from InvokeHttp and QueryElasticsearchHttp

2019-03-18 Thread Martin Cooley
If I configure an InvokeHttp processor to query against an elasticsearch node, I should get one json object written to a flowfile. If I use the QueryElasticsearchHttp processor, if the query returns two documents from the index, I should get two json objects, each written to their own flowfile.