[
https://issues.apache.org/jira/browse/FLUME-2225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13885822#comment-13885822
]
Edward Sargisson commented on FLUME-2225:
-----------------------------------------
> repair the backwards compatibility in all places
Where our docs say that a custom class can be specified, then we should support
that custom class in a backwards compatible fashion.
> Elasticsearch Sink for ES HTTP API
> ----------------------------------
>
> Key: FLUME-2225
> URL: https://issues.apache.org/jira/browse/FLUME-2225
> Project: Flume
> Issue Type: New Feature
> Affects Versions: v1.5.0
> Reporter: Otis Gospodnetic
> Fix For: v1.4.1, v1.5.0
>
> Attachments: FLUME-2225-0.patch, FLUME-2225-1.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)
