Github user asfgit closed the pull request at:
https://github.com/apache/flume/pull/237
---
Github user asfgit closed the pull request at:
https://github.com/apache/flume/pull/233
---
I agree with the above... the JAR hell we are currently in seems mostly
unresolvable and shedding dependencies seems like a reasonable choice
regardless of whether we implement an isolated classloader or not.
Mike
On Mon, Nov 19, 2018 at 6:02 AM Ferenc Szabo wrote:
> Hi all,
>
> I somewhat
Hi all,
I somewhat agree with Helmut.
I think we should detach every component from the framework and provide an
isolated classloader for them to avoid the dependency issues we have now.
Basically, flume itself should be just the framework and every
source/sink/channel/interceptor/etc would come
Hi all,
What are we doing with integrations having no maintainer?
An example is the morphline sink. It supports Solr 4.3 and Apache has already
relased Solr 7.5.0.
Kite SDK is at 1.1.
Seems that no one is taking care of it.
On the other site we are still "supporting" Elasticsearch 0.90.1,
