You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current cugraph python code still has many places where hardcoded column names are used, sometimes inconsistently (eg. src, dst, weight, weights, wgt).
Other column names from PropertyGraph include those for edge ID, edge type, and vertex type, and may also need to be considered.
The proposal here is to create a single python module that defines the column names as constants which can be imported and used throughout the python code.
This PR addresses a similar problem, and should be considered in the final solution.
The text was updated successfully, but these errors were encountered:
This issue has been labeled inactive-30d due to no recent activity in the past 30 days. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed. This issue will be labeled inactive-90d if there is no activity in the next 60 days.
The current cugraph python code still has many places where hardcoded column names are used, sometimes inconsistently (eg.
src
,dst
,weight
,weights
,wgt
).Other column names from PropertyGraph include those for edge ID, edge type, and vertex type, and may also need to be considered.
The proposal here is to create a single python module that defines the column names as constants which can be imported and used throughout the python code.
This PR addresses a similar problem, and should be considered in the final solution.
The text was updated successfully, but these errors were encountered: