-
Notifications
You must be signed in to change notification settings - Fork 260
experiment: remove current final agg check and see what breaks #2886
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #2886 +/- ##
============================================
+ Coverage 56.12% 59.31% +3.18%
- Complexity 976 1374 +398
============================================
Files 119 167 +48
Lines 11743 15347 +3604
Branches 2251 2549 +298
============================================
+ Hits 6591 9103 +2512
- Misses 4012 4957 +945
- Partials 1140 1287 +147 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
Spark SQL Test Failures: These tests may need updating because Comet is now accelerating more queries. oore-1core-2core-3 |
…t hash agg for Spark 3.5
|
Genuine failure with mixed Spark/Comet hash agg: |
Which issue does this PR close?
Part of #2887
Rationale for this change
Comet currently falls back to Spark for final aggregates if Comet did not accelerate the partial aggregate. This is overly aggressive, and since final aggregations are often the leaf nodes in a query stage, we are unnecessarily falling back for entire stages.
What changes are included in this PR?
CometHashAggregateExecso that the fallback for final aggregates only happens in cases where a Comet partial aggregate would not be compatible, rather than in all casesCometExecRuleHow are these changes tested?