[
https://issues.apache.org/jira/browse/FLUME-2921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15374402#comment-15374402
]
Lior Zeno commented on FLUME-2921:
----------------------------------
I think we should avoid a custom classloader, and simply shade/remove
dependencies as necessary. If a user wants to run both ES and HDFS sinks in the
same agent, he would have to shade one of them. This is perfectly acceptable.
I think that the best thing to do right now is to block this issue until we
clean our public API. In the meantime, users may use the REST client with 1.x
and up clusters.
Since this is a popular sink, there are other projects on GitHub that
implements elasticsearch 2.x support on Flume (obviously, by breaking
backwards-compatibility), e.g.
https://github.com/arberzal/flume-ng-elasticsearch2-sink.
> Support Elasticsearch 2.0+
> --------------------------
>
> Key: FLUME-2921
> URL: https://issues.apache.org/jira/browse/FLUME-2921
> Project: Flume
> Issue Type: Improvement
> Components: Sinks+Sources
> Reporter: Lior Zeno
> Assignee: Lior Zeno
> Fix For: v1.7.0
>
> Attachments: FLUME-2921-0.patch, FLUME-2921-1.patch
>
>
> Elasticsearch sink supports an ancient version of ES. We should make the sink
> work with newer versions of Elasticsearch.
> I attached a patch for that. Please note that this involves upgrading netty
> and guava.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
