feat: [EXPERIMENTAL] Add cost-based optimizer (CBO) for Comet vs Spark execution #3220
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR introduces an experimental lightweight cost-based optimizer (CBO) that estimates whether a Comet query plan will be faster than a Spark plan, falling back to Spark when Comet execution is estimated to be slower.
Key Features
Configuration Options
spark.comet.cbo.enabledfalsespark.comet.cbo.speedupThreshold1.0spark.comet.cbo.explain.enabledfalseAdditional internal configs for tuning weights and speedup factors are available (see
CometConf.scala).How It Works
CometExecRuletransforms operators to Comet equivalents, CBO analyzes the planLimitations
CometScanRuleExample Usage
Files Changed
CometCostEstimator.scala- Core cost estimation logicCometCBOSuite.scala- Unit testsCometConf.scala- Configuration optionsCometExecRule.scala- CBO integrationExtendedExplainInfo.scala- CBO info in EXPLAINTest plan
CometCBOSuite(13 tests)CometExecRuleSuitetests pass🤖 Generated with Claude Code