[
https://issues.apache.org/jira/browse/BEAM-4130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16466508#comment-16466508
]
Thomas Weise commented on BEAM-4130:
------------------------------------
I don't think we should assume packaging as a Docker container, it is one
possible deployment option, but not the only one. Like in the prototype, the
user may provision the job service separately, and point the SDK to the
endpoint:
[https://github.com/bsidhom/beam/blob/hacking-job-server/sdks/python/flink-example.py]
> Portable Flink runner JobService entry point in a Docker container
> ------------------------------------------------------------------
>
> Key: BEAM-4130
> URL: https://issues.apache.org/jira/browse/BEAM-4130
> Project: Beam
> Issue Type: New Feature
> Components: runner-flink
> Reporter: Ben Sidhom
> Priority: Minor
>
> The portable Flink runner exists as a Job Service that runs somewhere. We
> need a main entry point that itself spins up the job service (and artifact
> staging service). The main program itself should be packaged into an uberjar
> such that it can be run locally or submitted to a Flink deployment via `flink
> run`.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
