planetscale / planetscale/vitess-operator
Creating a Keyspace with >1 parts does not update VSchema
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 372
- Forks
- 102
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 15
Description
The deploy/example.yml has 2 parts in the keyspace it's creating but the VSchema is just created as an empty { }.
I think this is causing problems as I was seeing errors complaining that tables I created in that keyspace weren't sharded.
I think during instantiation of the keyspace it should detect parts > 1 and update the schema with the minimum:
{
"sharded": true
}Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with deploy/example.yml and trace the keyspace instantiation path that creates its VSchema. Reproduce the case with more than one keyspace part, then verify that the resulting VSchema contains the minimum sharding setting and that tables in the keyspace are treated as sharded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- databases, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100