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.

Sign up for GitHub

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

Jump to bottom

[FEA]: MG PropertyGraph backed by Dask DataFrames #9

Open
2 tasks done
Tracked by #17
eriknw opened this issue Jan 6, 2023 · 0 comments
Open
2 tasks done
Tracked by #17

[FEA]: MG PropertyGraph backed by Dask DataFrames #9

eriknw opened this issue Jan 6, 2023 · 0 comments
Labels
feature request New feature or request

Comments

@eriknw
Copy link

eriknw commented Jan 6, 2023

Is this a new feature, an improvement, or a change to existing functionality?

New Feature

How would you describe the priority of this feature request

Medium

Please provide a clear description of problem this feature solves

Allow MG PropertyGraph to store data with dask.dataframe instead of with dask_cudf. This allows data to be stored in host memory and mirrors functionality in PropertyGraph.

Describe your ideal solution

Ideally this can be composed nicely with rapidsai/cugraph#2424 where some types can be Dask DataFrames and some can be cudf DataFrames. But, I think this issue can be done before rapidsai/cugraph#2424.

Describe any alternatives you have considered

No response

Additional context

No response

Code of Conduct

  • I agree to follow cuGraph's Code of Conduct
  • I have searched the open feature requests and have found no duplicates for this feature request
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature request New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@eriknw