Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/16594#discussion_r97216973
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/internal/SQLConf.scala ---
@@ -649,6 +649,14 @@ object SQLConf {
.doubleConf
.createWithDefault(0.05)
+ val SHOW_STATS_IN_EXPLAIN =
--- End diff --
If the `sizeInBytes` affects the plan decision, I think it makes sense to
let users see it.
When the plan is not expected and the number is super large, they might
turn on CBO or trigger the command to re-analyze the tables. Hiding it looks
not right to me, even if the number is ugly. : )
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
