[
https://issues.apache.org/jira/browse/NIFI-4325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16196896#comment-16196896
]
ASF GitHub Bot commented on NIFI-4325:
--------------------------------------
Github user mattyb149 commented on the issue:
https://github.com/apache/nifi/pull/2113
If you're looking to run integration tests against a ES instance (from the
Maven plugin), perhaps you can split out the integration tests into a new file
called ITJsonQueryElasticsearch5, rather than having the @Ignore or running
integration tests during the unit test phase. I realize the others aren't done
this way, but if that Maven plugin works well, I think we should consider a
separate Jira/PR to refactor the tests into proper integration vs unit tests,
so they can be run during their corresponding lifecycle (integration tests
aren't run during a normal test phase, e.g.)
> 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)
