Doc - Add warning note about persistence message deletion (#21486)

This commit is contained in:
Richard Imaoka 2016-10-09 06:07:06 +09:00 committed by Patrik Nordwall
parent 224ca30331
commit 55729bdbbf
2 changed files with 12 additions and 0 deletions

View file

@ -384,6 +384,12 @@ Deleting messages in event sourcing based applications is typically either not u
up until the sequence number of the data held by that snapshot can be issued to safely delete the previous events
while still having access to the accumulated state during replays - by loading the snapshot.
.. warning::
If you are using :ref:`persistence-query-java`, query results may be missing deleted messages in a journal,
depending on how deletions are implemented in the journal plugin.
Unless you use a plugin which still shows deleted messages in persistence query results,
you have to design your application so that it is not affected by missing messages.
The result of the ``deleteMessages`` request is signaled to the persistent actor with a ``DeleteMessagesSuccess``
message if the delete was successful or a ``DeleteMessagesFailure`` message if it failed.

View file

@ -372,6 +372,12 @@ Deleting messages in event sourcing based applications is typically either not u
up until the sequence number of the data held by that snapshot can be issued to safely delete the previous events
while still having access to the accumulated state during replays - by loading the snapshot.
.. warning::
If you are using :ref:`persistence-query-scala`, query results may be missing deleted messages in a journal,
depending on how deletions are implemented in the journal plugin.
Unless you use a plugin which still shows deleted messages in persistence query results,
you have to design your application so that it is not affected by missing messages.
The result of the ``deleteMessages`` request is signaled to the persistent actor with a ``DeleteMessagesSuccess``
message if the delete was successful or a ``DeleteMessagesFailure`` message if it failed.