Implement message archive for EF persistence - #5691
Open
rbev wants to merge 10 commits into
Open
Conversation
rbev
marked this pull request as ready for review
August 4, 2026 05:46
rbev
commented
Aug 4, 2026
Contributor
Author
There was a problem hiding this comment.
Note: the migration here shows up as a move in this PR because I had to delete the previous one that was not included in the snapshot for the migration that followed it. Deleting it and including it in this migration was the simplest path to making them consistent.
johnsimons
approved these changes
Aug 4, 2026
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.
This pull request introduces new archive-related entities to the EF Core persistence layer for both PostgreSQL and SQL Server, and updates the corresponding migration and model snapshot files. The main changes involve adding the
ArchiveOperationEntityand related tables, as well as updating or removing some fields and indexes to support new archiving and retry features.Key changes:
Archive and Retry Feature Additions
ArchiveOperationEntityand correspondingarchive_operationstable with fields for tracking archive operations, including batch and message counts, group info, and initiator details. [1] [2] [3]Schema and Index Updates
TypeandGroupIdfor thefailed_message_groupstable to optimize queries.Migration and Model Maintenance