Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings
Discussion options

services.AddSubscription<AllStreamSubscription, AllStreamSubscriptionOptions>(
"MainProjection",
builder => builder
.UseCheckpointStore()
.AddEventHandler()
.AddEventHandler<>() --> Added to existing thing
.WithPartitioningByStream(2));

When I added ThirdProjection / event handler , It start listening to new event maybe because of the checkpoint store ?
But I wanted it to listen to stream from the start of Main Projection only for this projection and not for existing projection.

Can you suggest something here ?

You must be logged in to vote

Subscriptions start from the checkpoint stored in the checkpoint store by subscription id. Adding a new event handler does not force the subscription to replay all the events for that particular handler; it will continue from the last know checkpoints. It's all described in the docs.

If you add a new handler that needs to start from scratch, you either need to replay everything by deleting the subscription checkpoint or create a new subscription for that handler alone.

Replies: 2 comments · 3 replies

Comment options

This is urgent and concerning issue
Can someone help me here?

You must be logged in to vote
0 replies
Comment options

Subscriptions start from the checkpoint stored in the checkpoint store by subscription id. Adding a new event handler does not force the subscription to replay all the events for that particular handler; it will continue from the last know checkpoints. It's all described in the docs.

If you add a new handler that needs to start from scratch, you either need to replay everything by deleting the subscription checkpoint or create a new subscription for that handler alone.

You must be logged in to vote
3 replies
@bartelink
Comment options

or create a new subscription for that handler alone.

(when it's reached the tail, you can then collapse the handler into the other one, if that still makes sense)

@alexeyzimarev
Comment options

Yeah, that was implicit from my side :)

I can think of something to make it work, as it could be useful, but I am not sure when. It would require changing the checkpointing quite substantially as every handler would need to have its own checkpoint.

@bartelink
Comment options

Yes definitely wasn't expanding that for you, Alexey!
I'd say in general you don't want to be creating checkpoints/consumer groups per handler as that's not free - better to default to having groups that you can move handlers between and/or reset as a batch and then let people put things into groups of one if they need specific control for something

Answer selected by alexeyzimarev
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
🙏
Q&A
Labels
None yet
3 participants
Morty Proxy This is a proxified and sanitized view of the page, visit original site.