You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Thomas Weise (JIRA)" <ji...@apache.org> on 2018/08/21 17:47:00 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16587799#comment-16587799 ]
Thomas Weise commented on BEAM-5187:
------------------------------------
Changed title/description so there is no confusion with the existing InProcessServerFactory that is used for testing. It would be possible to execute Java pipelines within the task manager using that approach, the goal here is external process for different language environment.
> 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: Kenneth Knowles
> Priority: Minor
>
> 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)