You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/10/09 22:39:00 UTC
[jira] [Commented] (BEAM-2600) Python SDK harness container
[ https://issues.apache.org/jira/browse/BEAM-2600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16197818#comment-16197818 ]
ASF GitHub Bot commented on BEAM-2600:
--------------------------------------
GitHub user herohde opened a pull request:
https://github.com/apache/beam/pull/3965
[BEAM-2600] Add minimal python SDK harness container
The container image does not support requirements files, main sessions, etc yet.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/herohde/beam containers
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/beam/pull/3965.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3965
----
commit 56da326f04020ee3bae197177d1f541dc35c6f2d
Author: Henning Rohde <he...@google.com>
Date: 2017-10-09T22:28:25Z
[BEAM-2600] Add minimal python SDK harness container
----
> 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
>
> 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)