Github user wzhfy commented on the issue: https://github.com/apache/spark/pull/16401 If our goal is to fix two sets of stats issue first, is it ok to just use two `lazy val`s now, and leave the configuration and cache invalidation issues in the future? In current implementation, we don't need any configurations except the cbo switch conf. ``` def statistics(conf: CatalystConf): Statistics = { if (conf.cboEnabled) cboStats else basicStats } lazy val cboStats... lazy val basicStats... ```
--- 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