You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "godfrey he (Jira)" <ji...@apache.org> on 2022/05/12 11:41:00 UTC

[jira] [Updated] (FLINK-27591) Improve the plan for batch queries when statistics is unavailable

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

godfrey he updated FLINK-27591:
-------------------------------
    Fix Version/s: 1.16.0

> Improve the plan for batch queries when statistics is unavailable 
> ------------------------------------------------------------------
>
>                 Key: FLINK-27591
>                 URL: https://issues.apache.org/jira/browse/FLINK-27591
>             Project: Flink
>          Issue Type: New Feature
>          Components: Table SQL / Planner
>            Reporter: godfrey he
>            Priority: Major
>             Fix For: 1.16.0
>
>
> This jira is an umbrella issue, which aims to improve the plan for batch queries when statistics is unavailable.
> Currently, when statistics is unavailable, the planner will give default cost, which may lead to the planner choosing bad plan, such as: wrong broadcast join plan will cause a lot of network shuffle and OOM.
> We can detect whether the source tables have statistics. if not, join order, hash join can be disabled.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)