andygrove opened a new issue, #2413: URL: https://github.com/apache/datafusion-comet/issues/2413
### What is the problem the feature request solves? We currently have multiple ways of reporting information about which parts of a plan are accelerated with Comet, and it is not well-documented. # `spark.comet.explainFallback.enabled` When enabled, Comet checks for fallback reasons. If there are no fallback reasons then nothing gets logged. If there are fallback reasons, then Comet shows the verbose extended info plan (regardless of whether `spark.comet.explain.verbose.enabled` is enabled). There is no way to show the verbose plan if there are no fallback reasons (although this changes with Spark 4.0.0, which adds support for ExtendedExplainInfo). # `spark.comet.logFallbackReasons.enabled` This logs every fallback reason to a single WARN log entry and does not show the plan that it is related to. # `spark.comet.explain.verbose.enabled` This property is referenced from `ExtendedExplainInfo`. The code is only invoked via Spark 4.0.0 and later if `--conf spark.sql.extendedExplainProviders=org.apache.comet.ExtendedExplainInfo` is specified. `ExtendedExplainInfo` is invoked directly from some tests. ### Describe the potential solution _No response_ ### Additional context _No response_ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
