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

Use HighLevelGraph layers in dask-mongo.read_mongo #3

Open
jrbourbeau opened this issue Jul 12, 2021 · 4 comments
Open

Use HighLevelGraph layers in dask-mongo.read_mongo #3

jrbourbeau opened this issue Jul 12, 2021 · 4 comments

Comments

@jrbourbeau
Copy link
Member

As a follow-up to #2, we should update dask-mongo.read_mongo to use HighLevelGraph layers (specifically DataFrameIOLayer). This should look very similar to what's done in dask-snowflake.

cc @ncclementi

@crusaderky
Copy link
Contributor

To clarify: Bag.dask is already a HighLevelGraph. This issue is about replacing the basic MaterializedLayer, which is automatically generated by the Bag constructor and contains 1 key per partition, to a bag-specific I/O class.
Since no such class exists today (correct me if I'm wrong), it would need to be first implemented in dask.bag and then used here.

@ncclementi
Copy link
Contributor

@crusaderky I believe you are correct, this was open by James when we were implementing things to work with writing and reading into dataframes. @jrbourbeau Should we close this issue?

@crusaderky
Copy link
Contributor

@ncclementi it's still valid - it's just missing the prerequisite infrastructure in the dask package.

@jrbourbeau
Copy link
Member Author

Yeah, let's keep it open, but know that it is low priority

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

3 participants