[
https://issues.apache.org/jira/browse/BEAM-11784?focusedWorklogId=550436&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-550436
]
ASF GitHub Bot logged work on BEAM-11784:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 09/Feb/21 21:52
Start Date: 09/Feb/21 21:52
Worklog Time Spent: 10m
Work Description: kennknowles commented on pull request #13942:
URL: https://github.com/apache/beam/pull/13942#issuecomment-776267850
My only hesitation is that I don't see why this would ever be a `Set`. If
that was masking something weird, this will unmask it.
----------------------------------------------------------------
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: 550436)
Time Spent: 0.5h (was: 20m)
> Java pipeline proto serialization does not ensure topological ordering of
> root transforms
> -----------------------------------------------------------------------------------------
>
> Key: BEAM-11784
> URL: https://issues.apache.org/jira/browse/BEAM-11784
> Project: Beam
> Issue Type: Bug
> Components: sdk-java-core
> Reporter: Kenneth Knowles
> Assignee: Kenneth Knowles
> Priority: P1
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Seen these root orders when running {{ImpulseTest.testImpulse}}:
> - {{["Impulse", "PAssert$0", "FlatMapElements"]}}
> - {{["FlatMapElements", "PAssert$0", "Impulse"]}}
> Pipeline is:
> {code}
> PCollection<Integer> result =
> p.apply(Impulse.create())
> .apply(
> FlatMapElements.into(TypeDescriptors.integers())
> .via(impulse -> Arrays.asList(1, 2, 3)));
> PAssert.that(result).containsInAnyOrder(1, 2, 3);
> {code}
> The topological order is linear and is neither of the above.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
