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
..
leveldb	Use KeyMayExist for WriteBatch-Deletes	2013-07-23 13:36:50 -07:00
utilities	Bring read_only into ttl	2013-05-10 16:13:26 -07:00