Repository navigation
Add parsed OCR baseline migration to match production - #566
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
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.
Add nullable
coupon_ocr.parsed_baselineJSONB storage for replayed parser results and their provenance. The baseline records parsed monetary/date fields, parser revision, reference time, parsing timestamp, and raw-response checksum; actual coupon records are unchanged.V23 was mistakenly applied directly with Flyway outside CI/CD before this PR. This is the exact migration file already recorded in production's Flyway history. Merging it reconciles the repository with production; CI/CD should recognize V23 as applied and skip executing it again. All future production migrations must run through CI/CD.
Validation: Flyway successfully applied V23, and a read-only verification confirmed 2,364 saved baselines with zero raw-response checksum mismatches. The production backfill has completed; no private corpus, backfill tooling, or parser changes are included.