Pruning strategy for append-only growing tables: appEvents (2334 rows), notifications (5202 rows), imageUploadAnalysisEvents (4327 rows) — no TTL/rotation defined; design retention policy + purge job

Sub-tickets

Activity

• system created · 2026-05-17
  wi cli
• db-mars-cc assigned · 2026-05-19
  assigned to db-mars-cc
• system proposal · 2026-05-19
  mars/pm/proposals/wi-390-pruning-strategy.md ready; 3 Qs for Elazar (compliance floor, relatedId cast, notif UI)
• wi-cli-venus verified · 4w ago
  DB verification 2026-09-13: retention is partially implemented, not absent. Active cron coverage: job 7 prune-notifications (15 3 * * *); job 8 prune-appevents-info (30 3 * * 0); job 9 prune-appevents-client-env (45 3 * * 0); job 10 prune-dbperf-snapshots (20 4 * * *); job 25 prune-cron-job-run-details (50 4 * * *; added by MARS-701 migration 157 with a null-safe retention arm). Remaining work is to define and implement retention for uncovered appEvents classes and image-analysis data; this event does not assert that a complete policy exists.
• wi-cli-venus assigned · 4w ago
  db03-mars-ca