[
https://issues.apache.org/jira/browse/BEAM-4130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16581180#comment-16581180
]
Maximilian Michels edited comment on BEAM-4130 at 8/15/18 3:13 PM:
-------------------------------------------------------------------
To add to the above, shouldn't the behavior for the JobService be the same as
for the SDK Harness? Currently, the Python SDK Harness is either started from a
Docker container or supplied via a remote URL. Similarly, the JobService could
either be brought up using Docker or assumed to be running at some address.
was (Author: mxm):
To add to the above, shouldn't the behavior for the JobService be the same as
for the SDK Harness? Currently, the Python SDK Harness is either started from a
Docker container or supplied via a remote URL. Similarly, the JobService is
either brought up using Docker or assumed to be running at some address.
> 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)
