raboof/pekko
1
0
Fork 0
Code Issues Pull requests Projects Releases 6 Packages Wiki Activity Actions 10

Merge pull request #18721 from eshepelyuk/highestSeqNoKeptAfterMsgDeletion-18559-eshepelyuk

Browse source 
=per #18559 TCK tests for highestSequenceNr not reset after journal message deletion
This commit is contained in:
Patrik Nordwall 2015-10-20 19:41:48 +02:00
commit ba12c04026
5 changed files with 114 additions and 83 deletions
Download patch file Download diff file Expand all files Collapse all files

1
akka-persistence/src/main/scala/akka/persistence/journal/AsyncRecovery.scala
View file

@ -51,6 +51,7 @@ trait AsyncRecovery {
* number after recovery as the starting point when persisting new events.
* This sequence number is also used as `toSequenceNr` in subsequent call
* to [[#asyncReplayMessages]] unless the user has specified a lower `toSequenceNr`.
* Journal must maintain the highest sequence number and never decrease it.
*
* This call is protected with a circuit-breaker.
*

1
akka-persistence/src/main/scala/akka/persistence/journal/AsyncWriteJournal.scala
View file

@ -215,6 +215,7 @@ trait AsyncWriteJournal extends Actor with WriteJournalBase with AsyncRecovery {
* (inclusive).
*
* This call is protected with a circuit-breaker.
* Message deletion doesn't affect the highest sequence number of messages, journal must maintain the highest sequence number and never decrease it.
*/
def asyncDeleteMessagesTo(persistenceId: String, toSequenceNr: Long): Future[Unit]