flink-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stephan Ewen <se...@apache.org>
Subject Re: [DISCUSS] Break up streaming connectors into subprojects
Date Wed, 08 Apr 2015 11:33:40 GMT
Exactly each streaming connector would be a separate jar:

  - stream-connector-kafka
  - stream-connector-rabbitmq
  - stream-connector-flume
  - ...

On Tue, Apr 7, 2015 at 10:59 PM, Henry Saputra <henry.saputra@gmail.com>
wrote:

> Would this proposal also include packaging streaming connectors into
> separate source and binary jars?
>
> - Henry
>
> On Tue, Apr 7, 2015 at 12:21 PM, Stephan Ewen <sewen@apache.org> wrote:
> > What do you think about dividing the streaming connectors project into
> > various smaller projects, basically one per connector?
> >
> > I am personally always happy when projects offer me artifacts that
> contain
> > what I need, and not a lot of other unnecessary dependencies as well
> >
> > Many people using the streaming connectors as a dependency in other
> setups
> > will have to define a long list of exclusions, to get rid of all
> > dependencies (and their transitives) that they do not need.
> >
> > We have seen how these "super fat" dependencies cause trouble, for
> example
> > at the case of Hadoop 1 where everything was one artifact and how much
> > easier it is with Hadoop 2 where we can use subcomponents as
> dependencies.
> >
> > What do you think?
> >
> > Stephan
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message