[
https://issues.apache.org/jira/browse/FLINK-27815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-27815:
-----------------------------------
Labels: pull-request-available stale-assigned (was: pull-request-available)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issue is assigned but has not
received an update in 30 days, so it has been labeled "stale-assigned".
If you are still working on the issue, please remove the label and add a
comment updating the community on your progress. If this issue is waiting on
feedback, please consider this a reminder to the committer/reviewer. Flink is a
very active project, and so we appreciate your patience.
If you are no longer working on the issue, please unassign yourself so someone
else may work on it.
> 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, stale-assigned
>
> 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)
