-
Notifications
You must be signed in to change notification settings - Fork 72
Remove null-splitting from _perform_aggregation
#326
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
Merged
charlesbluca
merged 9 commits into
dask-contrib:main
from
charlesbluca:simplify-groupby-agg
Nov 29, 2021
Merged
Changes from 8 commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
b251acb
Remove null-splitting from _perform_aggregation
charlesbluca 6d1a478
Sort groupby results to match Postgres output
charlesbluca ecde0c8
Add back slow path for groupby
charlesbluca 276a5b9
Don't group nulls first for slow path
charlesbluca 4a709b2
Merge remote-tracking branch 'upstream/main' into simplify-groupby-agg
charlesbluca 05530d6
Remove unnecessary inverse comment
charlesbluca 0aa025d
Merge upstream latest
charlesbluca 84b60aa
Split up split_every test into CPU and GPU
charlesbluca 393f11c
Consolidate CPU / GPU tests again
charlesbluca 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
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.
Now that we are able to access dask-cudf's groupby agg codepath, the task graph size varies depending on if we use GPU or not. There could be a clean way to parametrize this all into one test, but I opted for this for now to make the difference more clear.
In general, is there a way we can verify that
split_everyis working that doesn't depend on checking the task graph? Asking because now upstream changes in dask-cudf can break this test.