You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2022/03/13 17:26:00 UTC
[jira] [Commented] (BEAM-13572) Flink runner does not support PerKeyOrdering
[ https://issues.apache.org/jira/browse/BEAM-13572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17505868#comment-17505868 ]
Beam JIRA Bot commented on BEAM-13572:
--------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it has been labeled "stale-P2". If this issue is still affecting you, we care! Please comment and remove the label. Otherwise, in 14 days the issue will be moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed explanation of what these priorities mean.
> Flink runner does not support PerKeyOrdering
> --------------------------------------------
>
> Key: BEAM-13572
> URL: https://issues.apache.org/jira/browse/BEAM-13572
> Project: Beam
> Issue Type: New Feature
> Components: runner-flink
> Reporter: Kyle Weaver
> Priority: P2
> Labels: stale-P2
>
> These tests were newly added and do not pass on the Flink runner. They can be excluded for now.
> org.apache.beam.sdk.transforms.PerKeyOrderingTest.testSingleCallOrderingWithShuffle
> org.apache.beam.sdk.transforms.PerKeyOrderingTest.testSingleCallOrderingWithoutShuffle
> java.lang.AssertionError: Verify/ParMultiDo(Verify).output:
> Expected: iterable with items [<KV{k1, true}>, <KV{k2, true}>, <KV{k3, true}>, <KV{k4, true}>, <KV{k5, true}>, <KV{k6, true}>, <KV{k7, true}>, <KV{k8, true}>, <KV{k9, true}>, <KV{k10, true}>] in any order
> but: not matched: <KV{k10, false}>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)