-
-
Notifications
You must be signed in to change notification settings - Fork 113
Add support for aggregate functions #589
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
Conversation
Fix whitespace errors reported by pre-commit hook
Fix whitespace errors reported by pre-commit hook
Fix whitespace errors reported by pre-commit hook
Information regarding the aggregate being available for only certain types is already there in the beginning of the aggregates section.
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.
Hey @spitfire55, thank you for this PR.
I've pushed some minor fixes and added some review comments but not fully done reviewing yet.
- Fix AggregateSelection typename to use field instead of sub_field - Create helper function for integer type matching
- Refactoring & simplification - Remove defensive UUID check - Better log & error strings
@olirice LGTM. Would like to take a quick look. One question I had was if we'd like to hide the aggregates behind a directive similar to total count for performance reasons. |
nice work on the pr @spitfire55 Yes I think we should have it setup like |
Added the comment directive to guard aggregate usage, similar to totalCount. Docs updated as well. |
What kind of change does this PR introduce?
Add support for aggregates (min, max, avg, count, sum)
What is the current behavior?
No support
What is the new behavior?
Standard support. I'm sure there are edge cases I haven't tested or covered, but this is a good first shot at it.
Additional context
N/A