[
https://issues.apache.org/jira/browse/BEAM-9073?focusedWorklogId=369431&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-369431
]
ASF GitHub Bot logged work on BEAM-9073:
----------------------------------------
Author: ASF GitHub Bot
Created on: 09/Jan/20 22:27
Start Date: 09/Jan/20 22:27
Worklog Time Spent: 10m
Work Description: rohdesamuel commented on issue #10541: [BEAM-9073]
Fixes order-dependence in PipelineVisitor
URL: https://github.com/apache/beam/pull/10541#issuecomment-572786060
> Wouldn't it make sense to ensure the topological visiting order in the
graph instead of making the visit order possibly random?
>
> (I ask this since some pipeline transform replacement algorithms may
assume that you first visit the composites before you have visited the children
so that replacing the higher level transform happens first).
That makes sense, but unfortunately I don't have time to implement that
larger change. I have a smaller work-around that fixes it at the
PipelineVisitor subclass that I'm using.
----------------------------------------------------------------
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:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 369431)
Time Spent: 0.5h (was: 20m)
> PipelineVisitor is topologically-order dependent
> ------------------------------------------------
>
> Key: BEAM-9073
> URL: https://issues.apache.org/jira/browse/BEAM-9073
> Project: Beam
> Issue Type: Bug
> Components: sdk-py-core
> Reporter: Sam Rohde
> Assignee: Sam Rohde
> Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The Python PipelineVisitor is topologically-order dependent and can visit the
> same transform multiple times.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
