You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's infrastructure-specific, but we need a way to perform an operation on new streams using the native event store client feature, like setting the stream meta using EventStoreClient. It can also be abstracted out, so only the specific things can be set, like max-age or max-count.
The reason for this would be to make the archive process automated, so people won't need to set the stream meta manually.
We can expect that the max-age and max-count properties would be aggregate-specific, so it cannot be done on the aggregate store level. It must be either some separate map, or be a part of the application service.
The text was updated successfully, but these errors were encountered:
It's infrastructure-specific, but we need a way to perform an operation on new streams using the native event store client feature, like setting the stream meta using
EventStoreClient
. It can also be abstracted out, so only the specific things can be set, like max-age or max-count.The reason for this would be to make the archive process automated, so people won't need to set the stream meta manually.
We can expect that the max-age and max-count properties would be aggregate-specific, so it cannot be done on the aggregate store level. It must be either some separate map, or be a part of the application service.
The text was updated successfully, but these errors were encountered: