Re: [DISCUSS] Towards a leaner flink-dist

Posted by Jamie Grier-2 on
URL: http://deprecated-apache-flink-user-mailing-list-archive.369.s1.nabble.com/DISCUSS-Towards-a-leaner-flink-dist-tp25615p25628.html

I'm not sure if this is required.  It's quite convenient to be able to just grab a single tarball and you've got everything you need.

I just did this for the latest binary release and it was 273MB and took about 25 seconds to download.  Of course I know connection speeds vary quite a bit but I don't think 273 MB seems onerous to download and I like the simplicity of it the way it is.

On Fri, Jan 18, 2019 at 3:34 AM Fabian Hueske <[hidden email]> wrote:

Hi Chesnay,

Thank you for the proposal.

I think this is a good idea.

We follow a similar approach already for Hadoop dependencies and connectors (although in application space).

+1

Fabian

Am Fr., 18. Jan. 2019 um 10:59 Uhr schrieb Chesnay Schepler <[hidden email]>:

Hello,

the binary distribution that we release by now contains quite a lot of
optional components, including various filesystems, metric reporters and
libraries. Most users will only use a fraction of these, and as such
pretty much only increase the size of flink-dist.

With Flink growing more and more in scope I don't believe it to be
feasible to ship everything we have with every distribution, and instead
suggest more of a "pick-what-you-need" model, where flink-dist is rather
lean and additional components are downloaded separately and added by
the user.

This would primarily affect the /opt directory, but could also be
extended to cover flink-dist. For example, the yarn and mesos code could
be spliced out into separate jars that could be added to lib manually.

Let me know what you think.

Regards,

Chesnay