Pulsar: subscription initial position (Earliest/Latest) (#3178)#3196
Merged
Conversation
Adds first-class cold-start control for new Pulsar subscriptions, the Pulsar analogue of the Kafka transport's BeginAtEarliest()/BeginAtLatest() (#3146). - PulsarEndpoint.SubscriptionInitialPosition (default Latest, matching DotPulsar) flows to the consumer (and retry consumer) via IConsumerBuilder.InitialPosition(...). - PulsarListenerConfiguration gains BeginAtEarliest(), BeginAtLatest(), and SubscriptionInitialPosition(SubscriptionInitialPosition) for explicit control. - Only affects the first read of a not-yet-existing subscription. Tests: config unit tests + integration tests proving Earliest replays messages published before the subscription existed and Latest consumes only messages published afterward. Docs updated with a "Subscription Initial Position" section. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This was referenced Jun 23, 2026
Closed
This was referenced Jul 9, 2026
This was referenced Jul 16, 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
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.
Part of the Pulsar re-evaluation epic #3176. Fixes #3178.
Adds first-class cold-start control for new Pulsar subscriptions — the Pulsar analogue of the Kafka transport's
BeginAtEarliest()/BeginAtLatest()(#3146).Changes
PulsarEndpoint.SubscriptionInitialPosition(defaultLatest, matching DotPulsar's own default) flows to the consumer and the retry consumer viaIConsumerBuilder.InitialPosition(...).PulsarListenerConfigurationgainsBeginAtEarliest(),BeginAtLatest(), andSubscriptionInitialPosition(SubscriptionInitialPosition).Tests
Latest;BeginAtEarliest/BeginAtLatest/explicit setter map correctly).Earliestreplays messages published before the subscription existed;Latestconsumes only messages published afterward.Docs
New "Subscription Initial Position" section in the Pulsar transport guide.
🤖 Generated with Claude Code