[ 
https://issues.apache.org/jira/browse/NIFI-4325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16404191#comment-16404191
 ] 

ASF GitHub Bot commented on NIFI-4325:
--------------------------------------

Github user JPercivall commented on a diff in the pull request:

    https://github.com/apache/nifi/pull/2113#discussion_r175304809
  
    --- Diff: 
nifi-nar-bundles/nifi-elasticsearch-bundle/nifi-elasticsearch-client-service/src/main/java/org/apache/nifi/elasticsearch/ElasticSearchClientServiceImpl.java
 ---
    @@ -121,7 +119,7 @@ private void setupClient(ConfigurationContext context) 
throws Exception {
     
             RestClientBuilder builder = RestClient.builder(hh)
                     .setHttpClientConfigCallback(httpClientBuilder -> {
    -                    if (sslService != null) {
    +                    if (sslService != null && 
sslService.isKeyStoreConfigured() && sslService.isTrustStoreConfigured()) {
                             try {
    --- End diff --
    
    Given that this is a callback, we probably want to move as much of the 
logic out of here as possible. That way we can better handle any errors and 
reduce performance cost if this is called multiple times. Currently, if there 
is an error which hits line 145, the error will be caught and logged but it 
will continue to create the http client as if nothing went wrong. What we 
should probably do is have a final SSLContext which gets created above, 
bubbling up any errors so that the CS doesn't enable in a bad state, and set 
the SSLContext same way as below in the context.


> 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)

Reply via email to