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

Posted to issues@beam.apache.org by "Kenneth Knowles (Jira)" <ji...@apache.org> on 2020/10/09 16:39:00 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=17211153#comment-17211153 ] 

Kenneth Knowles commented on BEAM-3971:
---------------------------------------

Closing because this looks obsolete.

> 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: P3
>          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)