[
https://issues.apache.org/jira/browse/BEAM-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15357786#comment-15357786
]
ASF GitHub Bot commented on BEAM-403:
-------------------------------------
GitHub user silviulica opened a pull request:
https://github.com/apache/incubator-beam/pull/569
[BEAM-403] Get current SDK package from PyPI instead of GitHub
With this change we support (in the DataflowPipelineRunner) getting the SDK
package from PyPI where we will release Google packages bundling Apache Beam
SDK code. This needs to change since currently we get this package from the old
SDK repo (before we moved to Apache Beam).
The CL also has support for computing the proper container version to be
used for remote execution and in particular supports the scenario of running a
non-Google wrapped Apache Beam SDK which is needed to run E2E tests in the
Apache infrastructure. For this latter case the container version is 'latest'
which works well for running E2E tests at HEAD.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/silviulica/incubator-beam sdktarball
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-beam/pull/569.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 #569
----
commit 5d8a6f106ab711c700ee91548eac6f16a5b15b2d
Author: Silviu Calinoiu <silv...@google.com>
Date: 2016-06-30T20:04:23Z
Get current SDK package from PyPI instead of GitHub
----
> Support staging SDK packages from PyPI for remote execution
> -----------------------------------------------------------
>
> Key: BEAM-403
> URL: https://issues.apache.org/jira/browse/BEAM-403
> Project: Beam
> Issue Type: Bug
> Components: runner-dataflow
> Reporter: Silviu Calinoiu
> Assignee: Davor Bonaci
> Priority: Minor
>
> Currently the dataflow runner will pickup the SDK tarball from the old github
> repo and stage it. We need to pick it up from PyPI (where packages will be
> released) and stage it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
