[jira] [Commented] (BEAM-10794) artifact.Materialize does not return list of ArtifactInformation

["Beam JIRA Bot (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/BEAM-10794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17218409#comment-17218409 ] 

Beam JIRA Bot commented on BEAM-10794:
--------------------------------------

This issue is P2 but has been unassigned without any comment for 60 days so it has been labeled "stale-P2". If this issue is still affecting you, we care! Please comment and remove the label. Otherwise, in 14 days the issue will be moved to P3.

Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed explanation of what these priorities mean.


> 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: P2
>              Labels: stale-P2
>
> 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.3.4#803005)