pmemkv
pmemkv copied to clipboard
pmem
Key/Value Datastore for Persistent Memory
perhaps we should add some "fuzzy" tests, doing random operations on our kv database. There are multiple choices for that; some of them include: - the actual fuzzy testing framework...
## Please provide a reproduction of the bug: run tests on devdax path, e.g.: ```sh pmemkv/build # cmake .. -DTEST_DIR=/dev/dax0.0 # make tests # ctest -R cmap__put_get_remove__default_0_none --output-on-failure ``` ##...
## Please provide a reproduction of the bug: If compile our examples standalone (which require pmemkv and it requires tbb) and tbb package is delivered without pkg-config file (*.pc) it...
## Environment Information pmemkv downloaded as a zip, e.g. from github ## Actual behavior: `VERSION` variable is not set, hence `make package` will create a package with empty "version=" parameter...
# FEAT: Engine migration support ## Rationale Need API for efficient moving existing data from existing database created using one engine, to another one. On top of such API may...
# FEAT: Add test engine ## Rationale There is need for tests of error handling and statuses in pmemkv, and exceptions in bindings. Most generic approach is to implement engine,...
# FEAT: add is_prev() method in Iterators API ## Rationale For now we have in documentation of prev(): > If the previous record exists, returns pmem::kv::status::OK, otherwise pmem::kv::status::NOT_FOUND is returned...
# FEAT: Relate statuses with functions ## Rationale In theory, each function can return any status which makes a correct error handling code very verbose. In C++ (and bindings) we...
# FEAT: Better error handling in robinhood ## Rationale For now, in case of an error in the C-part of robinhood engine, we don't know the real reason for the...
## Rationale We want to ~~test all examples in the CI and~~ make sure CMake file for each example is proper. ## Description Make use of "per example CMake" (e.g....