[jira] [Commented] (BEAM-2600) Artifact for Python SDK harness that can be referenced in pipeline definition

["Henning Korsholm Rohde (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/BEAM-2600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16123909#comment-16123909 ] 

Henning Korsholm Rohde commented on BEAM-2600:
----------------------------------------------

Proposal for a container contract here: https://s.apache.org/beam-fn-api-container-contract

> Artifact for Python SDK harness that can be referenced in pipeline definition
> -----------------------------------------------------------------------------
>
>                 Key: BEAM-2600
>                 URL: https://issues.apache.org/jira/browse/BEAM-2600
>             Project: Beam
>          Issue Type: New Feature
>          Components: sdk-py
>            Reporter: Kenneth Knowles
>            Assignee: Ahmet Altay
>              Labels: beam-python-everywhere
>
> 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.



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