-
Notifications
You must be signed in to change notification settings - Fork 111
Composite aggregates #3266
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
Open
normen662
wants to merge
23
commits into
FoundationDB:main
Choose a base branch
from
normen662:composite-aggregates
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Composite aggregates #3266
Changes from all commits
Commits
Show all changes
23 commits
Select commit
Hold shift + click to select a range
183d774
save point
normen662 1779ec5
pulling up matchedAggregationValueMap works
normen662 4c2603f
pre pulling up unmatched values
normen662 6e98b4c
pullng up unmatched values
normen662 3dcf180
intersection complete
normen662 72c8f9e
intersection complete
normen662 3c0d29e
save-point
normen662 6cb4d89
serialization for multi intersection implemented
normen662 59ae202
first plans
normen662 9458645
basic aggregation queries using agg indexes intersections work
normen662 c68b0e0
more agg queriers work
normen662 db8858d
rebased; regular intersections work; pre rollup
normen662 2ea1a71
roll ups work
normen662 6adbd65
rollups work
normen662 9059271
ordering sort of works
normen662 02d28f6
agg testcases run
normen662 a7b022d
cleaning up
normen662 f8c69a7
build somewhat stable
normen662 5b0b266
some polishing
normen662 42baaef
updating tests and writing documentation
normen662 5fde97b
fixups after rebasing
normen662 e428f08
regenerated metrics files
normen662 0aeab9c
addressing rebase fallout
normen662 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
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.
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.
It looks like the reason for using
SingleIterator
(withnull
argument) instead ofEmptyIterator
is related to returning empty list, compared to returningnull
inEmptyIterator
when callingcomputeNext
, is that so, why not just useEmptyIterator
instead and let the customer deal with thenull
?