Add TCK tests for replay bounds across a deletion gap#3076
Merged
He-Pin merged 1 commit intoJun 16, 2026
Conversation
Motivation: pekko-persistence-jdbc apache#517 added regression tests for replaying messages whose range overlaps a deleted prefix. Port the same coverage to the shared persistence TCK so all journal implementations meet one contract.
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.
Motivation
PR #517 on
pekko-persistence-jdbcadded regression tests for replaying messages whose range overlaps a deleted prefix (the gap left byDeleteMessagesTo). @pjfanning asked for the same coverage in the shared TCK so all journal implementations meet one contract.Test cases
Add five
JournalSpeccases. Each deletes messages 1..3 (4..5 survive) and then replays a different window:RecoverySuccessonlyRecoverySuccessonly