title: Connecting NiFi to ElasticSearch
body: <p>I'm trying to solve one task and will appreciate any help - links to documentation, or links to forums, or other FAQs besides <a href="https://cwiki.apache.org/confluence/display/NIFI/FAQs" rel="nofollow noreferrer">https://cwiki.apache.org/confluence/display/NIFI/FAQs</a>, or any meaningful answer in this post =) .</p>
  
  <p>So, I have the following task:
  Initial part of my system collects data each 5-15 min from different DB sources. Then I remove duplicates, remove junk, combine data from different sources according to logic and then redirect it to second part of the system as several streams. 
  As far as I know, "NiFi" can do this task in the best way =).</p>
  
  <p>Currently I can successfully get information from InfluxDB by "GetHTTP" processor. However I can't configure same kind of processor for getting information from Elastic DB with all necessary options. I'd like to receive data each 5-15 minutes for time period from "now-minus-&lt;5-15 minutes>" to "now". (depends on scheduler period) with several additional filters. If I understand it right, this can be achieved either by subscription to "_index" or by regular requests to DB with desired interval.</p>
  
  <p>I know that NiFi has several specific Processors designed for Elasticsearch (FetchElasticsearch5, FetchElasticsearchHttp, QueryElasticsearchHttp, ScrollElasticsearchHttp) as well as GetHTTP and PostHTTP Processors. However, unfortunately, I have lack of information or even better - examples - how to configure their "Properties" for my purposes =(. </p>
  
  <p>What's the difference between FetchElasticsearchHttp, QueryElasticsearchHttp? Which one fits better for my task? What's the difference between GetHTTP and QueryElasticsearchHttp besides several specific fields? Will GetHTTP perform the same way if I tune it as I need?</p>
  
  <p>Any advice?</p>
  
  <p>I will be grateful for any help. </p>