[ https://issues.apache.org/jira/browse/FLINK-15339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17026482#comment-17026482 ]
Timo Walther commented on FLINK-15339: -------------------------------------- Actually, the interval joins in DataStream API came after Table API but could not named like Table API because of legacy reasons. I don't have a strong opinion here. But we can do it for consistency. > Correct the terminology of "Time-windowed Join" to "Interval Join" in Table > API & SQL > ------------------------------------------------------------------------------------- > > Key: FLINK-15339 > URL: https://issues.apache.org/jira/browse/FLINK-15339 > Project: Flink > Issue Type: Sub-task > Components: Documentation > Reporter: Jark Wu > Priority: Major > Fix For: 1.10.0 > > > Currently, in the docuementation, we call the joins with time conditions as > "Time-windowed Join". However, it is called "Interval Join" in DataStream. We > should align the terminology in Flink project. > From my point of view, "Interval Join" is more suitable, because it joins a > time interval range of right stream[1]. And "Windowed Join" should be joins > data in the same window, this is also described in DataStream API. > For Table API & SQL, the "Time-windowed Join" is the "Interval Join" in > DataStream. And we miss the new feature "Windowed Join" in Table API & SQL. > I propose to correct the terminology in docs before 1.10 is release. > [1]: > https://ci.apache.org/projects/flink/flink-docs-master/dev/stream/operators/joining.html#interval-join > [2]: > https://ci.apache.org/projects/flink/flink-docs-master/dev/stream/operators/joining.html#window-join -- This message was sent by Atlassian Jira (v8.3.4#803005)