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

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

merged in 1.9.0: a6d72fed708e99404c96ffeca6ad70e08963e9cd

> Introduce join reorder planner rules in blink planner
> -----------------------------------------------------
>
>                 Key: FLINK-12937
>                 URL: https://issues.apache.org/jira/browse/FLINK-12937
>             Project: Flink
>          Issue Type: New Feature
>          Components: Table SQL / Planner
>            Reporter: godfrey he
>            Assignee: godfrey he
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.9.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> This issue aims to let blink planner support join reorder. 
> {{LoptOptimizeJoinRule}} in Calcite could meet our requirement for now, so we 
> could use directly this rule in blink planner. {{JoinToMultiJoinRule}} , 
> {{ProjectMultiJoinMergeRule}} and {{FilterMultiJoinMergeRule}} should be also 
> introduced to support {{LoptOptimizeJoinRule}}.
> additionally, we add a new rule named {{RewriteMultiJoinConditionRule}} which 
> could apply transitive closure on `MultiJoin` for equi-join predicates to 
> create more optimization possibilities.
> by default, join reorder is disabled, unless 
> {{sql.optimizer.join-reorder.enabled}} is set as true.



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

Reply via email to