Pengchao Wang e4234fbdcf collecting kValue type tombstone ... Summary: In our testing cluster, we found large amount tombstone has been promoted to kValue type from kMerge after reaching the top level of compaction. Since we used to only collecting tombstone in merge operator, those tombstones can never be collected. This PR addresses the issue by adding a GC step in compaction filter, which is only for kValue type records. Since those record already reached the top of compaction (no earlier data exists) we can safely remove them in compaction filter without worrying old data appears. This PR also removes an old optimization in cassandra merge operator for single merge operands. We need to do GC even on a single operand, so the optimation does not make sense anymore. Closes https://github.com/facebook/rocksdb/pull/2855 Reviewed By: sagar0 Differential Revision: D5806445 Pulled By: wpc fbshipit-source-id: 6eb25629d4ce917eb5e8b489f64a6aa78c7d270b		2017-09-18 16:27:12 -07:00
..
main/java/org/rocksdb	collecting kValue type tombstone	2017-09-18 16:27:12 -07:00
test/java/org/rocksdb	JNI support for ReadOptions::iterate_upper_bound	2017-09-14 18:28:20 -07:00