backfill uuid script#69294
Draft
alex-m-brown wants to merge 3 commits into
Draft
Conversation
This was referenced Nov 6, 2025
Merged
Merged
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
1 participant
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 is the fourth PR in a series of PRs to migrate our existing channel token system for projects to unique identifiers. This PR adds a script to backfill project UUIDs.
There are about 1.4 billion records in the Projects table. Limited at 1000 records/second, it will take at least 16 days to complete this backfill. On a production-cloned adhoc, backfilling 1 million records took 3 hours. At that rate, it will take 6 months of straight backfill to complete.
Links
Testing story
Follow-up work
Now that all projects have UUIDs, we can continue on to removing legacy channel token support.
4. Update the UUID column to be non-null
5. Eventually completely remove old channel token support
Privacy and Security
This PR is the third step in further securing our projects.