[
https://issues.apache.org/jira/browse/FLINK-21310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-21310:
-----------------------------------
Labels: auto-deprioritized-major stale-minor (was:
auto-deprioritized-major)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> unexpected behavior of DataStream union
> ---------------------------------------
>
> Key: FLINK-21310
> URL: https://issues.apache.org/jira/browse/FLINK-21310
> Project: Flink
> Issue Type: Bug
> Components: API / DataStream
> Affects Versions: 1.12.0
> Reporter: Tianshi Zhu
> Priority: Minor
> Labels: auto-deprioritized-major, stale-minor
>
> [https://gist.github.com/tianshizz/fd1bdbcc4676783b7300984c0bf532c1]
> The gist shows three unit tests, that have different union behaviors. In the
> first one, a data stream unions with itself. In the second one, two identical
> data streams are unioned. However, the two operations will lead to different
> end results, which seems surprising to me.
> In the third test when the list is long enough, union can show
> nondeterministic behavior. When running the third test for multiple times,
> each time the test will fail with a different `i` position.
> Are these expected? Could someone help me understand the different behaviors
> here?
> Thanks!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
