beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Work logged] (BEAM-3971) Pipeline translation utilities should not use SDK construction classes
Date Fri, 29 Jun 2018 22:36:00 GMT

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

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

                Author: ASF GitHub Bot
            Created on: 29/Jun/18 22:35
            Start Date: 29/Jun/18 22:35
    Worklog Time Spent: 10m 
      Work Description: lukecwik commented on issue #5833: [BEAM-3971, BEAM-4284] Remove fromProto
for Pipeline and PTransform translation.
URL: https://github.com/apache/beam/pull/5833#issuecomment-401490493
 
 
   Run Flink ValidatesRunner

----------------------------------------------------------------
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:
users@infra.apache.org


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

    Worklog Id:     (was: 117643)
    Time Spent: 2h 50m  (was: 2h 40m)

> 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: 2h 50m
>  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)

Mime
View raw message