-
Notifications
You must be signed in to change notification settings - Fork 310
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
Update API for node2vec and biased random walks #4841
base: branch-25.02
Are you sure you want to change the base?
Update API for node2vec and biased random walks #4841
Conversation
# padded results. The flags 'legacy_result_type' and 'use_padding" should be | ||
# removed. | ||
|
||
if legacy_result_type or use_padding is False: |
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.
Note... it seems like the old mechanism (coalesced format) is not particularly helpful other than a modest savings in memory on a small result type anyway.
We don't intend to support that in the C++ code any longer. If we need to continue to support this old mechanism while it is deprecated before we can delete it I would suggest implementing something to convert the format within the python layer.
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 still have the old mechanism around and I deprecated the coalesced path in the python API. Since there is no real benefit of using the coalesced path, I suggest to not support in the new API. @rlratzel any thoughts?
This PR
closes #3277
closes #2558
closes #2559
closes #2560
closes #2561