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

Posted to issues@flink.apache.org by "Kurt Young (JIRA)" <ji...@apache.org> on 2019/04/08 02:18:00 UTC

[jira] [Closed] (FLINK-12094) Introduce sort merge join operator to blink batch

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

Kurt Young closed FLINK-12094.
------------------------------
       Resolution: Implemented
    Fix Version/s: 1.9.0

fixed in 63876fbedfa52e7e6d6439384bfaca5aa5137d8b

> Introduce sort merge join operator to blink batch
> -------------------------------------------------
>
>                 Key: FLINK-12094
>                 URL: https://issues.apache.org/jira/browse/FLINK-12094
>             Project: Flink
>          Issue Type: New Feature
>          Components: Table SQL / Runtime
>            Reporter: Jingsong Lee
>            Assignee: Jingsong Lee
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.9.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Introduce SortMergeJoinOperator: An implementation that realizes the joining through a sort-merge join strategy.
> Support all sql types: INNER, LEFT, RIGHT, FULL, SEMI, ANTI
> 1.In most cases, its performance is weaker than HashJoin.
> 2.It is more stable than HashJoin, and most of the data can be sorted stably.
> 3.SortMergeJoin should be the best choice if sort can be omitted in the case of multi-level join cascade with the same key.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)