-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
non-unique vindex routing in update and delete query #9554
Conversation
Signed-off-by: Harshit Gangal <harshit@planetscale.com>
Signed-off-by: Harshit Gangal <harshit@planetscale.com>
Signed-off-by: Harshit Gangal <harshit@planetscale.com>
61e7a55
to
b526973
Compare
…ccomodate non-unique lookup Signed-off-by: Harshit Gangal <harshit@planetscale.com>
…to vtgate instead of fixed pre commit order Signed-off-by: Harshit Gangal <harshit@planetscale.com>
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.
Everything looks good to me! Is there a way to add an end to end test for this? I know it is hard since we won't know which vindex was used for routing, but we could do something like try deleting and check which all shards received that query
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 to me
already on it. |
Signed-off-by: Harshit Gangal <harshit@planetscale.com>
bee6b46
to
a6fef2a
Compare
Description
This PR adds supported for extracting routing information from update/delete query and using non-unique lookup vindex if available and having lowest cost among other options.
Related Issue(s)
Checklist
Deployment Notes