You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "boshu Zheng (JIRA)" <ji...@apache.org> on 2018/12/15 08:55:00 UTC

[jira] [Comment Edited] (FLINK-9717) Flush state of one side of the join if other side is bounded

    [ https://issues.apache.org/jira/browse/FLINK-9717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16722013#comment-16722013 ] 

boshu Zheng edited comment on FLINK-9717 at 12/15/18 8:54 AM:
--------------------------------------------------------------

Just a small thought on it to share. 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.


was (Author: kisimple):
Just a little thought on it to share. When considering about joins with bounded data, I would prefer the side input solution 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 &amp; 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)