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

Upgrade schema correctly at tarantool update within a release #4804

Open
Totktonada opened this issue Mar 11, 2020 · 0 comments
Open

Upgrade schema correctly at tarantool update within a release #4804

Totktonada opened this issue Mar 11, 2020 · 0 comments
Labels
feature A new functionality refactoring Code refactoring upgrade
Milestone
wishlist

Comments

@Totktonada
Copy link
Member

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.
@Totktonada Totktonada added refactoring Code refactoring upgrade labels Mar 11, 2020
@Totktonada Totktonada mentioned this issue Mar 11, 2020
Open
@kyukhin kyukhin added this to the 2.4.1 milestone Mar 18, 2020
slumber added a commit that referenced this issue Mar 18, 2020
@slumber
box: allow schema upgrades within a release
8f887ce 
If a user upgrades his schema (e.g. via pulling from master) and
later the corresponding upgrade script is updated, new changes won't
be applied for him. To avoid this, we introduce a hidden version,
which can be used to perform partial upgrades with a single release.

Closes #4804
slumber added a commit that referenced this issue Mar 19, 2020
@slumber
box: allow schema upgrades within a release
b7d8142 
To avoid cases when a user has an incorrectly upgraded schema, we
introduce new versioning, which can be used to perform upgrades
within a single release.

Closes #4804
Needed for #4666
slumber added a commit that referenced this issue Mar 25, 2020
@slumber
box: allow schema upgrades within a release
8afa958 
To avoid cases when a user has an incorrectly upgraded schema, we
introduce new versioning, which can be used to perform upgrades
within a single release.

Closes #4804
Needed for #4666
slumber added a commit that referenced this issue Mar 26, 2020
@slumber
box: allow schema upgrades within a release
c6682c9 
To avoid cases when a user has an incorrectly upgraded schema, we
introduce new versioning, which can be used to perform upgrades
within a single release.

Closes #4804
Needed for #4666
@kyukhin kyukhin modified the milestones: 2.4.1, 2.4.2 Apr 20, 2020
@kyukhin kyukhin added the feature A new functionality label Apr 24, 2020
@kyukhin kyukhin modified the milestones: 2.4.2, 2.5.1 Apr 24, 2020
slumber added a commit that referenced this issue Apr 24, 2020
@slumber
box: allow schema upgrades within a release
ab82029 
To avoid cases when a user has an incorrectly upgraded schema, we
introduce new versioning, which can be used to perform upgrades
within a single release.

Closes #4804
Needed for #4666
@kyukhin kyukhin modified the milestones: 2.5.1, 2.6.1 Jul 10, 2020
@kyukhin kyukhin modified the milestones: 2.6.1, wishlist Oct 23, 2020
@Totktonada Totktonada mentioned this issue Oct 11, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature A new functionality refactoring Code refactoring upgrade
Projects
None yet
Milestone
wishlist
Development

No branches or pull requests
3 participants
@Totktonada @kyukhin @slumber