ProjectTech4DevAI / ProjectTech4DevAI/kaapi-backend
Cleanup: Automated data retention system
Aperta
@Prajna1999 ci sta già lavorando.
Dal 4/9/2026.
- Lingua principale
- Python
- Stelle
- 18
- Fork
- 10
- Merge medio
- 2g 20h
- PR unite (30g)
- 14
Descrizione
Is your feature request related to a problem?
We need a system to automatically clean up query and response data in the LLM calls table after a specified retention period. Without this, the database may become cluttered and inefficient.
Describe the solution you'd like
- Implement a cron job to purge query/response data after a configurable retention window (default 1 week).
- Handle one-time backlog separately from regular cron operations.
- Write a cleanup strategy document detailing cron design, batching, and backlog handling.
- Conduct a staging load test by duplicating ~20k LLM call rows ~5x in the
copy_devdatabase to measure cleanup time. Do not use production data. - Ensure S3 cleanup is managed separately and not included in the DB cron/migration code.
Original issue
Context
query + response data in the LLM calls table will be cleaned up via a cron job after a configurable retention window (starting with 1 week).
A step-by-step cleanup strategy doc is to be written (cron design, batching, one-time backlog handling).
Scope / Acceptance criteria
- Cron job to purge query/response data in the LLM calls table after a configurable retention window (default 1 week).
- Handle one-time backlog separately from steady-state cron.
- Write cleanup strategy doc (cron design, batching, backlog).
- Staging load test: reuse the empty
copy_devdatabase, duplicate staging's ~20k LLM call rows ~5x to reach ~1 lakh, and measure cleanup time. Do NOT pull prod data. - Keep S3 cleanup separate — do not bundle S3 deletion into the DB cron/migration code.
Notes
- Guardrails input/output data is retained separately (anonymized, tagged as product enhancement) and is NOT part of this cleanup.
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Valutazione
Questa issue non è ancora stata valutata.