Add documentation for recalc option
This commit is contained in:
parent
8a9db9e75e
commit
20a7a22571
3 changed files with 11 additions and 7 deletions
|
@ -120,7 +120,7 @@ Three potential recovery strategies are supported to provide some flexibility fo
|
|||
|
||||
- retain - on compaction KeyDeltas are retained in the Journal, only values are removed.
|
||||
|
||||
- recalc (not yet implemented) - the compaction rules assume that on recovery the key changes will be recalculated by comparing the change with the current database state. In recovery the key changes will be recalculated by comparing the change with the current database state.
|
||||
- recalc - the compaction rules assume that on recovery the key changes will be recalculated by comparing the change with the current database state. In recovery the key changes will be recalculated by comparing the change with the current database state. A user-defined function should be passed in at startup to achieve this recalculation (to override `leveled_head:diff_indexspeacs/3`).
|
||||
|
||||
### Hot Backups
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue