Igor Canadi 00b26c3a83 JSONDocument ... Summary: After evaluating options for JSON storage, I decided to implement our own. The reason is that we'll be able to optimize it better and we get to reduce unnecessary dependencies (which is what we'd get with folly). I also plan to write a serializer/deserializer for JSONDocument with our own binary format similar to BSON. That way we'll store binary JSON format in RocksDB instead of the plain-text JSON. This means less storage and faster deserialization. There are still some inefficiencies left here. I plan to optimize them after we develop a functioning DocumentDB. That way we can move and iterate faster. Test Plan: added a unit test Reviewers: dhruba, haobo, sdong, ljin, yhchiang Reviewed By: haobo Subscribers: leveldb Differential Revision: https://reviews.facebook.net/D18831		2014-06-20 11:14:14 +02:00
..
backupable_db.h	Add share_files_with_cheksum option to BackupEngine	2014-05-02 17:08:55 -07:00
db_ttl.h	Support for adding TTL-ed column family	2014-04-28 20:34:20 -07:00
geo_db.h	RocksDBLite	2014-04-15 13:39:26 -07:00
json_document.h	JSONDocument	2014-06-20 11:14:14 +02:00
stackable_db.h	Support for adding TTL-ed column family	2014-04-28 20:34:20 -07:00
utility_db.h	Support for adding TTL-ed column family	2014-04-28 20:34:20 -07:00