-
Notifications
You must be signed in to change notification settings - Fork 1k
Add "collect" aggregation support to dask-cudf #15593
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
Merged
Changes from 5 commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
469f170
add collect support
rjzamora 0655b66
Merge remote-tracking branch 'upstream/branch-24.06' into groupby-upd…
rjzamora 4fc2025
remove dependency on upstream PR
rjzamora 61015ca
remove stale code
rjzamora 13791fb
Merge branch 'branch-24.06' into groupby-updates
rjzamora 0c1c272
Merge remote-tracking branch 'upstream/branch-24.06' into groupby-upd…
rjzamora 5c700b2
add warning - need to revise tests
rjzamora 433e19a
Merge branch 'branch-24.06' into groupby-updates
rjzamora 53fe014
Merge remote-tracking branch 'upstream/branch-24.06' into groupby-upd…
rjzamora 2170e18
clean up the message a bit
rjzamora 42b35c9
Update python/dask_cudf/dask_cudf/expr/_collection.py
rjzamora 3482386
Merge branch 'branch-24.06' into groupby-updates
rjzamora ca303be
avoid breaking 15634
rjzamora 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
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.
nit: This is a somewhat confusing error message. The only way to get past it with query planning enabled is to say
as_index=True, but the error message seems to say "as_index=True` is not handled by dask-expr.Do you mean:
WDYT?
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 sounds like dask-expr doesn't actually have support for the
as_indexkeyword arg in general and always follows the behavior ofas_index=False, so perhaps we should consider:FutureWarningif soas_index=True, raise the error description suggested aboveThere 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.
The upstream
dask.dataframeAPI has always raised an error whenas_indexis used, but dask-cudf has used a distinct groupby API until now.I agree that the real problem is that
as_indexis not supported at all by dask-expr. Therefore @charlesbluca's suggestion is probably the most "correct". With that said, I'm feeling a bit hesitant to add more noise for something that technically "works fine" :/