Skip to content

[release/v1.0] [DEV-866] PinnedByCorrelation #219

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 21, 2025
Merged

[release/v1.0] [DEV-866] PinnedByCorrelation #219

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions docs/api/persistent-subscriptions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -175,6 +175,18 @@ The main aim of this strategy is to decrease the likelihood of concurrency and
ordering issues while maintaining load balancing. This is **not a guarantee**,
and you should handle the usual ordering and concurrency issues.

### PinnedByCorrelation

The PinnedByCorrelation strategy is a consumer strategy available for persistent subscriptions
It ensures that events with the same correlation id are consistently delivered to the same
consumer within a subscription group.

:::note
This strategy requires database version 21.10.1 or later. You can only create a persistent subscription
with this strategy. To change the strategy, you must delete the existing subscription and create a
new one with the desired settings.
:::

## Updating a subscription group

You can edit the settings of an existing subscription group while it is running,
Expand Down