Initiate backfill for Focus Android without shredder mitigation#9581
Initiate backfill for Focus Android without shredder mitigation#9581lucia-vargas-a wants to merge 5 commits into
Conversation
There was a problem hiding this comment.
This PR adds a second backfill entry (dated 2026-06-15, status Initiate) to focus_android_derived/active_users_aggregates_v4/backfill.yaml for the 2026-04-15 to 2026-05-25 range, this time with shredder_mitigation: false, to update (rather than preserve) metrics affected by duplicate client_ids.
My main concern is a conflict between the entry's shredder_mitigation: false and the shredder_mitigation label still present on the table's metadata, which backfill validation requires to match for Initiate entries. Details inline. The start date is ~61 days before the entry date, well within the 775-day retention limit, and the prior entry is Complete, so the single-Initiate constraint is satisfied.
| Related Bug https://bugzilla.mozilla.org/show_bug.cgi?id=2042189. | ||
|
|
||
| This backfill does not use shredder mitigation because it requires an update of the metrics (not preserve), | ||
| thus a decrease is expected in the originally calculated metrics is expected after completing this backfill |
There was a problem hiding this comment.
nitpick: "is expected" is duplicated — "a decrease is expected in the originally calculated metrics is expected after completing this backfill". Drop one, e.g. "a decrease in the originally calculated metrics is expected after completing this backfill".
Integration report
|
…set back to true after.
Integration report
|
| level: gold | ||
| incremental: true | ||
| change_controlled: true | ||
| shredder_mitigation: false |
There was a problem hiding this comment.
Temporarily set to false. To be reverted after the backfill.
Integration report
|
Description
Backfill Focus Android active_users_aggregates_v4 without shredder mitigation.
Related Bug 2042189
Reviewer, please follow this checklist