The documentation for the
markDeleted method states:
Marks this aggregate as deleted, instructing a repository to remove that aggregate at an appropriate time. Note that different repository implementations may react differently to aggregates marked for deletion. Typically, Event Sourced Repositories will ignore the marking and expect deletion to be provided as part of Event information.
I have two questions:
Q1: What exactly is the effect of calling
markDeleted() on an aggregate using event sourcing and Axon server?
Is it just that future commands and events routed to that aggregate will be rejected? No actual deletion of events will ever take place right? But Axon Server will somehow store that the aggregate is deleted? How does it do that? In the metadata of the last event or something?
Q2: Is it possible to see if an aggregate has been ‘marked deleted’ in the Axon Server UI?
Perhaps a setting which changes the background colour for the row containing the event which triggered the deletion to red or something to that effect?