[
https://issues.apache.org/jira/browse/NIFI-4325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16327257#comment-16327257
]
ASF GitHub Bot commented on NIFI-4325:
--------------------------------------
Github user MikeThomsen commented on the issue:
https://github.com/apache/nifi/pull/2113
@mattyb149 I've been thinking about what to do with this PR, and I think it
needs to be put into a new NAR. I'm thinking "nifi-elasticsearch-restapi.nar"
or something like that. What I'd ideally like to do is position this to be a
new package that does full CRUD using only the official REST API from Elastic
Co.
It might also help with the issue that @joewitt raised about the sizing
because the current mix of ElasticSearch processors use different toolkits
which needlessly raises the size of the NARs.
Thoughts?
> 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)
