[
https://issues.apache.org/jira/browse/BEAM-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15368943#comment-15368943
]
Jean-Baptiste Onofré commented on BEAM-320:
-------------------------------------------
I think it's actually a mix of two:
- a module can be define a distribution
- the module can be called and an uver jar provided via a profile
> Provide Beam keyturn binary distributions embedding runners and execution
> runtime
> ---------------------------------------------------------------------------------
>
> Key: BEAM-320
> URL: https://issues.apache.org/jira/browse/BEAM-320
> 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
(v6.3.4#6332)
