You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@beam.apache.org by "Henning Rohde (JIRA)" <ji...@apache.org> on 2018/05/25 00:56:00 UTC

[jira] [Assigned] (BEAM-4408) Go SDK artifact staging client should validate the manifest

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

Henning Rohde reassigned BEAM-4408:
-----------------------------------

    Assignee:     (was: Henning Rohde)

> Go SDK artifact staging client should validate the manifest
> -----------------------------------------------------------
>
>                 Key: BEAM-4408
>                 URL: https://issues.apache.org/jira/browse/BEAM-4408
>             Project: Beam
>          Issue Type: Improvement
>          Components: sdk-go
>            Reporter: Henning Rohde
>            Priority: Minor
>
> One step of executing a Beam pipeline is staging pipeline dependencies to the runner, for Python SDK example see: [https://github.com/apache/beam/blob/1e2218aebf4902ca2f9107c885ff7ef0e1ef6eb8/sdks/python/apache_beam/runners/portability/stager.py#L83] and it's implementations. 
> As a part of this process, we create a manifest of all staged artifacts. We should identify the requirements that constitute correctness of the manifest (for example, artifacts do not repeat twice, see also: https://github.com/apache/beam/blob/b0b7e3bf4941f874d360923ffd1d03e38befc589/sdks/go/pkg/beam/artifact/gcsproxy/retrieval.go#L122), and verify these requirements on the SDK side at pipeline submission, to fail faster.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)