[
https://issues.apache.org/jira/browse/BEAM-3536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17131772#comment-17131772
]
Beam JIRA Bot commented on BEAM-3536:
-------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it
has been labeled "stale-P2". If this issue is still affecting you, we care!
Please comment and remove the label. Otherwise, in 14 days the issue will be
moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed
explanation of what these priorities mean.
> JobService#prepareJob should be one-to-many with JobService#run
> ---------------------------------------------------------------
>
> Key: BEAM-3536
> URL: https://issues.apache.org/jira/browse/BEAM-3536
> Project: Beam
> Issue Type: Bug
> Components: runner-core
> Reporter: Thomas Groh
> Priority: P2
> Labels: stale-P2
>
> More specifically, prepare should not require a job; instead, it should
> return endpoints for any pre-job work that the client must perform (e.g.
> staging artifacts). Once the client has completed any pre-job work, those
> endpoints should return tokens by which the results of the pre-job work can
> be referenced. #run should then consume those tokens and use them to ensure
> that those results are available during execution.
>
> The simple example is that #prepare should return an artifact staging
> endpoint, and #run should take tokens returned by that endpoint that it can
> understand when executing the job. This permits multiple pipelines to be run
> with the same artifacts, among other benefits, and reduces the statefulness
> of the prepare-run call sequence.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)