You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This ticket continues work of #1575 (also related to #1573 and #1574).
How to handle populating the Asset Storage image new field?
Using a "data" migration to populate the field kept getting killed by the OS less than 1.5 hours into the process - most likely due to memory trying to update ~700k records. zsh: killed pipenv run ./manage.py migrate.
After consultation - even if the this code was modified to chunk the updates - as a "data" migration - the way Django handles it - may still not run fast enough for the application start up process to not loose connection.
For local development - built sql and directly update set the value of the asset storage_image database field. This approach is possible but not recommended for production.
Looking at creating a management command and/or "one off" celery task based on "data" migration logic @ queryset level.
The text was updated successfully, but these errors were encountered:
elainekamlley
changed the title
Build a process to populate the Storage image field value for existing assets
Admin S3 Object Deletion - Build a process to populate the Storage image field value for existing assets
Feb 2, 2022
This ticket continues work of #1575 (also related to #1573 and #1574).
How to handle populating the Asset Storage image new field?
Using a "data" migration to populate the field kept getting killed by the OS less than 1.5 hours into the process - most likely due to memory trying to update ~700k records.
zsh: killed pipenv run ./manage.py migrate
.For local development - built sql and directly update set the value of the asset storage_image database field. This approach is possible but not recommended for production.
Looking at creating a management command and/or "one off" celery task based on "data" migration logic @ queryset level.
The text was updated successfully, but these errors were encountered: