Releases: Eventuous/eventuous
Releases · Eventuous/eventuous
0.6.3
What's Changed
- Fixed the partitioned consumer bug when it didn't commit checkpoints correctly after starting from the beginning
- Made the concurrency limit configurable
- Fixed the re-subscribe bug for ESDB subscriptions, in the last version a dropped subscription would not recover
- Elastic connector by @alexeyzimarev in #73
Full Changelog: 0.6.2...0.6.3
0.6.1
0.6.0
What's Changed
- Subscriptions Next by @alexeyzimarev in #52
- Added a simple retry handling with Polly for #7 by @alexeyzimarev in #55
- Consume pipe by @alexeyzimarev in #56
- More logs by @alexeyzimarev in #58
- Telemetry improvements by @alexeyzimarev in #62
- Add an interface to help register transformation services by @alexeyzimarev in #63
- Custom telemetry tags by @alexeyzimarev in #68
Full Changelog: 0.5.15...0.6.0
0.6.0-rc.6
What's Changed
- Added the partitioned consume with sequenced acknowledgements. Currently only works with EventStoreDB subscriptions.
0.6.0-rc.3
What's Changed
- Subscriptions Next by @alexeyzimarev in #52
- Added a simple retry handling with Polly for #7 by @alexeyzimarev in #55
- Consume pipe by @alexeyzimarev in #56
Full Changelog: 0.5.15...0.6.0-rc.3
0.5.15
- When the EventStoreDB encounters an error, it will produce a warning in the logs, not an error
- Google PubSub subscription not stopping properly fixed
0.5.13
Breaking
IAggregateStore
got a new functionExists
IEventStore
got a new functionStreamExists
Fixes
- Logging in
EsdbEventStore
caused error log entries when handling commands withOnAny
0.5.12
Breaking
- Event handlers need to process
ReceivedEvent
EventHandler
needs an optionalTypeMapper
argument to check events mapping- Better errors from the type mapper mean different exception types produced for unmapped events
- Better errors from
EsdbEventStore
mean different exception types produced when append or read fails IEventHandler
has a new function to add the subscription loggerIEventHandler
doesn't needSubscriptionId
Fixes
- Event handler issues with wrong event type being handled
- Reading long aggregate streams won't break
- Mongo projections broke down between releases
- Subscriptions weren't properly registered as hosted services with the new way to register them
Features
- Subscription logging produces better messages
- Subscription logs get injected into event handlers for scoped logging
- Better logging for
EsdbEventStore
- Subscription logs its registered handlers on startup
EventHandler
logs what events it can process on startupEventHandler
checks if all the events it can process are registered in the type map
0.5.3
- Removed the
SubscriptionId
abstract property fromEventHandler
as it's no longer used - Changed
IOptionsSnapshot
toIOptionsMonitor
as the snapshot is scoped, but subscriptions are singletons
0.5.1
Breaking
- Removed
SubscriptionQueue
from RMQ subscriptions, useSubscriptionId
as the queue name. Aligned with PubSub. - App service
OnNew
andOnNewAsync
don't need thegetId
function. - When the app service handles a command with
OnNew(Async)
, it won't assign the id to the state. You have to do it yourself using the event.
Non-breaking
- Fixed
AddSubscription
without options configuration function - Moved aggregate instantiation to aggregate factory registry, allowing custom aggregate factories
- Added new DI registrations in Eventuous.AspNetCore