You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@beam.apache.org by "Henning Rohde (JIRA)" <ji...@apache.org> on 2017/10/10 22:20:00 UTC

[jira] [Resolved] (BEAM-2875) Portable SDK harness containers

     [ https://issues.apache.org/jira/browse/BEAM-2875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Henning Rohde resolved BEAM-2875.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 2.3.0

> Portable SDK harness containers
> -------------------------------
>
>                 Key: BEAM-2875
>                 URL: https://issues.apache.org/jira/browse/BEAM-2875
>             Project: Beam
>          Issue Type: Improvement
>          Components: beam-model
>            Reporter: Henning Rohde
>            Assignee: Henning Rohde
>              Labels: portability
>             Fix For: 2.3.0
>
>
> To allow runners to handle current and future SDK harnesses uniformly, each SDK harness must be packaged as a docker container image satisfying the contact proposed here:
>     https://s.apache.org/beam-fn-api-container-contract
> The suggested structure is to use a Dockerfile with all dependencies (JRE, python 2.7, etc) and a separate minimal "boot" program in Go that retrieves staged files and invokes the SDK-specific harness. This structure allows flexibility to set up the environment dynamically as well as code sharing across SDKs.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)