Repository navigation
Release v3.10.1
Batches appended through event source definitions no longer silently guard only the first entry of an event source id.
Fixed
- A batch where one event source id has guarded entries with different guards (different stream ids, or different definitions with different dimensions) now fails with
{:incompatible_concurrency_scopes, event_source_id, guards}before anything is read or sent, instead of dropping the later guards. Entries with the same effective guard share one scope, entries without dimensions never suppress a later guarded entry, and an explicit:concurrency_scopeor separate batches remain the remedy. (part of #102)