flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aljoscha Krettek (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (FLINK-7388) ProcessFunction.onTimer() sets processing time as timestamp
Date Tue, 24 Oct 2017 15:03:00 GMT

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

Aljoscha Krettek closed FLINK-7388.
-----------------------------------
      Resolution: Fixed
    Release Note: The timestamp of elements emitted from ProcessFunction.onTimer() is no longer
set to the timestamp of the timestamp of the timer if the firing timer is a processing-time
timer.

Implemented in 904c95104d70f483bc79f98a35b64ec46c7f6a80.

> ProcessFunction.onTimer() sets processing time as timestamp
> -----------------------------------------------------------
>
>                 Key: FLINK-7388
>                 URL: https://issues.apache.org/jira/browse/FLINK-7388
>             Project: Flink
>          Issue Type: Improvement
>          Components: DataStream API
>    Affects Versions: 1.4.0, 1.3.2
>            Reporter: Fabian Hueske
>            Assignee: Bowen Li
>             Fix For: 1.4.0
>
>
> The {{ProcessFunction.onTimer()}} method sets the current processing time as event-time
timestamp when it is called from a processing time timer.
> I don't think this behavior is useful. Processing time timestamps won't be aligned with
watermarks and are not deterministic. The only reason would be to have _some_ value in the
timestamp field. However, the behavior is very subtle and might not be noticed by users.
> IMO, it would be better to erase the timestamp. This will cause downstream operator that
rely on timestamps to fail and notify the users that the logic they implemented was probably
not what they intended to do.
> What do you think [~aljoscha]?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message