-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
feat: Add having
to group_by
context
#23550
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 ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #23550 +/- ##
==========================================
- Coverage 81.28% 81.28% -0.01%
==========================================
Files 1644 1644
Lines 223249 223312 +63
Branches 2841 2847 +6
==========================================
+ Hits 181479 181511 +32
- Misses 41071 41097 +26
- Partials 699 704 +5 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
I am not sure we should implement this as opposed this lowering to a group-by with a post filter. I think it should be the latter. |
Fair, the only problem I see is that I now need to choose column names for the predicates which may not clash with each other and any keys/aggregations. How do you typically solve such an issue here? |
You can use |
One more question @ritchie46: would you want to do the
translation when building the |
Unless absolutely trivial, I think it should be when converting from |
I removed the |
@ritchie46 do you have any thoughts on the updated implementation? :) |
|
||
Examples | ||
-------- | ||
Filter groups that contain only one element. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Isn't it "that contain more than one element" instead? ("filter" is equivalent to "keep" for me)
Or "Keep groups that contain more than one element" ?
Fixes #23290.
A few comments: