-
Notifications
You must be signed in to change notification settings - Fork 104
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
Set additional_deletion_requests_v1 retention to 775 days #6901
base: main
Are you sure you want to change the base?
Conversation
This comment has been minimized.
This comment has been minimized.
@@ -16,3 +16,4 @@ bigquery: | |||
type: day | |||
field: submission_timestamp | |||
require_partition_filter: false | |||
expiration_days: 775 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@BenWu should we define this value inside bqetl_project.yaml
which could be used as a default value when retention policy is enabled on a table? From my understanding most tables should share the same retention policy. If need be we could always allow for explicitly overwriting it in the metadata.yaml.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IMO since retention is still new, it would be better to have retention explicitly set for every table rather than having a default value so there are fewer surprises. When we get to a point where we all assume derived client tables default to 775 days then we can set a default. There's also going to be a check that retention is set so all the existing tables should be covered
Integration report for "Add client_level table type"
|
Description
Per policy discussion in https://mozilla-hub.atlassian.net/browse/DSRE-1799, the retention of deletion requests should be equal to the longest retained data subject to the deletion request. That would be 760 for pings https://github.com/mozilla/probe-scraper/blob/cf4abcf2e94e1453315f44e2b2d45ab1ba8a29d2/repositories.yaml#L1336-L1342 and eventually 775 for derived data
cc @akkomar
Related Tickets & Documents
Reviewer, please follow this checklist
┆Issue is synchronized with this Jira Task