* expose memtable flush
This can be used to avoid log replays on startup, for example
* Add flush to RocksDbReadWriteRef.
* Remove atomic flush default.
---------
Co-authored-by: bhartnett <51288821+bhartnett@users.noreply.github.com>
* Add support for optimistic transaction db.
* Add keyMayExist to RocksDbRef.
* Add support for write batch with index.
* Allow empty keys to be used in API.
* Update readme.
* Add additional opts getters and setters for ReadOptionsRef and WriteOptionsRef. Updated BackupEngineOptionsRef to use newer c library type.
* Add majority of option type getter and setters.
* Revert some changes from prior PR https://github.com/status-im/nim-rocksdb/pull/48 which enable memory leak of options when not cleaned up manually.
* Clean up, add more tests and use correct free function for listColumnFamilies.
* Close opt types when opening database fails.
* Add autoClose flag to each opt type.
* Finish autoClose changes to prevent memory leaks.
* Refactor API to pass in column family handle instead of string.
* Check for unknown column family in getColFamilyHandle and update tests.
* Update column family function names. Remove redundant exists check.
Several options were mistakenly classified as db options when in fact
they are column family options - the C interface does not make this
distinction and instead puts them all under one umbrella.
This PR updates options to use nim setter/getter properties allowing
both read and write of most options - lots of options are exposed both
for reading and writing, but hey, one could always add _even more_ of
them - there's certainly no lack!
* Column families support (#34)
* Update library to support column families. If not specified, uses the 'default' column family.
* Added tests for column family changes.
* Update library version and readme.
* Updated the librocksdb c library to the latest stable version.
* Started rewrite of library.
* Commit library rewrite progress.
* Completed initial rewrite and refactored tests.
* Completed implementation of backup engine.
* Added tests for new types.
* Completed tests for existing features.
* Remove features not supported by older versions of RocksDB to fix CI (temporary fix).
* Remove flush before backup support from BackupEngine to fix CI.
* Transactions support (#36)
* Update library to support column families. If not specified, uses the 'default' column family.
* Added tests for column family changes.
* Update library version and readme.
* Updated the librocksdb c library to the latest stable version.
* Started rewrite of library.
* Commit library rewrite progress.
* Completed initial rewrite and refactored tests.
* Completed implementation of backup engine.
* Added tests for new types.
* Completed tests for existing features.
* Remove features not supported by older versions of RocksDB to fix CI (temporary fix).
* Remove flush before backup support from BackupEngine to fix CI.
* Implemented RocksDB iterator.
* Implemented pairs iterator.
* Completed implementation of WriteBatch with tests.
* Fix example code.
* Completed implementation of TransactionDb.
* Support setting default column family.
* Remove unneeded usage of var for ref type parameters.
* Completed transactiondb tests.
* Improve and refactor rocksdb test.
* Added support for ingesting sst files using the SstFileWriter. (#37)
* Create ColFamilyReadOnly and ColFamilyReadWrite types for using a specific column family.
* Use inline pragma for small procs and add lock to RocksDbRef type close to prevent double free.
* Added documentation for the public API.
* Initial implementation of sst filewriter.
* Added tests for sstfilewriter.
* Documentation minor improvements.
* Made del return a bool, and added clear.
What I've done here feels very awkward. Maybe I'm missing something,
but it looks to me like RocksDB doesn't support these operations in
any natural way.
These changes were made in order to get our implementation of
KvStoreRef for RocksDB working again after these changes to the
KvStoreRef interface:
8f0ae55353
I don't really recommend merging this; I think I'd prefer to just stop
trying to use this common KvStoreRef interface.
Still, if we do want to keep the common interface, I think this commit
will work well enough.
* Updated the tests to expect del to return a bool too.
* Leave the new `clear` operation unimplemented.
- added "--threads:on"
- fixed the Nim API tests and moved them to unittest
- added copyright header
- combined the 2 test file into tests/all.nim and set that as the
Nimble test target
- had Travis run that
- new "tempfile" dependency to create proper tempfiles + deleting them
at the end
- copied the error string to RocksDBResult
* error is a pointer to a cstring that the API will allocate on error
* if an error is returned, it must be free'd
* note missing tests for when error happens
The API is still very basic and suffering from multiple Nim issues
that will be resolved in the near future:
* destructors will handle the resource cleanup better
* converter concepts will enable a wider range of possible types
to be used as keys and values.
The API currently uses an ErrorResult type to communicate errors,
but RocksDB doesn't seem to have many recoverable failure modes
and I anticipate that the API will be migrated to use exceptions
once we get a bit more experience with RocksDB.
The C interface file was moved to a separate directory to make
nimble happy (`nimble check`).
Jacek Sieka
web3-developer
Adam Spitz
Ștefan Talpalaru
Yuriy Glukhov
Yuriy Glukhov
Zahary Karadjov
Mamy Ratsimbazafy
mratsim