You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Luke Cwik (Jira)" <ji...@apache.org> on 2020/08/07 22:08:00 UTC
[jira] [Updated] (BEAM-8460) Flink/Spark runner ignores
UsesStrictTimerOrdering category tests
[ https://issues.apache.org/jira/browse/BEAM-8460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Luke Cwik updated BEAM-8460:
----------------------------
Component/s: runner-spark
> Flink/Spark runner ignores UsesStrictTimerOrdering category tests
> -----------------------------------------------------------------
>
> Key: BEAM-8460
> URL: https://issues.apache.org/jira/browse/BEAM-8460
> Project: Beam
> Issue Type: Bug
> Components: runner-flink, runner-spark
> Affects Versions: 2.17.0
> Reporter: Jan Lukavský
> Priority: P2
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> BEAM-7520 introduced new set of validatesRunner tests that test that timers are fired exactly in order of increasing timestamp. Portable Flink runner fails these added tests (are currently ignored).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)