godfreyhe opened a new pull request #8317: [FLINK-12371] [table-planner-blink] Add support for converting (NOT) IN/ (NOT) EXISTS to SemiJoin, and generating optimized logical plan URL: https://github.com/apache/flink/pull/8317 ## What is the purpose of the change *Add support for converting (NOT) IN/ (NOT) EXISTS to SemiJoin, and generating optimized logical plan* ## Brief change log - *Add SemiJoin to support anti-join and non-equi join* - *Add FlinkSubQueryRemoveRule to convert (NOT) IN/ (NOT) EXISTS to SemiJoin* - *Add SimplifyFilterConditionRule to simplify filter condition (including filter condition in RexSubQuery)* - *Update BatchExecHashJoinRule to convert FlinkLogicalSemiJoin to BatchExecHashSemiJoin, so do BatchExecNestedLoopJoinRule and BatchExecSortMergeJoinRule* - *Add StreamExecSemiJoinRule to convert FlinkLogicalSemiJoin to SteamExecSemiJoin* ## Verifying this change This change added tests and can be verified as follows: - *Added FlinkJoinPushExpressionsRuleTest that validates FlinkJoinPushExpressionsRule* - *Added SimplifyFilterConditionRuleTest that validates SimplifyFilterConditionRule* - *Added tests that validate logical plan after FlinkSubQueryRemoveRule applied* - *Added tests that validate physical plan after physical convert rules applied* ## Does this pull request potentially affect one of the following parts: - Dependencies (does it add or upgrade a dependency): (no) - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: (no) - The serializers: (no) - The runtime per-record code paths (performance sensitive): (no) - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no) - The S3 file system connector: (no) ## Documentation - Does this pull request introduce a new feature? (no) - If yes, how is the feature documented? (not documented)
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
