This commit permits a projection consumer to receive a volatile offset store for the purposes of always sourcing events from the start of a journal. This is used, for example, when sourcing events for an http connection where no start offset is provided.
The store can be used with all both sequence and timestamp offsets.
As an extra convenience, the tuple returned from the offset store task functions is now passed directly into the the projection consumer. The projection consumer will take care of running the offset store task and saves the caller from having to spawn it. Under the covers, the offset store task is joined with the projection consumer task, which are subsequently spawned as one.
This commit permits a projection consumer to receive a volatile offset store for the purposes of always sourcing events from the start of a journal. This is used, for example, when sourcing events for an http connection where no start offset is provided.
The store can be used with all both sequence and timestamp offsets.
As an extra convenience, the tuple returned from the offset store task functions is now passed directly into the the projection consumer. The projection consumer will take care of running the offset store task and saves the caller from having to spawn it. Under the covers, the offset store task is joined with the projection consumer task, which are subsequently spawned as one.
Related: https://github.com/lightbend/akka-projection-temp/pull/23