Mayank Agarwal bf66c10b13 Use KeyMayExist for WriteBatch-Deletes ... Summary: Introduced KeyMayExist checking during writebatch-delete and removed from Outer Delete API because it uses writebatch-delete. Added code to skip getting Table from disk if not already present in table_cache. Some renaming of variables. Introduced KeyMayExistImpl which allows checking since specified sequence number in GetImpl useful to check partially written writebatch. Changed KeyMayExist to not be pure virtual and provided a default implementation. Expanded unit-tests in db_test to check appropriately. Ran db_stress for 1 hour with ./db_stress --max_key=100000 --ops_per_thread=10000000 --delpercent=50 --filter_deletes=1 --statistics=1. Test Plan: db_stress;make check Reviewers: dhruba, haobo Reviewed By: dhruba CC: leveldb, xjin Differential Revision: https://reviews.facebook.net/D11745		2013-07-23 13:36:50 -07:00
..
shell
db_crashtest.py	[RocksDB] add back --mmap_read options to crashtest	2013-06-19 16:15:59 -07:00
db_crashtest2.py	[RocksDB] add back --mmap_read options to crashtest	2013-06-19 16:15:59 -07:00
db_repl_stress.cc
db_stress.cc	Use KeyMayExist for WriteBatch-Deletes	2013-07-23 13:36:50 -07:00
ldb.cc	[RocksDB] Expose LDB functioanality as a library call - clients can build their own LDB binary with additional options	2013-04-11 20:21:49 -07:00
ldb_test.py	Enhance the ldb tool to support ttl databases	2013-05-15 12:10:00 -07:00
reduce_levels_test.cc	[Rocksdb] codemod NULL to nullptr in tools/*.cc	2013-03-21 10:45:57 -07:00
sst_dump.cc	[RocksDB] cleanup EnvOptions	2013-06-12 11:17:19 -07:00