=pro fixup in PR validation logging logic
This commit is contained in:
parent
874d07c0ae
commit
561d46e2da
5 changed files with 46 additions and 15 deletions
|
|
@ -362,11 +362,11 @@ Persisting, deleting and replaying messages can eitehr succeed or fail.
|
|||
+---------------------------------+-----------------------------+-------------------------------+-----------------------------------+
|
||||
| ``persist`` / ``persistAsync`` | persist handler invoked | ``onPersistFailure`` | Actor is stopped. |
|
||||
| | +-------------------------------+-----------------------------------+
|
||||
| | | ``onPersistRejected`` | --- |
|
||||
| | | ``onPersistRejected`` | No automatic actions. |
|
||||
+---------------------------------+-----------------------------+-------------------------------+-----------------------------------+
|
||||
| ``recovery`` | ``RecoverySuccess`` | ``onRecoveryFailure`` | Actor is stopped. |
|
||||
+---------------------------------+-----------------------------+-------------------------------+-----------------------------------+
|
||||
| ``deleteMessages`` | ``DeleteMessagesSuccess`` | ``DeleteMessagesFailure`` | --- |
|
||||
| ``deleteMessages`` | ``DeleteMessagesSuccess`` | ``DeleteMessagesFailure`` | No automatic actions. |
|
||||
+---------------------------------+-----------------------------+-------------------------------+-----------------------------------+
|
||||
|
||||
The most important operations (``persist`` and ``recovery``) have failure handlers modelled as explicit callbacks which
|
||||
|
|
@ -488,9 +488,25 @@ saved snapshot matches the specified ``SnapshotSelectionCriteria`` will replay a
|
|||
Snapshot deletion
|
||||
-----------------
|
||||
|
||||
A persistent actor can delete individual snapshots by calling the ``deleteSnapshot`` method with the sequence number and the
|
||||
timestamp of a snapshot as argument. To bulk-delete snapshots matching ``SnapshotSelectionCriteria``, persistent actors should
|
||||
use the ``deleteSnapshots`` method.
|
||||
A persistent actor can delete individual snapshots by calling the ``deleteSnapshot`` method with the sequence number of
|
||||
when the snapshot was taken.
|
||||
|
||||
To bulk-delete a range of snapshots matching ``SnapshotSelectionCriteria``,
|
||||
persistent actors should use the ``deleteSnapshots`` method.
|
||||
|
||||
Snapshot status handling
|
||||
------------------------
|
||||
|
||||
Saving or deleting snapshots can either succeed or fail – this information is reported back to the persistent actor via
|
||||
status messages as illustrated in the following table.
|
||||
|
||||
============================================== ========================== ==============================
|
||||
**Method** **Success** **Failure message**
|
||||
============================================== ========================== ==============================
|
||||
``saveSnapshot(Any)`` ``SaveSnapshotSuccess`` ``SaveSnapshotFailure``
|
||||
``deleteSnapshot(Long)`` ``DeleteSnapshotSuccess`` ``DeleteSnapshotFailure``
|
||||
``deleteSnapshots(SnapshotSelectionCriteria)`` ``DeleteSnapshotsSuccess`` ``DeleteSnapshotsFailure``
|
||||
============================================== ========================== ==============================
|
||||
|
||||
.. _at-least-once-delivery-java-lambda:
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue