You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My SnapshotUpgrader need to retrieve data from the aggregate's events.
For this, it use the IEventStore instance.
But it should only take into account events whose sequence is less than or equal to that of the snapshot.
This information should be an argument of the UpgradeAsync method.
Moreover IEventStore should provide a method to get a range of events.
We hope you are doing well. We noticed that this issue has not seen any activity in the past 90 days.
We consider this issue to be stale and will be closing it within the next seven days.
If you still require assistance with this issue, please feel free to reopen it or create a new issue.
We hope you are doing well. We noticed that this issue has not seen any activity in the past 90 days.
We consider this issue to be stale and will be closing it within the next seven days.
If you still require assistance with this issue, please feel free to reopen it or create a new issue.
Long-time lurker here. Decided that it's time to contribute a bit to the repository.
The underlying idea of enabling the event store to load domain events within a given sequence-number range makes sense to me. I would go ahead and prepare a PR if still relevant.
Regarding your snapshot upgrading question, would it help if the specific snapshots in your application would carry their respective aggregate Id in the payload? That way you would have access to it when upgrading from one snapshot version to the other, no?
In case you found a solution to the problem, I would be curious what it was :)
While an old issue, having more metadata available in the snapshot upgraders makes a lot of sense. Since it involves breaking changes, its a good candidate for a v2.
@nlips while it doesn't save you from your current problem, you could add the information you need to the snapshot yourself, e.g. add a property that holds the aggregate ID or other meta data you might need.
Activity
nlips commentedon Jan 18, 2022
Actually I can't use IEventStore... I don't have the aggregate's id !
github-actions commentedon Apr 8, 2023
Hello there!
We hope you are doing well. We noticed that this issue has not seen any activity in the past 90 days.
We consider this issue to be stale and will be closing it within the next seven days.
If you still require assistance with this issue, please feel free to reopen it or create a new issue.
Thank you for your understanding and cooperation.
Best regards,
EventFlow
github-actions commentedon Jul 8, 2023
Hello there!
We hope you are doing well. We noticed that this issue has not seen any activity in the past 90 days.
We consider this issue to be stale and will be closing it within the next seven days.
If you still require assistance with this issue, please feel free to reopen it or create a new issue.
Thank you for your understanding and cooperation.
Best regards,
EventFlow
SeWaS commentedon Oct 30, 2023
Hello there 👋
Long-time lurker here. Decided that it's time to contribute a bit to the repository.
The underlying idea of enabling the event store to load domain events within a given sequence-number range makes sense to me. I would go ahead and prepare a PR if still relevant.
Regarding your snapshot upgrading question, would it help if the specific snapshots in your application would carry their respective aggregate Id in the payload? That way you would have access to it when upgrading from one snapshot version to the other, no?
In case you found a solution to the problem, I would be curious what it was :)
Cheers
Merge pull request #1008 from SeWaS/issue/919/snapshot-upgrader-metadata
rasmus commentedon Dec 24, 2024
While an old issue, having more metadata available in the snapshot upgraders makes a lot of sense. Since it involves breaking changes, its a good candidate for a v2.
rasmus commentedon Dec 31, 2024
@nlips while it doesn't save you from your current problem, you could add the information you need to the snapshot yourself, e.g. add a property that holds the aggregate ID or other meta data you might need.