Is your feature request related to a problem? Please describe.
We have some (large) events that don't effect future command validations that we'd like to avoid reading when hydrating the aggregate. Currently there is no capability to server-side filter events using readStream
Describe the solution you'd like
Allow server-side filtering events similar to readAll (obviously just on eventName not streamName)
Describe alternatives you've considered
I've thought about moving these events to other streams but: A: we might decide to implement validation based on these events in the future. B: it breaks up the stream history for quickly understanding what has occurred on a stream when debugging.
Additional context
N/A
Is your feature request related to a problem? Please describe.
We have some (large) events that don't effect future command validations that we'd like to avoid reading when hydrating the aggregate. Currently there is no capability to server-side filter events using
readStreamDescribe the solution you'd like
Allow server-side filtering events similar to
readAll(obviously just on eventName not streamName)Describe alternatives you've considered
I've thought about moving these events to other streams but: A: we might decide to implement validation based on these events in the future. B: it breaks up the stream history for quickly understanding what has occurred on a stream when debugging.
Additional context
N/A