materialization phase 1: worker + store + flag-gated read path - #418
Merged
Conversation
… schema (steps 1-2)
…ad path (steps 3-5,8)
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.
Steps 1-5 + 8 of the materialization plan: Next-free loader core (src/lib/materialize/load.ts), versioned snapshot schema with per-provider staleness meta, Upstash store client with atomic pointer-swap publish, Railway worker (worker/index.ts, pnpm worker) sweeping 27 aggregates/60s + 96 variants/5min with carry-forward of values+series+panels, and a READ_FROM_STORE=1 flag-gated read path in spec.ts with live fallback (snapshot >30min old falls through). Validated end-to-end: real sweep published 27 benches in 171s via the public gateway, snapshots read back complete (HL 75 providers/75 series/10 panels). Flag is OFF everywhere; zero behavior change until enabled.