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

[FEA] Property Graph get_vertex_data accept int #2692

Closed
BradReesWork opened this issue Sep 13, 2022 · 0 comments · Fixed by #2698
Closed

[FEA] Property Graph get_vertex_data accept int #2692

BradReesWork opened this issue Sep 13, 2022 · 0 comments · Fixed by #2698
Assignees
Labels
feature request New feature or request
Milestone

Comments

@BradReesWork
Copy link
Member

Describe the solution you'd like and any additional context
currently get_vertex_data only accepts an array of vertex IDs, it should also support a single int as input


For Developers below this line

  • [] Code passes CI
  • [] Code uses Graph Primitives
  • [] Code in C++/CUDA layer
  • [] Code in C layer
  • [] Code in pylibcugraph Python layer
  • [] Code in cugraph Python layer
  • [] Documentation
  • [] Test cases at each layer (for MG tests, a note in the PR description indicating the new/existing MG tests were run and passed)
@BradReesWork BradReesWork added the feature request New feature or request label Sep 13, 2022
@BradReesWork BradReesWork added this to the 22.10 milestone Sep 13, 2022
eriknw added a commit to eriknw/cugraph that referenced this issue Sep 14, 2022
Closes rapidsai#2692.

Currently SG only.  MG version coming shortly!
rapids-bot bot pushed a commit that referenced this issue Sep 22, 2022
Closes #2692.

Currently SG only.  ~MG version coming shortly!~  MG version done.

Authors:
  - Erik Welch (https://github.com/eriknw)

Approvers:
  - Rick Ratzel (https://github.com/rlratzel)

URL: #2698
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants