Repository navigation
Keep time-dependent analytics reads scoped to affected sessions - #30
Merged
Merged
Conversation
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
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.
Future-dated events becoming visible currently route overview reads through every session's detailed event arrays. Store a materialized visibility deadline per session and combine compact summaries with detailed calculations only for the affected sessions. Deadline-driven refreshes also reuse unaffected session rows instead of rebuilding their entire bucket.
Date-aligned time series use the same split while preserving exact partial-day and historical fallbacks. Per-video completion keeps its precise segment path, including rewinds across midnight. The additive materialized column remains compatible with existing insert statements; format 6 publication prevents readers from using incompatible generations.
Validation: all repository CI checks pass, along with 32 targeted session tests, strict Credo, security enforcement, formatting and precommit checks. Regression comparisons cover overview, unique-watch, time-series, incremental-copy and cross-day rewind correctness, including concurrent reads.