You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Yunhong Zheng (Jira)" <ji...@apache.org> on 2022/10/10 03:37:00 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=17614858#comment-17614858 ]
Yunhong Zheng commented on FLINK-27591:
---------------------------------------
Hi, [~godfreyhe] , I would like to get this ticket. Could you assign this to me, Thanks a lot!
> 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.17.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.10#820010)