Configure automatic snapshotting at 500 events per aggregate #46
Labels
No labels
Blocked
Duplicate
MoSCoW/Could Have
MoSCoW/Must Have
MoSCoW/Should Have
Points/1
Points/13
Points/2
Points/21
Points/3
Points/5
Points/8
Priority/Backlog
Priority/Critical
Priority/High
Priority/Low
Priority/Medium
State/Completed
State/In progress
State/In review
State/Paused
State/Unverified
State/Verified
State/Wont Do
Type/Bug
Type/Epic
Type/Feature
Type/Legendary
Type/Task
Type/Testing
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
#21 Epic: Projection schema and rebuild capability
aethyr/Aethyr
#22 Epic: Event sourcing configuration and enablement
aethyr/Aethyr
Reference: aethyr/Aethyr#46
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Metadata
feat(event-sourcing): configure automatic snapshotting thresholdfeature/m1-v12-snapshot-configBackground
sequent_setup.rbhas a comment placeholder# Configure snapshottingwith nothing configured. The default snapshot threshold inServerConfigis 100 but the spec calls for 500.Expected Behavior
Snapshotting is configured with a default threshold of 500 events per aggregate, configurable via
ServerConfig[:snapshot_threshold].Acceptance Criteria
SequentSetup.configureconfig.yamldocumentssnapshot_thresholdkey with default 500Subtasks
sequent_setup.rbconfig.yamldefault to 500bundle exec rake unit, fix any errorsDefinition of Done
This issue is complete when all subtasks are done, commit created on the specified branch, PR submitted and merged.