ref(outcomes-routing): always downsample data older than 30 days#7424
Merged
Conversation
phacops
reviewed
Sep 24, 2025
phacops
reviewed
Sep 30, 2025
phacops
reviewed
Sep 30, 2025
MeredithAnya
force-pushed
the
meredith/EAP-295
branch
from
fda7362 to
2445f1f
Compare
phacops
approved these changes
Oct 1, 2025
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
2 participants
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.
Soon we will be only storing up to 30 days of data in the non-sampled table (aka tier 1). When that is the case we want to make sure that any queries that query for data that is older than 30 days will not route to tier 1.
Added
enforce_unsampled_retentionruntime config so that we can test this out and because we don't expect to enforce this right away.