EventStore
Related Doc:
package scala
Retrieves an event from the store.
Retrieves an event from the store.
The cache key of the event to retrieve.
The event string.
Non-Option instance apply() version could be added for idiomatic Scala.
,Should return an Option[String] in Scala land.
Retrieves all handles for a specific project from the store.
Retrieves all handles for a specific project from the store.
The ID of the project.
A map of collection names to their event handles.
Removes an event from the store.
Removes an event from the store.
The handle of the event.
Stores an event in the store.
Stores an event in the store.
The ID of the project to which the collection belongs.
The collection to which the event will be added.
The event.
A handle which can be used to retrieve or remove the event from the store (a cache key).
Sets a maximum number of events that should be stored per-collection.
Sets a maximum number of events that should be stored per-collection. Eviction strategy may vary by implementation.
This could be moved to RamEventStore instead of being a formal part of the interface.
The number of events currently in the store.
The number of events currently in the store.
Long? The implementation in RamEventStore uses Longs for key/handle/ID, so…
,This should be an accessor method with private field, not public var.
An EventStore is an abstract store for events, intended primarily as a write cache for events to be flushed in batches, such as by a BatchWriterClient.
The documentation refers to "handles", which you can think of simply as cache keys or map keys in common parlance. The parameter naming is historical.
The data structure should be generalized from
,TrieMap&ListBufferThe handle/key type could be generic instead of
,Long.I'd like to change parameter names to
keybefore 1.0.