[ https://issues.apache.org/jira/browse/SPARK-22529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zhenhua Wang updated SPARK-22529: --------------------------------- Description: Currently, relation stats is the same whether cbo is enabled or not. While relation (`LogicalRelation` or `HiveTableRelation`) is a `LogicalPlan`, this behavior makes it inconsistent with other plans. This can cause confusion when user runs EXPLAIN COST commands. Besides, when CBO is disabled, we apply the size-only estimation strategy, so there's no need to propagate other statistics to relation. (was: When CBO is disabled, we apply the size-only estimation strategy, so there's no need to propagate other statistics from catalog to the plan.) > Relation stats should be consistent with other plans based on cbo config > ------------------------------------------------------------------------ > > Key: SPARK-22529 > URL: https://issues.apache.org/jira/browse/SPARK-22529 > Project: Spark > Issue Type: Sub-task > Components: SQL > Affects Versions: 2.3.0 > Reporter: Zhenhua Wang > > Currently, relation stats is the same whether cbo is enabled or not. While > relation (`LogicalRelation` or `HiveTableRelation`) is a `LogicalPlan`, this > behavior makes it inconsistent with other plans. This can cause confusion > when user runs EXPLAIN COST commands. Besides, when CBO is disabled, we apply > the size-only estimation strategy, so there's no need to propagate other > statistics to relation. -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org