[ https://issues.apache.org/jira/browse/FLINK-9717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16732106#comment-16732106 ]
Piotr Nowojski commented on FLINK-9717: --------------------------------------- What do you [~kisimple] mean by: > When considering about joins with bounded data, I would prefer the side input > solution in which there is no `MAX_WATERMARK` if I understand correctly. ? > Flush state of one side of the join if other side is bounded > ------------------------------------------------------------ > > Key: FLINK-9717 > URL: https://issues.apache.org/jira/browse/FLINK-9717 > Project: Flink > Issue Type: Sub-task > Components: Table API & SQL > Affects Versions: 1.5.0 > Reporter: Piotr Nowojski > Priority: Major > > Whenever one side of join receives {{MAX_WATERMARK}}, other side in joins > (both normal and versioned joins) could flush the state from other side. > This highly useful optimisation that would speed up versioned joins and would > allow normal joins of large unbounded streams with bounded tables (for > example some static data). -- This message was sent by Atlassian JIRA (v7.6.3#76005)