You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@flink.apache.org by "Kanthi Vaidya (Jira)" <ji...@apache.org> on 2024/05/04 12:14:00 UTC

[jira] [Created] (FLINK-35289) Incorrect timestamp of stream elements collected from onTimer in batch mode

Kanthi Vaidya created FLINK-35289:
-------------------------------------

             Summary: Incorrect timestamp of stream elements collected from onTimer in batch mode
                 Key: FLINK-35289
                 URL: https://issues.apache.org/jira/browse/FLINK-35289
             Project: Flink
          Issue Type: Bug
          Components: API / Core
    Affects Versions: 1.18.1
            Reporter: Kanthi Vaidya


In batch mode  all registered timers will fire at the _end of time. Given this, if a user registers a timer for Long.MAX_VALUE, the timestamp assigned to the elements that are collected from the onTimer context ends up being Long.MAX_VALUE. Ideally this should be the time when the batch actually executed  the onTimer function._



--
This message was sent by Atlassian Jira
(v8.20.10#820010)