[
https://issues.apache.org/jira/browse/BEAM-10308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Hulette updated BEAM-10308:
---------------------------------
Description:
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.
> 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
>
> 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)
