Skip to content
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.

Sign up for GitHub

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

Jump to bottom

FeatureRequest: LookupVindex create should use an existing VIndex and Table when possible #15983

Closed
Tracked by #13960
mattlord opened this issue May 20, 2024 · 0 comments · Fixed by #16097
Closed
Tracked by #13960

FeatureRequest: LookupVindex create should use an existing VIndex and Table when possible #15983

mattlord opened this issue May 20, 2024 · 0 comments · Fixed by #16097
Assignees
@mattlord
Labels
Component: VReplication Type: Feature

Comments

@mattlord
Copy link
Contributor

mattlord commented May 20, 2024 •
edited
Loading

If the vindex or empty table already exists in the target keyspace the create fails when it goes to create them. At least in some scenarios (table is empty e.g.) we should be able to use the existing resources.
This was referenced May 20, 2024
Open
Closed
@mattlord mattlord changed the title FeatureRequest: LookupVindex create should use existing VSchama and Table entries when possible FeatureRequest: LookupVindex create should use an existing VIndex and Table when possible May 20, 2024
@mattlord mattlord self-assigned this Jun 10, 2024
@mattlord mattlord mentioned this issue Jun 10, 2024
Merged
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mattlord mattlord

Labels
Component: VReplication Type: Feature
Projects
VReplication
Status: Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

VReplication: LookupVindex create use existing artifacts when possible planetscale/vitess
1 participant
@mattlord