karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Baptiste Onofré (JIRA) <j...@apache.org>
Subject [jira] [Created] (KARAF-4295) Use of Elasticsearch REST API in addition of the TransportClient (by configuration)
Date Wed, 27 Jan 2016 13:01:39 GMT
Jean-Baptiste Onofré created KARAF-4295:
-------------------------------------------

             Summary: Use of Elasticsearch REST API in addition of the TransportClient (by
configuration)
                 Key: KARAF-4295
                 URL: https://issues.apache.org/jira/browse/KARAF-4295
             Project: Karaf
          Issue Type: Improvement
          Components: decanter
            Reporter: Jean-Baptiste Onofré
            Assignee: Jean-Baptiste Onofré
             Fix For: decanter-1.0.2


Regarding elasticsearch, we can see:

https://www.elastic.co/guide/en/logstash/current/plugins-outputs-elasticsearch.html

{code}
We strongly encourage the use of HTTP over the node protocol for a number of reasons. HTTP
is only marginally slower, yet far easier to administer and work with. When using the HTTP
protocol one may upgrade Elasticsearch versions without having to upgrade Logstash in lock-step.
For those still wishing to use the node or transport protocols please see the logstash-output-elasticsearch_java
plugin.
{code}

So, it makes sense to allow users to use the REST API (instead of the TransportClient), by
configuration.

It would be great to be able to use HTTP URL, username, password, eventually key store (for
cert) as well.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message