Document that the initial token is not a replay - #4982
Merged
Conversation
MateuszNaKodach
requested review from
hatzlj,
jangalinski and
laura-devriendt-lemon
and removed request for
a team
August 26, 2026 23:35
MateuszNaKodach
force-pushed
the
fixtoken-init-replay
branch
from
August 26, 2026 23:39
28cd560 to
784affe
Compare
MateuszNaKodach
added
Priority 2: Should
A streaming processor starting without a stored token handles its initial catch-up in ReplayStatus.REGULAR rather than as a replay. Document this behavior and the reasoning across the PooledStreamingEventProcessorConfiguration Javadoc, the streaming event processors reference page, and the projectors migration guide, including how to flag the initial catch-up as a replay when handlers rely on ReplayStatus.REPLAY to suppress side effects.
MateuszNaKodach
force-pushed
the
fixtoken-init-replay
branch
from
August 26, 2026 23:45
784affe to
e3decfa
Compare
Contributor
|
/backport axon-5.3.x |
Contributor
|
Successfully created backport PR for |
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.
In Axon Framework 5 a streaming processor starting without a stored token handles its initial catch-up under
ReplayStatus.REGULARrather than as a replay, unlike Axon Framework 4. This documents that behavior and the reasoning behind it across thePooledStreamingEventProcessorConfigurationJavadoc, the streaming event processors reference page, and the projectors migration guide. It adds a migration section with an AF4-vs-AF5 comparison table and a runnableReplayingInitialTokenExampleshowing how to restore the AF4 replay behavior by concluding the replay at the latest position. No behavioral code changes are included beyond Javadoc updates.