Fix: Drop customer_snapshots table from database #4453
+10
−90
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
ancorcruz
force-pushed
the
fix/revert-customer-snapshots-drop-table
branch
from
d1a94f9 to
f68b1d2
Compare
ancorcruz
force-pushed
the
fix/revert-customer-snapshots-drop-table
branch
from
f68b1d2 to
0aa76a4
Compare
|
This other PR #3761 could be released together. |
vincent-pochet
approved these changes
Oct 9, 2025
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.
DO NOT MERGE UNTIL PREPARING A SPECIAL RELEASE WITH DATABASE CLEANUP
Description
This PR contains a destructive and irreversible database migration that drops the
customer_snapshotstable. This is the third and final step in the complete removal of the customer_snapshots.DO NOT upgrade directly to the version containing this change, ensure previous version is upgraded first.
Context
The customer_snapshot feature was rolled back due to significant scalability risks. We implemented a three-step removal process to ensure maximum safety:
After a safe interval to allow users to upgrade, we are now removing the orphaned table to eliminate database clutter and finalize the cleanup.
This PR completes that process.