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

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

                Author: ASF GitHub Bot
            Created on: 25/Jun/20 02:00
            Start Date: 25/Jun/20 02:00
    Worklog Time Spent: 10m 
      Work Description: TheNeuralBit commented on pull request #12067:
URL: https://github.com/apache/beam/pull/12067#issuecomment-649168647


   I have a POC working that solves the problem by fixing all of the component 
IDs in the external transforms in `to_runner_api()`. It feels pretty 
error-prone, but it doesn't maintain any global state, and keeps all of the 
special logic within ExternalTransform. I'll clean it up and push it here 
tomorrow morning.


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


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

    Worklog Id:     (was: 450777)
    Time Spent: 1h  (was: 50m)

> Component id assignement is not consistent across PipelineContext instances
> ---------------------------------------------------------------------------
>
>                 Key: BEAM-10308
>                 URL: https://issues.apache.org/jira/browse/BEAM-10308
>             Project: Beam
>          Issue Type: Bug
>          Components: cross-language, sdk-py-core
>            Reporter: Brian Hulette
>            Assignee: Brian Hulette
>            Priority: P1
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> The "unique ref" ids used in PipelineContext are generated on the fly, which 
> can cause us to get a different id for the same component in different 
> contexts.
> This becomes a problem when ExternalTransform is used, because it creates its 
> own pipeline context for expansion. So its possible the component ids in the 
> expansion request will actually refer to an entirely different component when 
> the pipeline is finally assembled for execution.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to