Cleanup old team feature storage #4470
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
zebot
added
the
ok-to-test
pcapriotti
force-pushed
the
cleanup-old-features
branch
from
4ae7c34 to
6dcb294
Compare
pcapriotti
changed the title
pcapriotti
force-pushed
the
cleanup-old-features
branch
2 times, most recently
from
a09d8d1 to
1f6719e
Compare
pcapriotti
force-pushed
the
cleanup-old-features
branch
from
1f6719e to
795418c
Compare
pcapriotti
changed the title
battermann
approved these changes
Mar 6, 2025
|
So we are keeping the DB schema for now? I guess that is fine. |
You mean the old table itself? Yeah, we have to keep it to prevent issues during deployment. We can get rid of it in one of the next releases. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR removes support for legacy team feature storage, and forces the use of the new dynamic feature table introduced in #4459.
Since #4459 and #4472 contain the data migration needed to fully migrate to the new storage, it is important that this PR not be merged before both of those PRs are included in a release.
https://wearezeta.atlassian.net/browse/WPB-16238
Checklist
changelog.d