[
https://issues.apache.org/jira/browse/BEAM-4130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16581161#comment-16581161
]
Maximilian Michels commented on BEAM-4130:
------------------------------------------
>From the design document ( https://s.apache.org/beam-job-api ) it looks like
>Docker has been chosen as the preferred approach. There is already a runner
>for testing purposes which brings up a JobService/ArtifactService, see
>{{TestPortableRunner}}. The goal is to have a similar functionality when
>executing in non-testing mode.
I agree with [~thw] that the Docker container shouldn't be the only way. Users
should be able to manually run the JobService and the service might be designed
to run long-term in the future.
> 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
> Assignee: Maximilian Michels
> Priority: Minor
> Time Spent: 4h 20m
> Remaining Estimate: 0h
>
> 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)
