You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Maximilian Michels (JIRA)" <ji...@apache.org> on 2018/10/03 10:37:00 UTC
[jira] [Resolved] (BEAM-5187) Create a ProcessJobBundleFactory for
non-dockerized SDK harness
[ https://issues.apache.org/jira/browse/BEAM-5187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maximilian Michels resolved BEAM-5187.
--------------------------------------
Resolution: Implemented
Fix Version/s: 2.7.0
Artifact staging is not integrated but [~thw] has tried it out and stated it is not required for his use case. We might follow up with a programmatic way to stage artifacts. Closing this for now since the basic process-based execution is in place.
> Create a ProcessJobBundleFactory for non-dockerized SDK harness
> ---------------------------------------------------------------
>
> Key: BEAM-5187
> URL: https://issues.apache.org/jira/browse/BEAM-5187
> Project: Beam
> Issue Type: New Feature
> Components: runner-core
> Reporter: Maximilian Michels
> Assignee: Maximilian Michels
> Priority: Minor
> Fix For: 2.7.0
>
> Time Spent: 6h 40m
> Remaining Estimate: 0h
>
> As discussed on the mailing list [1], we want to giver users an option to execute portable pipelines without Docker. Analog to the {{DockerJobBundleFactory}}, a {{ProcessJobBundleFactory}} could be added to directly fork SDK harness processes.
> Artifacts will be provided by an artifact directory or could be setup similar to the existing bootstrapping code ("boot.go") which we use for containers.
> The process-based execution can optionally be configured via the pipeline options.
> [1] [https://lists.apache.org/thread.html/d8b81e9f74f77d74c8b883cda80fa48efdcaf6ac2ad313c4fe68795a@%3Cdev.beam.apache.org%3E]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)