PostHog/posthog

Feature Flag Hash Key Overrides table can grow out of control

Open

#16,885 opened on 2023年8月2日

GitHub で見る
 (5 comments) (0 reactions) (0 assignees)Python (16,704 stars) (988 forks)batch import
backlogbugfeature/feature-flagsgood first issueteam/flags-platform

説明

Bug description

The hashkeyoverrides table can grow seriously out of control because it keeps all rows for stale flags. We cascade delete, but since flags are soft deleted, this table doesn't clean itself up automatically, which makes it hard to keep the size manageable

Additional context

We should run a nightly/weekly job , or whenever a flag is deleted, to remove stale rows from this table.

Thank you for your bug report – we love squashing them!

コントリビューターガイド

技術スタック
pythonpostgresql
領域
backenddatabase
Issue 種別
bug
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
3
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
1-2 days
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
stale
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
clear
前提条件
Django ORMdatabase cleanup strategies
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
60
調査方針
The issue requires implementing a cleanup mechanism for the hashkeyoverrides table. Currently, flags are soft deleted but the overrides table retains rows. A scheduled job (e.g., using Celery) should delete rows where the associated flag is soft deleted. Alternatively, a post delete hook could be added. Review the existing model definitions in posthog/models/feature flag.py and the soft deletion logic. Ensure the job is idempotent and efficient for large tables.
Feature Flag Hash Key Overrides table can grow out of control · PostHog/posthog#16885 | Good First Issue