[
https://issues.apache.org/jira/browse/BEAM-10794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Burke updated BEAM-10794:
--------------------------------
Fix Version/s: Not applicable
Resolution: Fixed
Status: Resolved (was: Open)
Looks like this was resolved at some point. The role is maintained at this
point.
https://github.com/apache/beam/blob/56e5c2c6ca574c969b53a72be51be1fa04c88786/sdks/go/pkg/beam/artifact/materialize.go#L116
> artifact.Materialize does not return list of ArtifactInformation
> ----------------------------------------------------------------
>
> Key: BEAM-10794
> URL: https://issues.apache.org/jira/browse/BEAM-10794
> Project: Beam
> Issue Type: Bug
> Components: sdk-go
> Reporter: Kevin Sijo Puthusseri
> Priority: P3
> Fix For: Not applicable
>
>
> As of now, artifact.Materialize returns []*jobpb.ArtifactMetadata which
> contains only the name of the artifact and hash. While this is important, the
> role information returned by the expansion service is lost. The Java harness
> fails without a role urn. For now, since the role urn generally is
> beam:artifact:role:staging_to:v1, I add it anyways and the pipeline runs. In
> the case where the role wasn't in fact what I am adding or if there is code
> dependent on role payload then it’ll fail. Moreover, this exact call is used
> by boot.go for each sdk’s worker container. Since I lack context, I don’t
> know if it is as easy or small an impact change as it seems at first glance.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
