feat: back-fill submission unique identifier - TASK 1459 #5434
+108
−1
Conversation
This file contains 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
noliveleger
changed the title
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.
📣 Summary
Added a long-running migration to backfill the
root_uuidfield for old submissions.📖 Description
Submissions now use a field called
root_uuid, which serves as a unique identifier per project. For older submissions, this field is empty. This PR introduces a long-running migration to backfill theroot_uuidfield with the currentuuidfor existing submissions.To ensure uniqueness, the migration includes logic to detect and resolve conflicts. If a
uuidis not unique within a project, theclean_duplicated_submissionsmanagement command is invoked to address the duplicates before assigning theroot_uuid.