[ https://issues.apache.org/jira/browse/NIFI-4325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16246525#comment-16246525 ]
ASF GitHub Bot commented on NIFI-4325: -------------------------------------- Github user MikeThomsen commented on a diff in the pull request: https://github.com/apache/nifi/pull/2113#discussion_r150086797 --- Diff: nifi-assembly/pom.xml --- @@ -338,6 +338,16 @@ </dependency> <dependency> <groupId>org.apache.nifi</groupId> + <artifactId>nifi-elasticsearch-client-service-nar</artifactId> + <type>nar</type> + </dependency> +<!-- <dependency> --- End diff -- That's how I included the nar file for the client service that the new processor uses. Is there a better approach? > 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 (v6.4.14#64029)