[
https://issues.apache.org/jira/browse/NIFI-4325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16327294#comment-16327294
]
ASF GitHub Bot commented on NIFI-4325:
--------------------------------------
Github user mattyb149 commented on the issue:
https://github.com/apache/nifi/pull/2113
Makes sense to me, we had to do the same with Elasticsearch 2.x and 5.x
because of the difference in transport client versions. As folks move
exclusively to ES5+, it would be nice to deprecate the other NARs and go
forward with versions of all the processors (Get,Put,Search, etc.) using the
new Java client.
> 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)
