[
https://issues.apache.org/jira/browse/NIFI-4325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16413732#comment-16413732
]
ASF GitHub Bot commented on NIFI-4325:
--------------------------------------
Github user MikeThomsen commented on the issue:
https://github.com/apache/nifi/pull/2113
@JPercivall I just got done testing it w/ X-Pack for SSL and u/p auth based
on Elastic docs. Everything was in working order there. [Steps if you want to
validate](https://www.elastic.co/guide/en/elasticsearch/reference/6.2/configuring-tls.html)
I also added the documentation there. Sorry about that.
AFAIK, that warning is going to be more of a polite warning than a real
"here be dragons" sort of thing because IIRC ES limits you to 10k results
unless you explicitly up the number in the index configuration. Probably a good
reminder, but I doubt anyone is going to blow up their NiFi installation
without having to take deliberate steps to facilitate that.
> Create a new ElasticSearch processor that supports the JSON DSL
> ---------------------------------------------------------------
>
> Key: NIFI-4325
> URL: https://issues.apache.org/jira/browse/NIFI-4325
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Mike Thomsen
> Priority: Minor
>
> The existing ElasticSearch processors use the Lucene-style syntax for
> querying, not the JSON DSL. A new processor is needed that can take a full
> JSON query and execute it. It should also support aggregation queries in this
> syntax. A user needs to be able to take a query as-is from Kibana and drop it
> into NiFi and have it just run.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
