akka.persistence.couchbase.javadsl
Same type of query as eventsByPersistenceId
but the event stream
is completed immediately when it reaches the end of the "result set".
Same type of query as eventsByPersistenceId
but the event stream
is completed immediately when it reaches the end of the "result set". Events that are
stored after the query is completed are not included in the event stream.
Same type of query as eventsByTag
but the event stream
is completed immediately when it reaches the end of the "result set"
unless it has received as many events as it has requested.
Same type of query as eventsByTag
but the event stream
is completed immediately when it reaches the end of the "result set"
unless it has received as many events as it has requested.
In that case it will request one more time before completing the stream.
Use NoOffset
when you want all events from the beginning of time.
To acquire an offset from a long unix timestamp to use with this query, you can use
akka.persistence.couchbase.UUIDs.timeBasedUUIDFrom.
Same type of query as persistenceIds
but the event stream
is completed immediately when it reaches the end of the "result set".
Same type of query as persistenceIds
but the event stream
is completed immediately when it reaches the end of the "result set". Events that are
stored after the query is triggered are not included in the event stream.
eventsByPersistenceId
is used to retrieve a stream of events for a particular persistenceId.
eventsByPersistenceId
is used to retrieve a stream of events for a particular persistenceId.
In addition to the offset
the EventEnvelope
also provides persistenceId
and sequenceNr
for each event. The sequenceNr
is the sequence number for the persistent actor with the
persistenceId
that persisted the event. The persistenceId
+ sequenceNr
is an unique
identifier for the event.
sequenceNr
and offset
are always the same for an event and they define ordering for events
emitted by this query. Causality is guaranteed (sequenceNr
s of events for a particular
persistenceId
are always ordered in a sequence monotonically increasing by one). Multiple
executions of the same bounded stream are guaranteed to emit exactly the same stream of events.
fromSequenceNr
and toSequenceNr
can be specified to limit the set of returned events.
The fromSequenceNr
and toSequenceNr
are inclusive.
Deleted events are also deleted from the event stream.
The stream is not completed when it reaches the end of the currently stored events,
but it continues to push new events when new events are persisted.
Corresponding query that is completed when it reaches the end of the currently
stored events is provided by currentEventsByPersistenceId
.
eventsByTag
is used for retrieving events that were marked with
a given tag, e.g.
eventsByTag
is used for retrieving events that were marked with
a given tag, e.g. all events of an Aggregate Root type.
To tag events you create an akka.persistence.journal.EventAdapter
that wraps the events
in a akka.persistence.journal.Tagged
with the given tags
.
You can use NoOffset
to retrieve all events with a given tag or
retrieve a subset of all events by specifying a TimeBasedUUID
offset
.
The offset of each event is provided in the streamed envelopes returned, which makes it possible to resume the stream at a later point from a given offset.
For querying events that happened after a long unix timestamp you can use akka.persistence.couchbase.UUIDs.timeBasedUUIDFrom to create the offset to use with this method.
In addition to the offset
the envelope also provides persistenceId
and sequenceNr
for each event. The sequenceNr
is the sequence number for the persistent actor with the
persistenceId
that persisted the event. The persistenceId
+ sequenceNr
is an unique
identifier for the event.
The returned event stream is ordered by the offset (timestamp), which corresponds
to the same order as the write journal stored the events, with inaccuracy due to clock skew
between different nodes. The same stream elements (in same order) are returned for multiple
executions of the query on a best effort basis. The query is using a Couchbase Indexes
that is eventually consistent, so different queries may see different
events for the latest events, but eventually the result will be ordered by the timestamp based
Couchbase ordering
field. To compensate for the the eventual consistency the query is
delayed to not read the latest events, see couchbase-journal.read.events-by-tag.eventual-consistency-delay
in reference.conf. However, this is only best effort and in case of network partitions
or other things that may delay the updates of the Couchbase indexes the events may be
delivered in different order (not strictly by their timestamp).
Deleted events are NOT deleted from the tagged event stream.
The stream is not completed when it reaches the end of the currently stored events,
but it continues to push new events when new events are persisted.
Corresponding query that is completed when it reaches the end of the currently
stored events is provided by currentEventsByTag
.
The stream is completed with failure if there is a failure in executing the query in the backend journal.
persistenceIds
is used to retrieve a stream of persistenceId
s.
persistenceIds
is used to retrieve a stream of persistenceId
s.
The stream emits persistenceId
strings.
The stream guarantees that a persistenceId
is only emitted once and there are no duplicates.
Order is not defined. Multiple executions of the same stream (even bounded) may emit different
sequence of persistenceId
s.
The stream is not completed when it reaches the end of the currently known persistenceId
s,
but it continues to push new persistenceId
s when new events are persisted.
Corresponding query that is completed when it reaches the end of the currently
known persistenceId
s is provided by currentPersistenceIds
.
Note the query is inefficient, especially for large numbers of persistenceId
s, because
of limitation of current internal implementation providing no information supporting
ordering/offset queries. The query uses Couchbase's select distinct
capabilities.
More importantly the live query has to repeatedly execute the query each refresh-interval
,
because order is not defined and new persistenceId
s may appear anywhere in the query results.
Data Access Object for arbitrary queries or updates.
(Since version ) see corresponding Javadoc for more information.
Java API:
akka.persistence.query.javadsl.ReadJournal
implementation for Couchbase.It is retrieved with:
CassandraReadJournal queries = PersistenceQuery.get(system).getReadJournalFor(CouchbaseReadJournal.class, CouchbaseReadJournal.Identifier());
Corresponding Scala API is in akka.persistence.couchbase.scaladsl.CouchbaseReadJournal.
Configuration settings can be defined in the configuration section with the absolute path corresponding to the identifier, which is
"couchbase-journal.read"
for the default CouchbaseReadJournal#Identifier. Seereference.conf
.