-
Notifications
You must be signed in to change notification settings - Fork 300
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
Allow users to provide their own edge IDS to PropertyGraph #2757
Conversation
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.
The overall changes look good but I think we should ask the user provide edge_ids if they do it once and also expose last_edge_id.
Case 1:
Case 2:
@VibhuJawa, do I understand your comment correctly that you want to support case 2, but not case 1? We can handle case 1 by taking the max of the user-provided edge ids (as is currently done in this PR). Not supporting this lets us avoid taking the max. We could support case 2 by trusting the user. Giving them the last (i.e., max) edge id could be a way to give them the tool to do this. Exposing this value once again requires taking the max of the user-provided edge ids. So, basically, all options are available to us:
|
I think this good for now . The usecase i think this is useful is when we want to create new edges like adding self-loops etc . Can we create a feature request for other cases so that we can track and prioritize them as need arises. |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## branch-22.10 #2757 +/- ##
===============================================
Coverage ? 59.80%
===============================================
Files ? 111
Lines ? 6185
Branches ? 0
===============================================
Hits ? 3699
Misses ? 2486
Partials ? 0 Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
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.
LGTM
We had further discussion about case 1/case 2 offline, captured here. |
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.
Looks good, I just had one question, then I'll re-review after the changes from this conversation are done.
If auto-generated, all edge IDs must be auto-generate. Conversely, if user-provied, all edge IDs must be user-provided.
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.
LGTM, especially the added test coverage.
@gpucibot merge |
Closes #2565
Should we try to avoid creating conflicting edge IDs (for example, when user doesn't provides all edge IDs). Should we expose
last_edge_id
.