[
https://issues.apache.org/jira/browse/EDGENT-368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15832866#comment-15832866
]
Otis Gospodnetic commented on EDGENT-368:
-----------------------------------------
Thanks
bq. Is just sample code / recipies needed?
What I was hoping was that you could include the Elasticsearch connector into
Edgent itself. I saw you have other connectors... aha, here, from FAQ:
{quote}
What connectors does Apache Edgent support?
Edgent supports connectors for MQTT, HTTP, JDBC, File, Apache Kafka and IBM
Watson IoT Platform. Edgent is extensible; you can add the connector of your
choice.
{quote}
... so I was hoping you could add Elasticsearch connector, which others could
use, too.
> Implement Elasticsearch output connector
> ----------------------------------------
>
> Key: EDGENT-368
> URL: https://issues.apache.org/jira/browse/EDGENT-368
> Project: Edgent
> Issue Type: New Feature
> Components: Connectors
> Reporter: Otis Gospodnetic
> Labels: connector, elasticsearch
> Fix For: Apache Edgent 1.1.0
>
>
> It would be great to be able to write data to Elasticsearch (bulk) API.
> This connector should use the ES the ES HTTP client, not TransportClient (TC
> has issues with things like different client vs. server library versions, so
> should be avoided and the ES HTTP client, written in Java, was written to
> avoid these TC issues)
> Once such connector exists one could use it not only writing to their own ES
> cluster, but also services that expose the ES API, like Logsene
> (http://sematext.com/logsene) and others.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
