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

Posted to commits@beam.apache.org by "Kenneth Knowles (JIRA)" <ji...@apache.org> on 2018/05/29 22:34: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=16494388#comment-16494388 ] 

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

I don't totally understand this. The "translation" utilities seem like their main purpose is to convert SDK construction classes and protos? Do you mean "pipeline surgery" and such things? If so, do you have a chance to take a look? It seems like you have some deeper insight.

> 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
>            Assignee: Ben Sidhom
>            Priority: Major
>
> 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
(v7.6.3#76005)