ee0e2201e0
Summary: This moves the current Getting Started that we have hosted over to our new GitHub pages infra. Next will be to move the blog over, along with some updates and maintenance of links, etc. in the new infra. Depends on: https://reviews.facebook.net/D62985 Test Plan: Visual Reviewers: IslamAbdelRahman, lgalanis Reviewed By: lgalanis Subscribers: andrewkr, dhruba, leveldb Differential Revision: https://reviews.facebook.net/D63051
79 lines
2.8 KiB
Markdown
79 lines
2.8 KiB
Markdown
---
|
||
docid: getting-started
|
||
title: Getting started
|
||
layout: docs
|
||
permalink: /docs/getting-started.html
|
||
---
|
||
|
||
## Overview
|
||
|
||
The RocksDB library provides a persistent key value store. Keys and values are arbitrary byte arrays. The keys are ordered within the key value store according to a user-specified comparator function.
|
||
|
||
The library is maintained by the Facebook Database Engineering Team, and is based on [LevelDB](https://github.com/google/leveldb), by Sanjay Ghemawat and Jeff Dean at Google.
|
||
|
||
This overview gives some simple examples of how RocksDB is used. For the story of why RocksDB was created in the first place, see [Dhruba Borthakur’s introductory talk](https://github.com/facebook/rocksdb/blob/gh-pages/intro.pdf?raw=true) from the Data @ Scale 2013 conference.
|
||
|
||
## Opening A Database
|
||
|
||
A rocksdb database has a name which corresponds to a file system directory. All of the contents of database are stored in this directory. The following example shows how to open a database, creating it if necessary:
|
||
|
||
```c++
|
||
#include <assert>
|
||
#include "rocksdb/db.h"
|
||
|
||
rocksdb::DB* db;
|
||
rocksdb::Options options;
|
||
options.create_if_missing = true;
|
||
rocksdb::Status status =
|
||
rocksdb::DB::Open(options, "/tmp/testdb", &db);
|
||
assert(status.ok());
|
||
...
|
||
```
|
||
|
||
If you want to raise an error if the database already exists, add the following line before the rocksdb::DB::Open call:
|
||
|
||
```c++
|
||
options.error_if_exists = true;
|
||
```
|
||
|
||
## Status
|
||
|
||
You may have noticed the `rocksdb::Status` type above. Values of this type are returned by most functions in RocksDB that may encounter
|
||
an error. You can check if such a result is ok, and also print an associated error message:
|
||
|
||
```c++
|
||
rocksdb::Status s = ...;
|
||
if (!s.ok()) cerr << s.ToString() << endl;
|
||
```
|
||
|
||
## Closing A Database
|
||
|
||
When you are done with a database, just delete the database object. For example:
|
||
|
||
```c++
|
||
/* open the db as described above */
|
||
/* do something with db */
|
||
delete db;
|
||
```
|
||
|
||
## Reads And Writes
|
||
|
||
The database provides Put, Delete, and Get methods to modify/query the database. For example, the following code moves the value stored under `key1` to `key2`.
|
||
|
||
```c++
|
||
std::string value;
|
||
rocksdb::Status s = db->Get(rocksdb::ReadOptions(), key1, &value);
|
||
if (s.ok()) s = db->Put(rocksdb::WriteOptions(), key2, value);
|
||
if (s.ok()) s = db->Delete(rocksdb::WriteOptions(), key1);
|
||
```
|
||
|
||
## Further documentation
|
||
|
||
These are just simple examples of how RocksDB is used. The full documentation is currently on the [GitHub wiki](https://github.com/facebook/rocksdb/wiki).
|
||
|
||
Here are some specific details about the RocksDB implementation:
|
||
|
||
- [Architecture Guide](https://github.com/facebook/rocksdb/wiki/Rocksdb-Architecture-Guide)
|
||
- [Format of an immutable Table file](https://github.com/facebook/rocksdb/wiki/Rocksdb-Table-Format)
|
||
- [Format of a log file](https://github.com/facebook/rocksdb/wiki/Write-Ahead-Log-File-Format)
|