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/27 09:58:00 UTC
[jira] [Closed] (FLINK-19479) Allow explicitly configuring time
behaviour on KeyedStream.intervalJoin()
[ https://issues.apache.org/jira/browse/FLINK-19479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aljoscha Krettek closed FLINK-19479.
------------------------------------
Fix Version/s: 1.12.0
Release Note: Before Flink 1.12 the `KeyedStream.intervalJoin()` operation was changing behavior based on the globally set Stream TimeCharacteristic. In Flink 1.12 we introduced explicit `inProcessingTime()` and `inEventTime()` methods on `IntervalJoin` and the join no longer changes behaviour based on the global characteristic.
Resolution: Fixed
master: dbf772fe83fbef8b720e7dfd087092248f185c5b
> Allow explicitly configuring time behaviour on KeyedStream.intervalJoin()
> -------------------------------------------------------------------------
>
> Key: FLINK-19479
> URL: https://issues.apache.org/jira/browse/FLINK-19479
> Project: Flink
> Issue Type: Sub-task
> Components: API / DataStream
> Reporter: Aljoscha Krettek
> Assignee: Nicholas Jiang
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.12.0
>
>
> With the deprecation of {{StreamExecutionEnvironment.setStreamTimeCharacteristic()}} in FLINK-19319 we need a way of explicitly configuring the time behaviour of these join operations. Currently, all join operations use the characteristic to configure themselves.
> Alternatively, we might consider removing/deprecating these join operations.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)