You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Robert Metzger (JIRA)" <ji...@apache.org> on 2019/02/28 15:48:00 UTC

[jira] [Updated] (FLINK-10831) Consider making processing time monotonically increasing by default

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

Robert Metzger updated FLINK-10831:
-----------------------------------
    Component/s: Runtime / Operators

> Consider making processing time monotonically increasing by default
> -------------------------------------------------------------------
>
>                 Key: FLINK-10831
>                 URL: https://issues.apache.org/jira/browse/FLINK-10831
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / Operators
>            Reporter: Andrey Zagrebin
>            Priority: Major
>
> At the moment, the processing time is basically implemented in a fixed way as 
> System.currentTimeMillis() and not configurable by users.
> The timestamp provided this way is not guaranteed to be monotonically increasing. It can jump back for a while because of possible periodic synchronisation of local clock with other more accurate system. It can be a problem for application business logic if we say that the general notion of time is that it always increases.
> We can change SystemProcessingTimeService to emit only timestamp which is not less than the latest emitted one, at least for current JVM process.
> This change in behaviour can be also configurable if somebody e.g. relies on rather accurate time.
> Other option is that if user needs monotonic processing time then custom processing time service should be provided as suggested in FLINK-10830.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)