Skip to content
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

Support latest dask.dataframe with query planning (dask-expr) #284

Open
jorisvandenbossche opened this issue Mar 11, 2024 · 2 comments
Open

Comments

@jorisvandenbossche
Copy link
Member

The 2024.2.0 release of Dask has deprecated the "legacy" dask.dataframe API. They are building a new API with "Query Planning" based on new high-level expressions (instead of the current HighLevelGraph), which currently lives in the dask-expr package.
It can be enabled through dask.config.set({'dataframe.query-planning': True}).

The upcoming 2024.3.0 release (dask/community#366) plans to enable this by default (but you can still turn it off for now).

Given that dask-geopandas is tightly integrated with dask.dataframe, we will have to update to use the new dask_expr backend.
For released versions of dask-geopandas, users will have to upper pin dask or disable the option for now.

(for reference, a similar issue on the cudf side rapidsai/cudf#15027 (they also have a subclass), and their PR to add basic support: rapidsai/cudf#14805)

@ReptarK
Copy link

ReptarK commented Apr 17, 2024

Hi, any updates on the integration of dask_expr ?

@jorisvandenbossche
Copy link
Member Author

An initial patch supporting dask with query planning was merged in #285. So for now using the latest dask-geopandas from the main branch (not yet released, so something like pip install git+https://github.com/geopandas/dask-geopandas.git) should work with the latest dask releases.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants