[
https://issues.apache.org/jira/browse/BEAM-4407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17547080#comment-17547080
]
Kenneth Knowles commented on BEAM-4407:
---------------------------------------
This issue has been migrated to https://github.com/apache/beam/issues/18867
> Artifact stager should validate the manifest at pipeline submission time.
> -------------------------------------------------------------------------
>
> Key: BEAM-4407
> URL: https://issues.apache.org/jira/browse/BEAM-4407
> Project: Beam
> Issue Type: Improvement
> Components: sdk-java-core, sdk-py-core
> Reporter: Valentyn Tymofieiev
> Priority: P3
> Labels: Clarified
>
> 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
(v8.20.7#820007)
