beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ahmet Altay (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BEAM-2600) Artifact for Python SDK harness that can be referenced in pipeline definition
Date Wed, 12 Jul 2017 02:54:00 GMT

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

Ahmet Altay commented on BEAM-2600:
-----------------------------------

cc: [~tvalentyn]

We might consider generalizing the dataflow runner option {{worker_harness_container_image}}.
Is there an equivalent for this today for <java sdk harness>?

> 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 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.



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

Mime
View raw message