I think that Event revisions and Snapshots are both awesome features of the Axon Framework.
However, I don’t quite get how these two features support each other.
Saying that I have a new event revision that adds a field for example. What happens now if that “extended” event influences now the aggregate state (and that aggregate has already a snapshots).
With a snapshots the old state of the aggregate will be saved, so the aggregate state loaded from the snapshot would not be the same as if all events (included upcased ones) would be used to create it.
Am I missing something here or this is simply a thing to consider when using both snapshots and event up-casting?
Thanks in advance…