-
-
Notifications
You must be signed in to change notification settings - Fork 184
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(migrations): introduce long-running migration system using Celery TASK-1394 #5379
Merged
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
9 tasks
Guitlle
requested changes
Dec 18, 2024
noliveleger
force-pushed
the
long-running-migrations
branch
from
December 18, 2024 21:34
d40c568
to
658d953
Compare
Guitlle
approved these changes
Dec 18, 2024
noliveleger
changed the title
Long running migrations
feat(migrations): introduce long-running migration system using Celery
Dec 18, 2024
…s is correct for transferred projects TASK-1352 (#5385) ### 📣 Summary Extended the bug fix from #5365 to address issues in existing projects. ### 📖 Description This update addresses the issue where OpenRosa media file paths were not updated correctly during project ownership transfers for existing projects. This misalignment led to 404 errors when users attempted to access transferred projects in Collect due to missing media files. ### Notes The fix leverages the new long-running migration flow to address the issue in the background.
…into long-running-migrations
noliveleger
changed the title
feat(migrations): introduce long-running migration system using Celery
feat(migrations): introduce long-running migration system using Celery TASK-1394
Dec 19, 2024
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 new system for handling long-running migrations using Celery.
📖 Description
A new long-running migration system has been implemented, leveraging Celery to process migrations in the background. This system is designed to handle large-scale data updates that would otherwise cause require significant downtime with regular Django migrations
💭 Notes
This long-running migration system leverages Celery for asynchronous task processing. However, a similar (and likely more robust) feature is being developed in Django, as detailed in DEP 14 - Background Workers. Once Django officially releases its built-in background worker system, this custom solution will be phased out in favor of the native implementation to better align with the Django ecosystem.