godfreyhe opened a new pull request #8832: [FLINK-12937] [table-planner-blink] Introduce join reorder planner rules in blink planner URL: https://github.com/apache/flink/pull/8832 ## What is the purpose of the change *Introduce join reorder planner rules in blink planner* ## Brief change log - *Introduce join reorder rules, including JoinToMultiJoinRule, ProjectMultiJoinMergeRule, FilterMultiJoinMergeRule and LoptOptimizeJoinRule* - *Add new rule named RewriteMultiJoinConditionRule which could apply transitive closure on `MultiJoin` for equi-join predicates to create more optimization possibilities* ## Verifying this change This change added tests and can be verified as follows: - *Added RewriteMultiJoinConditionRuleTest that validates the logical plan after RewriteMultiJoinConditionRule applied* - *Added JoinReorderTest that validates the join reorder result* ## Does this pull request potentially affect one of the following parts: - Dependencies (does it add or upgrade a dependency): (yes / **no**) - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: (yes / **no**) - The serializers: (yes / **no** / don't know) - The runtime per-record code paths (performance sensitive): (yes / **no** / don't know) - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes / **no** / don't know) - The S3 file system connector: (yes / **no** / don't know) ## Documentation - Does this pull request introduce a new feature? (yes / **no**) - If yes, how is the feature documented? (not applicable / docs / JavaDocs / **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: us...@infra.apache.org With regards, Apache Git Services
