[jira] [Resolved] (NIFI-6070) Elasticsearch HTTP processors should use Low-level Java REST client

["Aaron Leon (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/NIFI-6070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aaron Leon resolved NIFI-6070.
------------------------------
    Resolution: Duplicate

> Elasticsearch HTTP processors should use Low-level Java REST client
> -------------------------------------------------------------------
>
>                 Key: NIFI-6070
>                 URL: https://issues.apache.org/jira/browse/NIFI-6070
>             Project: Apache NiFi
>          Issue Type: Improvement
>    Affects Versions: 1.9.0
>            Reporter: Aaron Leon
>            Priority: Major
>
> The Elasticsearch HTTP processors should use Java REST client... Either high-level (which would tie the processor to specific versions of Elasticsearch in the same way the transport client processors are, e.g. PutElasticsearch5) or the low-level, which from my understanding does not depend on a specific version of ES. The reasoning is that the current Elasticsearch HTTP processors simply use OkHTTP to hit the REST API, but this does not include critical features to a production setup such as:
>  * load balancing across all available nodes
>  * failover in case of node failures and upon specific response codes
>  * failed connection penalization (whether a failed node is retried depends on how many consecutive times it failed; the more failed attempts the longer the client will wait before trying that same node again)
>  * persistent connections
>  * trace logging of requests and responses
>  * optional automatic [discovery of cluster nodes|https://www.elastic.co/guide/en/elasticsearch/client/java-rest/current/sniffer.html]
> (source: [https://www.elastic.co/guide/en/elasticsearch/client/java-rest/current/java-rest-low.html)]
> The current PutElasticsearchHTTP processor also sends timed out requests to 'failure' queue as opposed to 'retry' which is not the correct behavior.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)