[
https://issues.apache.org/jira/browse/BEAM-10308?focusedWorklogId=452702&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-452702
]
ASF GitHub Bot logged work on BEAM-10308:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 29/Jun/20 23:46
Start Date: 29/Jun/20 23:46
Worklog Time Spent: 10m
Work Description: TheNeuralBit commented on pull request #12067:
URL: https://github.com/apache/beam/pull/12067#issuecomment-651426642
Ok I think I'm finally done churning on this. Sorry for all the changes.
What I have now stores the component ids in a `ComponentIdContext` object
stored on the Pipeline. The same context is used in both
`ExternalTransform.expand` and in `Pipeline.to_runner_api`, so component ids
will be consistent across both of those functions, but everything we store in
memory will be cleaned up with the Pipeline. PTAL
----------------------------------------------------------------
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: 452702)
Time Spent: 2h 20m (was: 2h 10m)
> 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: 2h 20m
> 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)
