Closed Bug 1689758 Opened 4 years ago Closed 4 years ago

Set table retention period on pioneer-citp-news-disinfo dataset to 3 months

Categories

(Data Platform and Tools :: General, task, P2)

task
Points:
1

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: amiyaguchi, Assigned: amiyaguchi)

References

Details

Attachments

(1 file)

The retention period of the pioneer-citp-news-disinfo tables should be set to 3 months so we are regularly removing raw data that is no longer necessary. We will first need to confirm that the CITP group has an aggregate pipeline set up before we start to let date partitions expire from the stable tables.

I believe we should be able to set mozPipelineMetadata.expiration_policy.delete_after_days to 90 days in defaults.schema.json

:whd, can you confirm that setting the mozPipelineMetadata should set the expiration policy within the pioneer/rally projects as it does on shared-prod? Does it require any intervention on your part?

Flags: needinfo?(whd)

(In reply to Anthony Miyaguchi [:amiyaguchi] from comment #1)

:whd, can you confirm that setting the mozPipelineMetadata should set the expiration policy within the pioneer/rally projects as it does on shared-prod?

It should, and this is the correct way to specify retention.

Does it require any intervention on your part?

Yes. By design, any change to retention is considered to be a destructive operation that requires an operator to approve the deployment.

Flags: needinfo?(whd)
Assignee: nobody → amiyaguchi
See Also: → 1690126
Depends on: 1690139
Blocks: 1690637

I'm going to call this closed, despite the lack of a schema deploy due to recent issues with bug 1690112. I've filed a new bug that will be the retention period going forward in bug 1690637.

No longer blocks: 1690637
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Component: Datasets: General → General
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: