Skip to content

Initiate backfill for Focus Android without shredder mitigation#9581

Open
lucia-vargas-a wants to merge 5 commits into
mainfrom
bug_2042189_focus_android_aua_regular_backfill
Open

Initiate backfill for Focus Android without shredder mitigation#9581
lucia-vargas-a wants to merge 5 commits into
mainfrom
bug_2042189_focus_android_aua_regular_backfill

Conversation

@lucia-vargas-a

Copy link
Copy Markdown
Contributor

Description

Backfill Focus Android active_users_aggregates_v4 without shredder mitigation.

Related Bug 2042189

Reviewer, please follow this checklist

@lucia-vargas-a lucia-vargas-a requested a review from a team as a code owner June 15, 2026 15:33
@lucia-vargas-a lucia-vargas-a requested a review from gkabbz June 15, 2026 15:33
@lucia-vargas-a lucia-vargas-a changed the title Initiate backfill for Focus Android WITHOUT shredder mitigaiton Initiate backfill for Focus Android without shredder mitigation Jun 15, 2026

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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".

@scholtzan

Copy link
Copy Markdown
Collaborator

Integration report

@lucia-vargas-a lucia-vargas-a requested a review from a team as a code owner June 15, 2026 15:55
@scholtzan

Copy link
Copy Markdown
Collaborator

Integration report

level: gold
incremental: true
change_controlled: true
shredder_mitigation: false

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Temporarily set to false. To be reverted after the backfill.

@scholtzan

Copy link
Copy Markdown
Collaborator

Integration report

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

Successfully merging this pull request may close these issues.

2 participants