<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Re: Problems configuring FetchElasticSearch processor in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Problems-configuring-FetchElasticSearch-processor/m-p/193425#M62117</link>
    <description>&lt;P&gt;FetchElasticsearch is used to get a single document from an ES cluster. Each document in ES has a document identifier (or "_id") associated with it, and that identifier is what should be supplied to the Document Identifier property.&lt;/P&gt;&lt;P&gt;If you don't know the document identifier for the document(s) you're looking for, then &lt;A target="_blank" href="https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-elasticsearch-nar/1.2.0/org.apache.nifi.processors.elasticsearch.QueryElasticsearchHttp/index.html"&gt;QueryElasticsearchHttp&lt;/A&gt; is your best bet. It allows you to use the Query String "mini-language" to search for fields with desired values (see &lt;A target="_blank" href="https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-query-string-query.html#query-string-syntax"&gt;here&lt;/A&gt; for more information). You can then parse the results using any number of processors, such as &lt;A target="_blank" href="https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.2.0/org.apache.nifi.processors.standard.EvaluateJsonPath/index.html"&gt;EvaluateJsonPath&lt;/A&gt; to get individual fields from the results, &lt;A target="_blank" href="https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.2.0/org.apache.nifi.processors.standard.SplitJson/index.html"&gt;SplitJson&lt;/A&gt; if there are multiple results, etc.&lt;/P&gt;</description>
    <pubDate>Thu, 01 Jun 2017 22:27:34 GMT</pubDate>
    <dc:creator>mburgess</dc:creator>
    <dc:date>2017-06-01T22:27:34Z</dc:date>
    <item>
      <title>Problems configuring FetchElasticSearch processor</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Problems-configuring-FetchElasticSearch-processor/m-p/193424#M62116</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I am trying to build a flow that gets a file from elasticsearch, however since it is my first time using the FetchElasticSearch processor I am having a doubt about how to configure it. I don't understand what the Document Identifier means and what value am I suppose to give in this configuration. If someone could help in this I would greatly appreciate it.&lt;/P&gt;</description>
      <pubDate>Wed, 31 May 2017 23:45:36 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Problems-configuring-FetchElasticSearch-processor/m-p/193424#M62116</guid>
      <dc:creator>Adda_Fuentes2</dc:creator>
      <dc:date>2017-05-31T23:45:36Z</dc:date>
    </item>
    <item>
      <title>Re: Problems configuring FetchElasticSearch processor</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Problems-configuring-FetchElasticSearch-processor/m-p/193425#M62117</link>
      <description>&lt;P&gt;FetchElasticsearch is used to get a single document from an ES cluster. Each document in ES has a document identifier (or "_id") associated with it, and that identifier is what should be supplied to the Document Identifier property.&lt;/P&gt;&lt;P&gt;If you don't know the document identifier for the document(s) you're looking for, then &lt;A target="_blank" href="https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-elasticsearch-nar/1.2.0/org.apache.nifi.processors.elasticsearch.QueryElasticsearchHttp/index.html"&gt;QueryElasticsearchHttp&lt;/A&gt; is your best bet. It allows you to use the Query String "mini-language" to search for fields with desired values (see &lt;A target="_blank" href="https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-query-string-query.html#query-string-syntax"&gt;here&lt;/A&gt; for more information). You can then parse the results using any number of processors, such as &lt;A target="_blank" href="https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.2.0/org.apache.nifi.processors.standard.EvaluateJsonPath/index.html"&gt;EvaluateJsonPath&lt;/A&gt; to get individual fields from the results, &lt;A target="_blank" href="https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.2.0/org.apache.nifi.processors.standard.SplitJson/index.html"&gt;SplitJson&lt;/A&gt; if there are multiple results, etc.&lt;/P&gt;</description>
      <pubDate>Thu, 01 Jun 2017 22:27:34 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Problems-configuring-FetchElasticSearch-processor/m-p/193425#M62117</guid>
      <dc:creator>mburgess</dc:creator>
      <dc:date>2017-06-01T22:27:34Z</dc:date>
    </item>
    <item>
      <title>Re: Problems configuring FetchElasticSearch processor</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Problems-configuring-FetchElasticSearch-processor/m-p/193426#M62118</link>
      <description>&lt;P&gt;Thanks Matt, the QueryElasticsearchHTTP processor was very useful and helped me with the problem.&lt;/P&gt;</description>
      <pubDate>Thu, 01 Jun 2017 22:43:03 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Problems-configuring-FetchElasticSearch-processor/m-p/193426#M62118</guid>
      <dc:creator>Adda_Fuentes2</dc:creator>
      <dc:date>2017-06-01T22:43:03Z</dc:date>
    </item>
    <item>
      <title>Re: Problems configuring FetchElasticSearch processor</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Problems-configuring-FetchElasticSearch-processor/m-p/193427#M62119</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/641/mburgess.html" nodeid="641"&gt;@Matt Burgess&lt;/A&gt;&lt;/P&gt;&lt;P&gt;If I want to get all the documents in the Index, what is the &lt;STRONG&gt;query &lt;/STRONG&gt;parameter I should be giving in  QueryElasticsearchHTTP processor.&lt;/P&gt;</description>
      <pubDate>Tue, 22 Aug 2017 15:50:54 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Problems-configuring-FetchElasticSearch-processor/m-p/193427#M62119</guid>
      <dc:creator>naveen_mittemar</dc:creator>
      <dc:date>2017-08-22T15:50:54Z</dc:date>
    </item>
    <item>
      <title>Re: Problems configuring FetchElasticSearch processor</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Problems-configuring-FetchElasticSearch-processor/m-p/193428#M62120</link>
      <description>&lt;P&gt;Try * as the value for the Query property.&lt;/P&gt;</description>
      <pubDate>Tue, 22 Aug 2017 20:23:34 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Problems-configuring-FetchElasticSearch-processor/m-p/193428#M62120</guid>
      <dc:creator>mburgess</dc:creator>
      <dc:date>2017-08-22T20:23:34Z</dc:date>
    </item>
    <item>
      <title>Re: Problems configuring FetchElasticSearch processor</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Problems-configuring-FetchElasticSearch-processor/m-p/193429#M62121</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/641/mburgess.html" nodeid="641"&gt;@Matt Burgess&lt;/A&gt;&lt;/P&gt;&lt;P&gt;That worked Matt, Thanks a lot.&lt;/P&gt;&lt;P&gt;I am facing one more problem here.&lt;/P&gt;&lt;P&gt;My flow is like this:&lt;/P&gt;&lt;P&gt;Twitter --&amp;gt; ElasticSearch --&amp;gt; Kafka&lt;/P&gt;&lt;P&gt;Processor Flows:&lt;/P&gt;&lt;P&gt;1. GetTwitter --&amp;gt; PutElasticsearch5&lt;/P&gt;&lt;P&gt;2. ScrollElasticsearchHttp --&amp;gt; PublishKafka_0_10&lt;/P&gt;&lt;P&gt;ScrollElasticsearchHttp does fine job of fetching all the records from elastic index, but when the index content is changed(new tweets added to elasticsearch index from GetTwitter--&amp;gt;PutElasticsearch5), ScrollElasticsearchHttp not sending the updated content to Kafka.&lt;/P&gt;&lt;P&gt;In ScrollElasticsearchHttp processor If I clear state, all the documents from Elasticsearch is been sent to kafka again (same documents sent again).&lt;/P&gt;&lt;P&gt;Matt could you please help me out to sort this issue.&lt;/P&gt;</description>
      <pubDate>Wed, 23 Aug 2017 15:21:39 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Problems-configuring-FetchElasticSearch-processor/m-p/193429#M62121</guid>
      <dc:creator>naveen_mittemar</dc:creator>
      <dc:date>2017-08-23T15:21:39Z</dc:date>
    </item>
  </channel>
</rss>

