-
Notifications
You must be signed in to change notification settings - Fork 901
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
Patch dask-expr var
logic in dask-cudf
#15347
Conversation
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.
We need to add a test in dask-cudf for the functions used in the 10min notebook.
Agreed - This is still a draft. |
Note that the custom |
CI failures are due to a bad/old dask-expr version being pulled (dask/distributed#8574) |
The dask/dask-expr nightly-conda situation should be fixed now. So dask-related CI should start passing now. |
I reran the failed CI jobs (network issues). @rjzamora Is this ready for review? |
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.
Changes look fine to me.
Co-authored-by: Bradley Dice <bdice@bradleydice.com>
Yeah, thanks @bdice ! |
/merge |
Description
The
var
logic in dask-expr relies on pandas -> numpy conversion that does not work for cudf -> cupy when null values are present. This PR copies over the customvar
logic being used in dask-cudf for the legacy API.Checklist