Hello again, We've been discussing this a bit more today, and I wanted to amend my tip, since we'll be moving away from `deleteMessage`. Another discussion explaining "why?" can be found here on github: https://github.com/akka/akka/issues/15428
So my corrected advice would be somewhat among the lines of: * use PersistentActor - validate events before persisting; This should avoid "wrong events". * but something wrong could happen in theory, then: * we suggest bringing the actor into a consistent state, and performing a snapshot * since the snapshot will have seqNr > seqNr(wrongEvents), recovery will start from the snapshot * so you didn't have to change your past (aka. fiddle with it), but the work can continue from that recovered-snapshotted state. I hope this helps! If there's more concrete use cases you'd like to discuss please bring them up! :-) -- kornad -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
