-
Notifications
You must be signed in to change notification settings - Fork 25.3k
Remove ordinal grouping path in aggregations #131307
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
76b06b8
to
45e2587
Compare
Pinging @elastic/es-analytical-engine (Team:Analytics) |
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.
LGTM! Just a thought in a comment; probably not interesting anyway
@@ -121,7 +121,7 @@ | |||
* It is also possible to declare any number of arbitrary arguments that must be provided via generated Supplier. | |||
* </li> | |||
* <li> | |||
* {@code combine, combineStates, combineIntermediate, evaluateFinal} methods (see below) could be generated automatically |
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.
I wonder if it would be worth it keeping the combineStates()
, in case we want to reuse it later. For some node-level initial agg reduction. I think we talked about it at some point.
Not sure if it's really worth it. Commenting mostly because we're throwing quite some code.
However, I see there are no tests being removed though, so I suppose this wasn't tested either
With the ordinal grouping operator removed in #131133, this PR removes the corresponding code path in the grouping aggregator function, as it is no longer needed.
Relates #131133