Delete messages up to a given sequence number.
Delete messages up to a given sequence number. The range to which this applies first capped by the lowest and highest sequence number for this persistenceId since DynamoDB requires individual deletes to be issued for every single event. The procedure is to first update the lowest sequence number to the new value and then delete the now unreplayable events—this is desirable because in the other order a replay may see partially deleted history.
Failures during purging are only logged and do not contribute to the call’s result.
TODO in principle replays should be inhibited while the purge is ongoing
Write all PersistentRepr in the AtomicWrite provided
Write all PersistentRepr in the AtomicWrite provided
If there are any errors serializing (preparing the batch writes), then we must return a Future.success(Failure) as the result. This is needed to be compliant with Akka Persistence 2.4
Contains a list of persistentRepr that need to be persisted atomically
a successfully completed Future that contains either a Success or Failure
Write all messages in a sequence of AtomicWrites.
Write all messages in a sequence of AtomicWrites. Care must be taken to not have concurrent writes happening that touch the highest sequence number. The current implementation is the simplest with this guarantee in that it will run each AtomicWrite in sequence without even batching those that could be batched. The most common case is that there is just one message in total anyway.