You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2020/08/18 17:07:12 UTC
[jira] [Commented] (BEAM-3971) Pipeline translation utilities
should not use SDK construction classes
[ https://issues.apache.org/jira/browse/BEAM-3971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17179786#comment-17179786 ]
Beam JIRA Bot commented on BEAM-3971:
-------------------------------------
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.
> Pipeline translation utilities should not use SDK construction classes
> ----------------------------------------------------------------------
>
> Key: BEAM-3971
> URL: https://issues.apache.org/jira/browse/BEAM-3971
> Project: Beam
> Issue Type: Bug
> Components: runner-core
> Reporter: Ben Sidhom
> Priority: P2
> Labels: stale-P2
> Time Spent: 7.5h
> Remaining Estimate: 0h
>
> In general, portable runners will require access to pipeline information not available in rehydrated pipelines while constructing physical plans. Translation utilities should operate directly on protos or on thin, information-preserving wrappers.
> The pipeline fusion utilities already operate on protos directly and can be used as an example of how this could be done.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)