[
https://issues.apache.org/jira/browse/BEAM-4130?focusedWorklogId=112038&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-112038
]
ASF GitHub Bot logged work on BEAM-4130:
----------------------------------------
Author: ASF GitHub Bot
Created on: 14/Jun/18 20:21
Start Date: 14/Jun/18 20:21
Worklog Time Spent: 10m
Work Description: angoenka commented on issue #5493: [BEAM-4130] Add job
submission capabilities to Flink runner.
URL: https://github.com/apache/beam/pull/5493#issuecomment-397426050
@robertwb Based on the discussion in the chat thread, should we remove
BeamFileSystemArtifactSource as ArtifactRetrivalService is meant to do the same
job.
If you want we can keep it as it is as I can clean it up when I go about
removing ArtifactSource interface.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 112038)
Time Spent: 3h 50m (was: 3h 40m)
> 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
> Time Spent: 3h 50m
> 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)
