feat(ml): drop image_record.tagger_predictions — image_prediction is sole store (#768 step 3) #96
Reference in New Issue
Block a user
Delete Branch "dev"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Final step of #768. Read cutover verified in prod (suggestions + allowlist read
image_prediction; backfill complete at 908k rows / 51k images).Change
image_record.tagger_predictions. The model field is removed;tagger_model_versionstays as the "tagged / current?" signal.tag_and_embedno longer dual-writes the JSON —image_predictionis the only write path. The backfill needs-tagging check switched totagger_model_version IS NULL.image_prediction.Deploy notes
docker service scale curator_ml-worker=0) during the migration —0046'sDROP COLUMNtakes a briefACCESS EXCLUSIVEonimage_record, and an old ml-worker still writing the JSON column would error against the new schema.:latestre-pull and roll all services; web runs0046on boot.pg_dumpis logical). Optional, off-hours:VACUUM (FULL, ANALYZE) image_recordto return the ~100 GB physical disk to the OS — it takes an ACCESS EXCLUSIVE lock for the duration (likely minutes; only live data is copied), so run it quiesced.Dev CI green (run 895: lint, backend, integration incl. the 0046 migration, frontend-build).
🤖 Generated with Claude Code