You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Aljoscha Krettek (Jira)" <ji...@apache.org> on 2020/10/01 15:19:00 UTC

[jira] [Closed] (FLINK-19319) Deprecate StreamExecutionEnvironment.setStreamTimeCharacteristic() and TimeCharacteristic

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

Aljoscha Krettek closed FLINK-19319.
------------------------------------
    Fix Version/s: 1.12.0
     Release Note: 
This is formatted in Markdown for easy inclusion in the release post.

In Flink 1.12 the default stream time characteristic has been changed to `EventTime`, thus you don't need to call this method for enabling event-time support anymore. Explicitly using processing-time windows and timers works in event-time mode. If you need to disable watermarks, please use `ExecutionConfig.setAutoWatermarkInterval(long)`. If you are using `IngestionTime`, please manually set an appropriate `WatermarkStrategy`. If you are using generic "time window" operations (for example `KeyedStream.timeWindow()` that change behaviour based on the time characteristic, please use equivalent operations that explicitly specify processing time or event time.
       Resolution: Fixed

master: f8cc82b0c7d3ddd35b17c7f6475b8908363c930a

> Deprecate StreamExecutionEnvironment.setStreamTimeCharacteristic() and TimeCharacteristic
> -----------------------------------------------------------------------------------------
>
>                 Key: FLINK-19319
>                 URL: https://issues.apache.org/jira/browse/FLINK-19319
>             Project: Flink
>          Issue Type: Sub-task
>          Components: API / DataStream
>            Reporter: Aljoscha Krettek
>            Assignee: Aljoscha Krettek
>            Priority: Major
>             Fix For: 1.12.0
>
>
> After FLINK-19317 and FLINK-19318 we don't need this setting anymore. Using (explicit) processing-time windows and processing-time timers work fine in a program that has {{EventTime}} set as a time characteristic and once we deprecate {{timeWindow()}} there are not other operations that change behaviour depending on the time characteristic so there's no need to ever change from the new default of event-time. Similarly, the {{IngestionTime}} setting can be achieved in the future by providing an ingestion-time {{WatermarkStrategy}}.



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