You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2016/02/12 18:05:18 UTC
[jira] [Resolved] (KARAF-4295) Use of Elasticsearch REST API in
addition of the TransportClient (by configuration)
[ https://issues.apache.org/jira/browse/KARAF-4295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré resolved KARAF-4295.
-----------------------------------------
Resolution: Fixed
> 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
> Affects Versions: decanter-1.0.1
> Reporter: Jean-Baptiste Onofré
> Assignee: Jean-Baptiste Onofré
> Fix For: decanter-1.1.0
>
>
> 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)