chore: Remove Email model#116245
Draft
markstory wants to merge 1 commit into
Draft
Conversation
The Email model and writes (via signal handlers) was added back in 2017, but there have never been any reads to the table in either sentry, getsentry or internal etl pipelines. This table is often missing records which cause relocation validation failures. Removing this table will reduce our write throughput and simplify the user datamodel.
Contributor
|
This PR has a migration; here is the generated SQL for for --
-- Moved model Email to pending deletion state
--
-- (no-op) |
Contributor
Backend Test FailuresFailures on
|
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
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.
The Email model and writes (via signal handlers) was added back in 2017, but there have never been any reads to the table in either sentry, getsentry or internal etl pipelines.
This table is often missing records which cause relocation validation failures. Removing this table will reduce our write throughput and simplify the user datamodel.