trait CurrentEventsBySliceStartingFromSnapshotsQuery extends ReadJournal
Ordering
- Alphabetic
- By Inheritance
Inherited
- CurrentEventsBySliceStartingFromSnapshotsQuery
- ReadJournal
- AnyRef
- Any
Implicitly
- by any2stringadd
- by StringFormat
- by Ensuring
- by ArrowAssoc
- Hide All
- Show All
Visibility
- Public
- Protected
Abstract Value Members
- abstract def currentEventsBySlicesStartingFromSnapshots[Snapshot, Event](entityType: String, minSlice: Int, maxSlice: Int, offset: Offset, transformSnapshot: Function[Snapshot, Event]): [EventEnvelope[Event], NotUsed]
Same as EventsBySliceStartingFromSnapshotsQuery but with the purpose to use snapshots as starting points and thereby reducing number of events that have to be loaded.
Same as EventsBySliceStartingFromSnapshotsQuery but with the purpose to use snapshots as starting points and thereby reducing number of events that have to be loaded. This can be useful if the consumer start from zero without any previously processed offset or if it has been disconnected for a long while and its offset is far behind.
Same type of query as EventsBySliceStartingFromSnapshotsQuery.eventsBySlicesStartingFromSnapshots but the event stream is completed immediately when it reaches the end of the "result set".
- abstract def sliceForPersistenceId(persistenceId: String): Int
- abstract def sliceRanges(numberOfRanges: Int): [[, Integer]]
A plugin may optionally support this query by implementing this trait.
API May Change