rocksdb/utilities/redis
Zhongyi Xie 954b496b3f fix memory leak in two_level_iterator
Summary:
this PR fixes a few failed contbuild:
1. ASAN memory leak in Block::NewIterator (table/block.cc:429). the proper destruction of first_level_iter_ and second_level_iter_ of two_level_iterator.cc is missing from the code after the refactoring in https://github.com/facebook/rocksdb/pull/3406
2. various unused param errors introduced by https://github.com/facebook/rocksdb/pull/3662
3. updated comment for `ForceReleaseCachedEntry` to emphasize the use of `force_erase` flag.
Closes https://github.com/facebook/rocksdb/pull/3718

Reviewed By: maysamyabandeh

Differential Revision: D7621192

Pulled By: miasantreble

fbshipit-source-id: 476c94264083a0730ded957c29de7807e4f5b146
2018-04-15 17:26:26 -07:00
..
README Change namespace from leveldb to rocksdb 2013-10-04 11:59:26 -07:00
redis_list_exception.h rocksdb: Add missing override 2015-02-26 11:28:41 -08:00
redis_list_iterator.h Use nullptr instead of NULL / 0 more consistently. 2018-03-07 12:42:12 -08:00
redis_lists.cc Use nullptr instead of NULL / 0 more consistently. 2018-03-07 12:42:12 -08:00
redis_lists.h RocksDBLite 2014-04-15 13:39:26 -07:00
redis_lists_test.cc fix memory leak in two_level_iterator 2018-04-15 17:26:26 -07:00

This folder defines a REDIS-style interface for Rocksdb.
Right now it is written as a simple tag-on in the rocksdb::RedisLists class.
It implements Redis Lists, and supports only the "non-blocking operations".

Internally, the set of lists are stored in a rocksdb database, mapping keys to
values. Each "value" is the list itself, storing a sequence of "elements".
Each element is stored as a 32-bit-integer, followed by a sequence of bytes.
The 32-bit-integer represents the length of the element (that is, the number
of bytes that follow). And then that many bytes follow.


NOTE: This README file may be old. See the actual redis_lists.cc file for
definitive details on the implementation. There should be a header at the top
of that file, explaining a bit of the implementation details.