Well, in this case you are using the in memory saga repository. And your saga is managing its own state (vs using our state machine saga language). So removal of completed sagas really depends on whatever process you create to sweep and clear the repository of old sagas.
If you use the state machine language, you can define the states and transitions, and also specify a RemoveWhen expression that determines if the saga should be removed from the repository.
We rarely do this in production systems, however, and allow the sagas to remain in a Completed state (which is part of the state machine definition) so that they are available for audits.
Through mindful use of table partitioning this can be quite effective and highly performant.
____
Chris Patterson
> --
> You received this message because you are subscribed to the Google Groups "masstransit-discuss" group.
> To post to this group, send email to
masstrans...@googlegroups.com.
> To unsubscribe from this group, send email to
masstransit-dis...@googlegroups.com.
> For more options, visit this group at
http://groups.google.com/group/masstransit-discuss?hl=en.
>