Repository navigation
Enable prepared listing JSON after production backfill - #1770
Merged
Merged
Conversation
This branch was successfully deployed
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.
Enable prepared listing reads on the already deployed v1.8.7 release. This changes only the read-path flag; image, release commit, two replicas, CPU/pools, DB/storage and networking stay fixed.
Production deployment and backup succeeded. Bounded backfill prepared 198098 existing records; coverage was 198114/198114 with zero invalid indexes and no identity skips. A read-only sample of 384 production rows (first, last and recently updated records) matched fresh normalization and produced equivalent typed/prepared/fallback pages, including current metadata and cursors. Both replicas are healthy with zero restarts; sampled pool queues and health errors were zero.
Require current-head CI and reviewed read-only production preview before merge. After automatic apply, verify prepared-row counters, public responses and real traffic health. Rollback sets preparedListingJSON=false; retain additive migration018 and all data. Focused correctness/encoding proof supports this optimization; failed/confounded broad replay is not claimed as capacity acceptance.