beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Frances Perry (JIRA)" <>
Subject [jira] [Commented] (BEAM-320) Provide Beam keyturn binary distributions embedding runners and execution runtime
Date Wed, 01 Jun 2016 20:32:59 GMT


Frances Perry commented on BEAM-320:

Ready to use distributions for common usage patterns sounds like a good idea -- it will make
things much easier for users. 

For the Dataflow Runner, I think Google may prefer to provide a Google-built binary distribution
based on Beam instead of providing this convenience as part of Beam, because for Google Cloud
Platform customers, we may want to package in a few additional libraries for interacting with
other Google Cloud Platform services. It doesn't sound right to complicate Beam with those

But I can definitely see there are some that would make sense as part of Beam. And in any
case, we should make all of these distributions easy to find via documentation on the Beam

(Also keep in mind, that there will be multiple SDKs, so we likely want to name things to
include both the runner and the sdk -- beam-java-spark, etc.)

> Provide Beam keyturn binary distributions embedding runners and execution runtime
> ---------------------------------------------------------------------------------
>                 Key: BEAM-320
>                 URL:
>             Project: Beam
>          Issue Type: Wish
>          Components: build-system
>            Reporter: Jean-Baptiste Onofré
>            Assignee: Jean-Baptiste Onofré
> Now, the only distribution Beam provides is the source distribution.
> For new users, it could be interesting to have ready-to-use binary distribution embedding
the SDK, a specific runner with the backend execution runtime.
> For instance, we could provide:
> - beam-spark-xxx.tar.gz containing SDK, Spark runner, Spark
> - beam-flink-xxx.tar.gz containing SDK, Flink runner, Flink
> Thoughts ?

This message was sent by Atlassian JIRA

View raw message