You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Kenneth Knowles (JIRA)" <ji...@apache.org> on 2017/10/10 22:01:00 UTC

[jira] [Updated] (BEAM-2600) Python SDK harness container

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

Kenneth Knowles updated BEAM-2600:
----------------------------------
    Priority: Major  (was: Minor)

> Python SDK harness container
> ----------------------------
>
>                 Key: BEAM-2600
>                 URL: https://issues.apache.org/jira/browse/BEAM-2600
>             Project: Beam
>          Issue Type: Sub-task
>          Components: sdk-py-core
>            Reporter: Kenneth Knowles
>            Assignee: Henning Rohde
>              Labels: portability
>             Fix For: 2.3.0
>
>
> In order to build a pipeline that invokes a Python UDF, we need to be able to construct something like this:
> {code}
> SdkFunctionSpec {
>   environment = <python SDK harness>,
>   spec = {
>     urn = <python SDK pickled DoFn>,
>     data = <pickled DoFn>
>   }
> }
> {code}
> I could be out of date, but based on a couple of conversations I do not know that there exists anything we can put for "<python SDK harness>" today. For prototyping, it could be just a symbol that runners have to know. But eventually it should be something that runners can instantiate without knowing anything about the SDK that put it there. I imagine it may encompass "custom containers" eventually, though that doesn't block anything immediately.
> Update 9/11/2017: this issue will track the first portable SDK harness as per https://s.apache.org/beam-fn-api-container-contract, incl shared boot code and maven integration to build Go and Docker container images.



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