tarantool / tarantool/tarantool
Upgrade schema correctly at tarantool update within a release
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 3.7k
- Forks
- 419
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 88
Description
The overall situation is described in #4800.
I propose to implement necessary mechanics to do upgrades within one x.y.z.* release correctly. So it will be possible to implement an upgrade that does not block further upgrades within a release. It will not fix past upgrades.
Let's fix past upgrades (or provide a separate script to fix them) in the scope of #4800.
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 by reading the overall situation in issue #4800, then trace how schema upgrades are handled during a Tarantool update within an x.y.z.* release. Done means a new upgrade can proceed without blocking later upgrades in the same release; fixing past upgrades is explicitly out of scope here.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100