Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mark grouphashes seen, then delete unseen ones #81134

Open
lobsterkatie opened this issue Nov 21, 2024 · 0 comments
Open

Mark grouphashes seen, then delete unseen ones #81134

lobsterkatie opened this issue Nov 21, 2024 · 0 comments

Comments

@lobsterkatie
Copy link
Member

Once we have a sense of the rate at which we see distinct grouphashes and are confident we can safely do this, apply the new-years-hanger effect to grouphashes:

  • Run a migration to mark them all unseen (new status value)
  • Each time we see one, mark it seen
  • Wait 90 days
  • Run another migration to delete any which haven't been seen

Once metadata is fully rolled out (and so we can distinguish newly-created hashes from old ones by the date_added value, or lack thereof), we might start by just deleting all older grouphashes missing a group.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant