[jira] [Updated] (FLINK-27815) Improve the join reorder strategy for batch sql job

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

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

ASF GitHub Bot updated FLINK-27815:
-----------------------------------
    Labels: pull-request-available  (was: )

> Improve the join reorder strategy for batch sql job 
> ----------------------------------------------------
>
>                 Key: FLINK-27815
>                 URL: https://issues.apache.org/jira/browse/FLINK-27815
>             Project: Flink
>          Issue Type: New Feature
>          Components: Table SQL / Planner
>            Reporter: godfrey he
>            Assignee: godfrey he
>            Priority: Major
>              Labels: pull-request-available
>
> Join is heavy operation in the execution, the join order in a query can have a significant impact on the query’s performance. 
> Currently, the planner has one  join reorder strategy which is provided by Apache Calcite, and it strongly depends on the statistics.
> It's better we can provide different join reorder strategies for different situations, such as:
> 1. provide a join reorder strategy without statistics, e.g. eliminate cross joins
> 2. improve current join reorders strategy with statistics
> 3. provide hints to allow users to choose join order strategy
> 4. ...



--
This message was sent by Atlassian Jira
(v8.20.10#820010)