edgent-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (EDGENT-368) Implement Elasticsearch output connector
Date Sat, 21 Jan 2017 17:53:26 GMT

    [ https://issues.apache.org/jira/browse/EDGENT-368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15833078#comment-15833078

Daniel John Debrunner commented on EDGENT-368:

[~otis@apache.org] Please consider getting involved with Edgent and implementing the Elasticsearch
connector yourself.

> 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

View raw message