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

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

                Author: ASF GitHub Bot
            Created on: 23/Mar/18 18:20
            Start Date: 23/Mar/18 18:20
    Worklog Time Spent: 10m 
      Work Description: tgroh commented on issue #4938: [BEAM-3913] Allow 
Fusion to Continue with unknown PTransforms
URL: https://github.com/apache/beam/pull/4938#issuecomment-375757466
 
 
   Added a test.
   
   Only runner-executed unknown URNs are allowed right now in the fuser, as we 
assume that the runner can handle them properly

----------------------------------------------------------------
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: 83733)
    Time Spent: 40m  (was: 0.5h)

> Support custom runner primitives in Fusion
> ------------------------------------------
>
>                 Key: BEAM-3913
>                 URL: https://issues.apache.org/jira/browse/BEAM-3913
>             Project: Beam
>          Issue Type: Improvement
>          Components: runner-core
>            Reporter: Thomas Groh
>            Assignee: Thomas Groh
>            Priority: Major
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> Effectively, register runner-provided transform URNs in the 
> GreedyPCollectionFusers to understand runner-specific primitives, and don't 
> ever fuse them.
>  
> It's probably appropriate to continue to crash when encountering truly 
> unknown URNs



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to