-
Notifications
You must be signed in to change notification settings - Fork 53
Retry idempotent queries using builtin mechanism in neo4j driver #868
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
Conversation
✅ Deploy Preview for neo4j-graph-data-science-client canceled.
|
435274c
to
3781b2d
Compare
✅ Deploy Preview for neo4j-graph-data-science-client canceled.
|
3781b2d
to
4d2ac35
Compare
routing = neo4j.RoutingControl.WRITE if "write" in endpoint else neo4j.RoutingControl.READ | ||
return self.run_retryable_cypher(query, params, database, custom_error, routing=routing) |
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.
Will this ever be a safe combination. Our write are not always idempotent.
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 main case was gds.arrow.write.v3
Maybe should rather have it explicit in for the write protocol case
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.
okay its already explicit as before the caller needs to have passed retryable=True
explicitly
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.
Maybe instead of doing the string matching we could pass in the RoutingControl from the caller
No description provided.