-
Notifications
You must be signed in to change notification settings - Fork 94
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
Remove legacy Dask-cuDF handling #1417
base: branch-25.02
Are you sure you want to change the base?
Conversation
Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually. Contributors can view more details about this message here. |
/ok to test |
The build failure is not related to the changes here, it should be fixed by #1418 . |
Thanks @pentschev - Just a heads up that I do see some pytest failures locally. My |
/ok to test |
/okay to test |
dask_cuda/__init__.py
Outdated
dask.dataframe.shuffle.get_default_shuffle_method = get_default_shuffle_method | ||
dask.dataframe.multi.get_default_shuffle_method = get_default_shuffle_method | ||
dask.bag.core.get_default_shuffle_method = get_default_shuffle_method | ||
patch_shuffle_expression() |
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.
cc @madsbk (for viz) - Now that we are dropping "legacy" support, we need to do something a bit different to satisfy the "explicit-comms"
config. Let me know if you have any thoughts or concerns.
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 think this looks good now given tests are also passing. Would be best if @madsbk could have a look too before we merge.
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.
Giving you a packaging-codeowners
approval. Thanks for removing those warnings filters from pyproject.toml
!
Removes testing/handling for "legacy" Dask cuDF (i.e.
DASK_DATAFRAME__QUERY_PLANNING=False
).This PR also adds support for the
"explicit-comms"
config with query-planning enabled (we used to raise an error telling the user to disable query planning).This should be merged before rapidsai/cudf#17558 (otherwise Dask-CUDA CI will break).
This PR is marked as "breaking", because it technically breaks the
"explicit-comms"
config with the "legacy" version of Dask cuDF (which we are about to remove in 25.02 anyway).