[
https://issues.apache.org/jira/browse/BEAM-10308?focusedWorklogId=456921&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-456921
]
ASF GitHub Bot logged work on BEAM-10308:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 10/Jul/20 00:49
Start Date: 10/Jul/20 00:49
Worklog Time Spent: 10m
Work Description: tvalentyn edited a comment on pull request #12196:
URL: https://github.com/apache/beam/pull/12196#issuecomment-656278107
This change is currently is not in RC1, and we can consider if for RC2 if
there has to be an RC2. The release guildeline clearly say that bugs in new
functionality should not be blocking the release. I have applied the same
criteria to at least 3 or 4 other CP requests, so it would not be fair to have
to select which new features are worth delaying the release and which are not.
Also, are we confident that the fix would not introduce new issues given that
it was merged recently?
----------------------------------------------------------------
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: 456921)
Time Spent: 5h 40m (was: 5.5h)
> 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
> Fix For: 2.24.0
>
> Time Spent: 5h 40m
> 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)
