[ 
https://issues.apache.org/jira/browse/BEAM-3971?focusedWorklogId=117549&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-117549
 ]

ASF GitHub Bot logged work on BEAM-3971:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 29/Jun/18 19:18
            Start Date: 29/Jun/18 19:18
    Worklog Time Spent: 10m 
      Work Description: bsidhom commented on issue #5833: [BEAM-3971, 
BEAM-4284] Remove fromProto for Pipeline and PTransform translation.
URL: https://github.com/apache/beam/pull/5833#issuecomment-401449281
 
 
   I suspect this will break the non-portable Flink translator because it 
forces a proto round trip. It may be sufficient to just remove that round trip, 
but it may be a much more involved fix.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 117549)
    Time Spent: 0.5h  (was: 20m)

> 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
>          Time Spent: 0.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
(v7.6.3#76005)

Reply via email to