You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Nico Kruber (Jira)" <ji...@apache.org> on 2021/05/03 12:42:00 UTC

[jira] [Updated] (FLINK-16556) TopSpeedWindowing should implement checkpointing for its source

     [ https://issues.apache.org/jira/browse/FLINK-16556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nico Kruber updated FLINK-16556:
--------------------------------
    Labels: auto-deprioritized-major starter  (was: auto-deprioritized-major)

> TopSpeedWindowing should implement checkpointing for its source
> ---------------------------------------------------------------
>
>                 Key: FLINK-16556
>                 URL: https://issues.apache.org/jira/browse/FLINK-16556
>             Project: Flink
>          Issue Type: Bug
>          Components: Examples
>    Affects Versions: 1.10.0
>            Reporter: Nico Kruber
>            Priority: Minor
>              Labels: auto-deprioritized-major, starter
>
> {\{org.apache.flink.streaming.examples.windowing.TopSpeedWindowing.CarSource}} does not implement checkpointing of its state, namely the current speeds and distances per car. The main problem with this is that the window trigger only fires if the new distance has increased by at least 50 but after restore, it will be reset to 0 and could thus not produce output for a while.
>  
> Either the distance calculation could use {{Math.abs}} or the source needs proper checkpointing. Optionally with allowing the number of cars to increase/decrease.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)