Contribution policy

Contributions via GitHub pull requests are gladly accepted from their original author. Along with any pull requests, please state that the contribution is your original work and that you license the work to the project under the project's open source license. Whether or not you state this explicitly, by submitting any copyrighted material via pull request, email, or other means you agree to license the material under the project's open source license and warrant that you have the legal authority to do so.

Configuration

Configuring the query API

The query API can be configured by overriding the defaults by placing the following in application.conf:

inmemory-read-journal {
# Absolute path to the write journal plugin configuration section to get the event adapters from
write-plugin = "inmemory-journal"
# there are two modes; sequence or uuid. If set to "sequence" and NoOffset will be requested, then
# the query will return Sequence offset types. If set to "uuid" and NoOffset will be requested, then
# the query will return TimeBasedUUID offset types. When the query is called with Sequence then
# the query will return Sequence offset types and if the query is called with TimeBasedUUID types then
# the query will return TimeBasedUUID offset types.
offset-mode = "sequence"
# ask timeout on Futures
ask-timeout = "10s"
# New events are retrieved (polled) with this interval.
refresh-interval = "100ms"
# How many events to fetch in one query (replay) and keep buffered until they
# are delivered downstreams.
max-buffer-size = "100"
}

Clearing Journal and Snapshot messages

It is possible to manually clear the journal an snapshot storage, for example:

offset-mode

akka-persistence-query introduces akka.persistence.query.Offset, an ADT that defines akka.persistence.query.NoOffset, akka.persistence.query.Sequence and akka.persistence.query.TimeBasedUUID. These offsets can be used when using the queries akka.persistence.query.scaladsl.EventsByTagQuery2 and akka.persistence.query.scaladsl.CurrentEventsByTagQuery2 to request and offset in the stream of events.

Because akka-persistence-inmemory implements both the Sequence-based number offset strategy as the TimeBasedUUID strategy it is required to configure the inmemory-read-journal.offset-mode="sequence". This way akka-persistence-inmemory knows what kind of journal it should emulate when a NoOffset type is requested. EventEnvelope will contain either a Sequence when the configuration is sequence or a TimeBasedUUID when the configuration is uuid.

By default the setting is sequence.

query and event-adapters

Write plugins (ie. akka-persistence-plugins that write events) can define event adapters. These event adapters can be reused when executing a query so that the EventEnvelope contains the application domain event and not the data-model representation of that event. Set the inmemory-read-journal.write-plugin="inmemory-journal" and configure it with the write plugin name (defaults to the inmemory-journal).

Refresh Interval

The async query API uses polling to query the journal for new events. The refresh interval can be configured eg. "1s" so that the journal will be polled every 1 second. This setting is global for each async query, so the allPersistenceId, eventsByTag and eventsByPersistenceId queries.

Max Buffer Size

When an async query is started, a number of events will be buffered and will use memory when not consumed by a Sink. The default size is 100.

How to get the ReadJournal using Scala

The ReadJournal is retrieved via the akka.persistence.query.PersistenceQuery extension:

The returned event stream is unordered and you can expect different order for multiple executions of the query.

When using the allPersistenceIds query, the stream is not completed when it reaches the end of the currently used persistenceIds, but it continues to push new persistenceIds when new persistent actors are created.

When using the currentPersistenceIds query, the stream is completed when the end of the current list of persistenceIds is reached, thus it is not a live query.

The stream is completed with failure if there is a failure in executing the query in the backend journal.

EventsByPersistenceIdQuery and CurrentEventsByPersistenceIdQuery

eventsByPersistenceId and currentEventsByPersistenceId is used for retrieving events for a specific PersistentActor identified by persistenceId.

You can retrieve a subset of all events by specifying fromSequenceNr and toSequenceNr or use 0L and Long.MaxValue respectively to retrieve all events. Note that the corresponding sequence number of each event is provided in the EventEnvelope, which makes it possible to resume the stream at a later point from a given sequence number.

The returned event stream is ordered by sequence number, i.e. the same order as the PersistentActor persisted the events. The same prefix of stream elements (in same order) are returned for multiple executions of the query, except for when events have been deleted.

The stream is completed with failure if there is a failure in executing the query in the backend journal.

EventsByTag and CurrentEventsByTag

eventsByTag and currentEventsByTag are used for retrieving events that were marked with a given tag, e.g. all domain events of an Aggregate Root type.

To tag events you'll need to create an Event Adapter that will wrap the event in a akka.persistence.journal.Tagged class with the given tags. The Tagged class will instruct the persistence plugin to tag the event with the given set of tags. The persistence plugin will not store the Tagged class in the journal. It will strip the tags and payload from the Tagged class, and use the class only as an instruction to tag the event with the given tags and store the payload in the message field of the journal table.

The EventAdapter must be registered by adding the following to the root of application.conf Please see the demo-akka-persistence-jdbc project for more information. The identifier of the persistence plugin must be used which for the inmemory plugin is inmemory-journal.

You can retrieve a subset of all events by specifying offset, or use 0L to retrieve all events with a given tag. The offset corresponds to an ordered sequence number for the specific tag. Note that the corresponding offset of each event is provided in the EventEnvelope, which makes it possible to resume the stream at a later point from a given offset.

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.

The returned event stream contains only events that correspond to the given tag, and is ordered by the creation time of the events, The same stream elements (in same order) are returned for multiple executions of the same query. Deleted events are not deleted from the tagged event stream.

2.4.17.2 (2017-02-16)

2.5.0.1-M1 (2017-02-16)

Fix for PR #31 'eventsByTag including substrings of tag' by jibbers42, thanks!

Tags will be matched against the whole tag so tag 'foo' will be matched against 'foo' and not 'fo' or 'f' which was the previous behavior.

2.4.17.1 (2017-02-12)

Fix for PR #31 'eventsByTag including substrings of tag' by jibbers42, thanks!

Tags will be matched against the whole tag so tag 'foo' will be matched against 'foo' and not 'fo' or 'f' which was the previous behavior.

2.4.17.0 (2017-02-11)

Akka 2.4.16 -> 2.4.17

2.4.16.0 (2017-01-29)

New versioning scheme; now using the version of Akka with the akka-persistence-inmemory version appended to it, starting from .0

Support for Akka 2.4.16

Support akka 2.11.x and 2.12.x

Changed how the byTag queries work, the requested offset is excluding, so if a materialized stream is created, when you ask for Sequence(2) for example, you will get Sequence(3) and so on so this is for the use case when you store the lastest offset on the read side, you can just put that value in the query and the stream will continue with the next offset, no need to manually do the plus-one operation.

2.5.0.0-M1 (2017-01-29)

New versioning scheme; now using the version of Akka with the akka-persistence-inmemory version appended to it, starting from .0

Changed how the byTag queries work, the requested offset is excluding, so if a materialized stream is created, when you ask for Sequence(2) for example, you will get Sequence(3) and so on so this is for the use case when you store the lastest offset on the read side, you can just put that value in the query and the stream will continue with the next offset, no need to manually do the plus-one operation.

1.3.18 (2016-12-21)

Akka 2.4.14 -> 2.4.16

1.3.17 (2016-12-08)

Scala 2.12.0 -> 2.12.1

1.3.16 (2016-11-22)

Akka 2.4.13 -> 2.4.14

1.3.15 (2016-11-19)

Akka 2.4.12 -> 2.4.13

1.3.14 (2016-11-03)

cross scala 2.11.8 and 2.12.0 build

1.3.13 (2016-11-01 - Birthday Edition!)

Implemented support for the akka.persistence.query.TimeBasedUUID.

You should set the new configuration key inmemory-read-journal.offset-mode = "uuid", defaults to sequence to produce EventEnvelope2 that contain TimeBasedUUID offset fields.

1.3.12 (2016-10-28)

Akka 2.4.11 -> 2.4.12

Support for the new queries CurrentEventsByTagQuery2 and EventsByTagQuery2, please read the akka-persistence-query documentation to see what has changed.

The akka-persistence-inmemory plugin only supports the akka.persistence.query.NoOffset or akka.persistence.query.Sequence offset types.

There is no support for the akka.persistence.query.TimeBasedUUID offset type. When used, akka-persistence-inmemory will throw an IllegalArgumentException.

1.3.11 (2016-10-23)

Scala 2.11.8 and 2.12.0-RC2 compatible

1.3.10 (2016-09-30)

Akka 2.4.10 -> 2.4.11

1.3.9 (2016-09-22)

As event adapters are no first class citizins of akka-persistence-query (yet), a workaround based on the configuration of akka-persistence-cassandra has been implemented in the inmemory journal based on the work of Yury Gribkov. Basically, the query-journal will look for a write-plugin entry in the inmemory-read-journal configuration of your application.conf that must point to the writePluginId that will write the events to the journal. That writePlugin has all event adapters configured and if applicable, those event adapters will be used to adapt the events from the data-model to the application-model effectively you should have application-model events in your EventEnvelope if configured correctly.

Removed the non-official and never-to-be-used bulk loading interface

1.3.8 (2016-09-07)

Akka 2.4.9 -> Akka 2.4.10

1.3.7 (2016-08-21)

Fix for EventsByPersistenceId should terminate when toSequenceNumber is reached as pointed out by monktastic, thanks!

1.3.6 (2016-08-20)

Akka 2.4.9-RC2 -> Akka 2.4.9

1.3.6-RC2 (2016-08-06)

Akka 2.4.9-RC1 -> 2.4.9-RC2

1.3.6-RC1 (2016-08-03)

Akka 2.4.8 -> 2.4.9-RC1

1.3.5 (2016-07-23)

Support for the non-official bulk loading interface akka.persistence.query.scaladsl.EventWriter added. I need this interface to load massive amounts of data, that will be processed by many actors, but initially I just want to create and store one or more events belonging to an actor, that will handle the business rules eventually. Using actors or a shard region for that matter, just gives to much actor life cycle overhead ie. too many calls to the data store. The akka.persistence.query.scaladsl.EventWriter interface is non-official and puts all responsibility of ensuring the integrity of the journal on you. This means when some strange things are happening caused by wrong loading of the data, and therefor breaking the integrity and ruleset of akka-persistence, all the responsibility on fixing it is on you, and not on the Akka team.

1.3.4 (2016-07-17)

Codacy code cleanup release.

1.3.3 (2016-07-16)

No need for Query Publishers with the new akka-streams API.

1.3.2 (2016-07-09)

Journal entry 'deleted' fixed, must be set manually.

1.3.1 (2016-07-09)

Akka 2.4.7 -> 2.4.8,

Behavior of akka-persistence-query *byTag query should be up to spec,

Refactored the inmemory plugin code base, should be more clean now.

1.3.0 (2016-06-09)

Removed the queries eventsByPersistenceIdAndTag and currentEventsByPersistenceIdAndTag as they are not supported by Akka natively and can be configured by filtering the event stream.