Repository navigation
chore(stats): retire legacy s3 lake - #52515
Merged
Merged
Conversation
This was referenced Oct 1, 2026
adamdotdevin
changed the title
adamdotdevin
force-pushed
the
remove-s3-lake
branch
from
October 1, 2026 22:41
ccc0a4a to
a677e97
Compare
adamdotdevin
marked this pull request as ready for review
October 2, 2026 03:21
3 tasks done
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue for this PR
Legacy S3 lake retirement; no separate issue.
Type of change
What does this PR do?
Remove the retired S3 table, catalog, Athena workgroup, query results and delivery-error bucket. Move LakeVpc and LakeCluster into stats.ts with the same names and arguments so R2 stats sync keeps its deployed network and service.
The production raw archive is fully verified: 20,772,423,321 records, 378 date/type groups and all original fields. Development history and delivery failures are also preserved in R2. Analytics removal is complete in anomalyco/anomaly#676; the inference reader is deployed in anomalyco/anomaly#677 and #679. The normal scheduled hourly refresh and archive/live Requests rebuild succeeded on the new reader. Obsolete inference AWS bindings and repository credentials are removed. The three requested manual checks remain on hold, with their published data unchanged.
How did you verify your code works?
Dev and production previews add exactly seven expected lake deletions compared with unchanged-source previews. Builder, image and task revisions also appear in both baselines; the VPC, cluster and ECS service are preserved. All hosted checks pass. Both current stats-sync services are healthy and read R2 generation data. Full raw readback and representative hourly, boundary, Financials, User Cost and monthly Requests controls pass; the complete latest mixed-source Requests collector also passes read-only production queries.
Screenshots / recordings
No UI change.
Checklist