... | ... | @@ -137,4 +137,12 @@ rocksdb:release_snapshot(Snapshot) |
|
|
|
|
|
[Backup](how-to-backup-rocksdb) allows users to create periodic incremental backups in a remote file system (think about HDFS or S3) and recover from any of them.
|
|
|
|
|
|
[Checkpoints](Checkpoints) provides the ability to take a snapshot of a running RocksDB database in a separate directory. Files are hardlinked, rather than copied, if possible, so it is a relatively lightweight operation. |
|
|
\ No newline at end of file |
|
|
[Checkpoints](Checkpoints) provides the ability to take a snapshot of a running RocksDB database in a separate directory. Files are hardlinked, rather than copied, if possible, so it is a relatively lightweight operation.
|
|
|
|
|
|
### Merge Operator
|
|
|
|
|
|
Starting in version 0.21.0, Erlang Rocksdb support a [Merge Operator](Erlang-Merge-Operator) for Erlang data types.
|
|
|
|
|
|
RocksDB offers the possibility of doing appends to existing key values efficiently through the use of a [merge operator]. This operator is a user-provided callback that knows how to merge the old value ("the message") and the new value ("the delta") into a single value ("the merged value").
|
|
|
|
|
|
The [Erlang Merge Operator](Erlang-Merge-Operator) allows two combine two values of the same Erlang data type in a single value. As long as your data is stored as Erlang binary term (encoded using the `term_to_binary` function), , it should be possible to apply a single predefined merge operator in order to take advantage of the RocksDB merge operation. |
|
|
\ No newline at end of file |