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

Paweł updated FLUME-2225:
-------------------------

    Attachment: FLUME-2225-0.patch

I attach patch for this. There is no new sink created. Existing one was 
modified to be able to send documents to elasticsearch by two different 
clients. One of clients is Transport client and second one i REST client (using 
Jest library).

There is also possibility to change it a little as Chiwan Park suggested: 
http://mail-archives.apache.org/mod_mbox/flume-dev/201401.mbox/%3CCC8881BF-E635-430D-8D2A-F466C6C2EAAE%40icloud.com%3E

Please let me know if I should write some more detailed information about the 
change.

> Elasticsearch Sink for ES HTTP API
> ----------------------------------
>
>                 Key: FLUME-2225
>                 URL: https://issues.apache.org/jira/browse/FLUME-2225
>             Project: Flume
>          Issue Type: New Feature
>            Reporter: Otis Gospodnetic
>             Fix For: v1.4.1, v1.5.0
>
>         Attachments: FLUME-2225-0.patch
>
>
> Existing ElasticSearchSink uses ES TransportClient.  As such, one cannot use 
> the ES HTTP API, which is sometimes easier, and doesn't have issues around 
> client and server/cluster components using incompatible versions - currently, 
> both client and server/cluster need to be on the same version.
> See
> http://search-hadoop.com/m/k76HH9Te68/otis&subj=Elasticsearch+sink+that+uses+HTTP+API



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to