You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by "godfrey he (JIRA)" <ji...@apache.org> on 2019/05/14 13:07:00 UTC

[jira] [Created] (FLINK-12509) Introduce planner rules about non semi/anti join

godfrey he created FLINK-12509:
----------------------------------

             Summary: Introduce planner rules about non semi/anti join
                 Key: FLINK-12509
                 URL: https://issues.apache.org/jira/browse/FLINK-12509
             Project: Flink
          Issue Type: New Feature
          Components: Table SQL / Planner
            Reporter: godfrey he
            Assignee: godfrey he


This issue aims to introduce planner rules about non semi/anti join, rules include:
1. {{JoinConditionEqualityTransferRule}}, that converts Join's conditions to the left or right table's own independent filter as much as possible, so that the rules of filter-push-down can push down the filter to below.
2. {{JoinConditionTypeCoerceRule}}, that coerces the both sides of EQUALS(`=`) operator in Join condition to the same type while sans nullability.
3. {{JoinDependentConditionPushDownRule}}, that extracts some sub-conditions in the Join OR condition that can be pushed into join inputs by {{FlinkFilterJoinRule}}.
4. {{JoinDeriveNullFilterRule}} filters null values before join if the count null value from join input
  is greater than {{sql.optimizer.join.null.filter.threshold}}
5. {{SimplifyJoinConditionRule}}, that apply various simplifying transformations on join condition.

planner rules about semi/anti join will be introduced in another issue.



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