rocksdb

fork of https://github.com/oxigraph/rocksdb and https://github.com/facebook/rocksdb for nextgraph and oxigraph

Igor Canadi 26f5dd9a5a TablePropertiesCollectorFactory Summary: This diff addresses task #4296714 and rethinks how users provide us with TablePropertiesCollectors as part of Options. Here's description of task #4296714: I'm debugging #4295529 and noticed that our count of user properties kDeletedKeys is wrong. We're sharing one single InternalKeyPropertiesCollector with all Table Builders. In LOG Files, we're outputting number of kDeletedKeys as connected with a single table, while it's actually the total count of deleted keys since creation of the DB. For example, this table has 3155 entries and 1391828 deleted keys. The problem with current approach that we call methods on a single TablePropertiesCollector for all the tables we create. Even worse, we could do it from multiple threads at the same time and TablePropertiesCollector has no way of knowing which table we're calling it for. Good part: Looks like nobody inside Facebook is using Options::table_properties_collectors. This means we should be able to painfully change the API. In this change, I introduce TablePropertiesCollectorFactory. For every table we create, we call `CreateTablePropertiesCollector`, which creates a TablePropertiesCollector for a single table. We then use it sequentially from a single thread, which means it doesn't have to be thread-safe. Test Plan: Added a test in table_properties_collector_test that fails on master (build two tables, assert that kDeletedKeys count is correct for the second one). Also, all other tests Reviewers: sdong, dhruba, haobo, kailiu Reviewed By: kailiu CC: leveldb Differential Revision: https://reviews.facebook.net/D18579		11 years ago
build_tools	Fix building RocksDB in paths containing spaces -- quote path names in Makefile and build_detect_platform.	11 years ago
coverage	Disable the html-based coverage report by default	11 years ago
db	TablePropertiesCollectorFactory	11 years ago
doc	doc: table_stats_collectors -> table_properties_collectors.	11 years ago
examples	Make it easier to start using RocksDB	11 years ago
hdfs	Env to add a function to allow users to query waiting queue length	11 years ago
helpers/memenv	Expose in memory Env to the world	11 years ago
include	TablePropertiesCollectorFactory	11 years ago
java	[Java] Temporary set the number of BG threads based on the number of BG compactions.	11 years ago
linters	allow lambda function syntax in cpplint	11 years ago
port	Make rocksdb work with all versions of lz4	11 years ago
table	TablePropertiesCollectorFactory	11 years ago
tools	Make RocksDB work with newer gflags	11 years ago
util	TablePropertiesCollectorFactory	11 years ago
utilities	BackupableDBTest thread-safe	11 years ago
.arcconfig	Improve/fix bugs for the cpp linter	11 years ago
.clang-format	A script that automatically reformat affected lines	11 years ago
.gitignore	Add TARGETS to gitignore	11 years ago
CONTRIBUTING.md	New CLA form	11 years ago
HISTORY.md	TablePropertiesCollectorFactory	11 years ago
INSTALL.md	Better INSTALL.md and Makefile rules	11 years ago
LICENSE	Fix copyright year	11 years ago
Makefile	Fix building RocksDB in paths containing spaces -- quote path names in Makefile and build_detect_platform.	11 years ago
PATENTS	Fix the patent format	11 years ago
README.md	Make it easier to start using RocksDB	11 years ago
ROCKSDB_LITE.md	RocksDBLite	11 years ago

README.md

RocksDB: A Persistent Key-Value Store for Flash and RAM Storage

RocksDB is developed and maintained by Facebook Database Engineering Team. It is built on on earlier work on LevelDB by Sanjay Ghemawat (sanjay@google.com) and Jeff Dean (jeff@google.com)

This code is a library that forms the core building block for a fast key value server, especially suited for storing data on flash drives. It has an Log-Structured-Merge-Database (LSM) design with flexible tradeoffs between Write-Amplification-Factor (WAF), Read-Amplification-Factor (RAF) and Space-Amplification-Factor (SAF). It has multi-threaded compactions, making it specially suitable for storing multiple terabytes of data in a single database.

Start with example usage here: https://github.com/facebook/rocksdb/tree/master/examples

See doc/index.html and github wiki for more explanation.

The public interface is in include/. Callers should not include or rely on the details of any other header files in this package. Those internal APIs may be changed without warning.

Design discussions are conducted in https://www.facebook.com/groups/rocksdb.dev/