# MVStore Overview Example Code Store Builder R-Tree Features - Maps - Versions - Transactions - In-Memory Performance and Usage - Pluggable Data Types - BLOB Support - R-Tree and Pluggable Map Implementations - Concurrent Operations and Caching - Log Structured Storage - Off-Heap and Pluggable Storage - File System Abstraction, File Locking and Online Backup - Encrypted Files - Tools - Exception Handling - Storage Engine for H2 Similar Projects and Differences to Other Storage Engines Current State Requirements ## Overview The MVStore is work in progress, and is planned to be the next storage subsystem of H2. But it can be also directly within an application, without using JDBC or SQL. MVStore stands for "multi-version store". Each store contains a number of maps (using the `java.util.Map` interface). Both file-based persistence and in-memory operation are supported. It is intended to be fast, simple to use, and small. Old versions of the data can be read concurrently with all other operations. Transaction are supported (including concurrent transactions and 2-phase commit). The tool is very modular. It supports pluggable data types / serialization, pluggable storage (to a file, to off-heap memory), pluggable map implementations (B-tree, R-tree, concurrent B-tree currently), BLOB storage, and a file system abstraction to support encrypted files and zip files. ## Example Code The following sample code show how to use the tool:
    import org.h2.mvstore.*;

    // open the store (in-memory if fileName is null)
    MVStore s = MVStore.open(fileName);

    // create/get the map named "data"
    MVMap<Integer, String> map = s.openMap("data");

    // add and read some data
    map.put(1, "Hello World");
    System.out.println(map.get(1));

    // mark the changes as committed
    s.commit();

    // close the store (this will store committed changes)
    s.close();
## Store Builder The `MVStore.Builder` provides a fluid interface to build a store if more complex configuration options are used. The following code contains all supported configuration options:
    MVStore s = new MVStore.Builder().
        backgroundExceptionListener(listener).
        cacheSize(10).
        compressData().
        encryptionKey("007".toCharArray()).
        fileName(fileName).
        fileStore(new FileStore()).
        pageSplitSize(6 * 1024).
        readOnly().
        writeBufferSize(8).
        writeDelay(100).
        open();
backgroundExceptionListener: a listener for exceptions that could occur while writing in the background. cacheSize: the cache size in MB. compressData: compress the data when storing. encryptionKey: the encryption key for file encryption. fileName: the name of the file, for file based stores. fileStore: the storage implementation to use. pageSplitSize: the point where pages are split. readOnly: open the file in read-only mode. writeBufferSize: the size of the write buffer in MB. writeDelay: the maximum delay in milliseconds until committed changes are stored in the background. ## R-Tree The `MVRTreeMap` is an R-tree implementation that supports fast spatial queries. It can be used as follows:
    // create an in-memory store
    MVStore s = MVStore.open(null);

    // open an R-tree map
    MVRTreeMap<String> r = s.openMap("data",
            new MVRTreeMap.Builder<String>());

    // add two key-value pairs
    // the first value is the key id (to make the key unique)
    // then the min x, max x, min y, max y
    r.add(new SpatialKey(0, -3f, -2f, 2f, 3f), "left");
    r.add(new SpatialKey(1, 3f, 4f, 4f, 5f), "right");

    // iterate over the intersecting keys
    Iterator<SpatialKey> it =
            r.findIntersectingKeys(new SpatialKey(0, 0f, 9f, 3f, 6f));
    for (SpatialKey k; it.hasNext();) {
        k = it.next();
        System.out.println(k + ": " + r.get(k));
    }
    s.close();
The default number of dimensions is 2. To use a different number of dimensions, call `new MVRTreeMap.Builder<String>().dimensions(3)`. The minimum number of dimensions is 1, the maximum is 255. ## Features ### Maps Each store contains a set of named maps. A map is sorted by key, and supports the common lookup operations, including access to the first and last key, iterate over some or all keys, and so on. Also supported, and very uncommon for maps, is fast index lookup: the entries of the map can be be efficiently accessed like a random-access list (get the entry at the given index), and the index of a key can be calculated efficiently. That also means getting the median of two keys is very fast, and a range of keys can be counted very quickly. The iterator supports fast skipping. This is possible because internally, each map is organized in the form of a counted B+-tree. In database terms, a map can be used like a table, where the key of the map is the primary key of the table, and the value is the row. A map can also represent an index, where the key of the map is the key of the index, and the value of the map is the primary key of the table (for non-unique indexes, the key of the map must also contain the primary key). ### Versions Multiple versions are supported. A version is a snapshot of all the data of all maps at a given point in time. Versions are not immediately persisted; instead, only the version counter is incremented. If there is a change after switching to a new version, a snapshot of the old version is kept in memory, so that it can still be read. Old persisted versions are readable until the old data was explicitly overwritten. Creating a snapshot is fast: only the pages that are changed after a snapshot are copied. This behavior is also called COW (copy on write). Rollback is supported (rollback to any old in-memory version or an old persisted version). The following sample code show how to create a store, open a map, add some data, and access the current and an old version:
    // create/get the map named "data"
    MVMap<Integer, String> map = s.openMap("data");

    // add some data
    map.put(1, "Hello");
    map.put(2, "World");

    // get the current version, for later use
    long oldVersion = s.getCurrentVersion();

    // from now on, the old version is read-only
    s.incrementVersion();

    // more changes, in the new version
    // changes can be rolled back if required
    // changes always go into "head" (the newest version)
    map.put(1, "Hi");
    map.remove(2);

    // access the old data (before incrementVersion)
    MVMap<Integer, String> oldMap =
            map.openVersion(oldVersion);

    // mark the changes as committed
    s.commit();

    // print the old version (can be done
    // concurrently with further modifications)
    // this will print "Hello" and "World":
    System.out.println(oldMap.get(1));
    System.out.println(oldMap.get(2));
    oldMap.close();

    // print the newest version ("Hi")
    System.out.println(map.get(1));
### Transactions To support multiple concurrent open transactions, a transaction utility is included, the `TransactionStore`. The tool supports PostgreSQL style "read committed" transaction isolation with savepoints, two-phase commit, and other features typically available in a database. There is no limit on the size of a transaction (the log is written to disk for large or long running transactions). Internally, this utility stores the old versions of changed entries in a separate map, similar to a transaction log (except that entries of a closed transaction are removed, and the log is usually not stored for short transactions). For common use cases, the storage overhead of this utility is very small compared to the overhead of a regular transaction log. ### In-Memory Performance and Usage Performance of in-memory operations is comparable with `java.util.TreeMap`, but usually slower than `java.util.HashMap`. The memory overhead for large maps is slightly better than for the regular map implementations, but there is a higher overhead per map. For maps with less than about 25 entries, the regular map implementations need less memory. If no file name is specified, the store operates purely in memory. Except for persisting data, all features are supported in this mode (multi-versioning, index lookup, R-tree and so on). If a file name is specified, all operations occur in memory (with the same performance characteristics) until data is persisted. ### Pluggable Data Types Serialization is pluggable. The default serialization currently supports many common data types, and uses Java serialization for other objects. The following classes are currently directly supported: `Boolean, Byte, Short, Character, Integer, Long, Float, Double, BigInteger, BigDecimal, String, UUID, Date` and arrays (both primitive arrays and object arrays). Parameterized data types are supported (for example one could build a string data type that limits the length for some reason). The storage engine itself does not have any length limits, so that keys, values, pages, and chunks can be very big (as big as fits in memory). Also, there is no inherent limit to the number of maps and chunks. Due to using a log structured storage, there is no special case handling for large keys or pages. ### BLOB Support There is a mechanism that stores large binary objects by splitting them into smaller blocks. This allows to store objects that don't fit in memory. Streaming as well as random access reads on such objects are supported. This tool is written on top of the store, using only the map interface. ### R-Tree and Pluggable Map Implementations The map implementation is pluggable. In addition to the default `MVMap` (multi-version map), there is a map that supports concurrent write operations, and a multi-version R-tree map implementation for spatial operations. ### Concurrent Operations and Caching The default map implementation supports concurrent reads on old versions of the data. All such read operations can occur in parallel. Concurrent reads from the page cache, as well as concurrent reads from the file system are supported. Writing changes to the file can occur concurrently to modifying the data, as writing operates on a snapshot. Caching is done on the page level. The page cache is a concurrent LIRS cache, which should be resistant against scan operations. The default map implementation does not support concurrent modification operations on a map (the same as `HashMap` and `TreeMap`). Similar to those classes, the map tries to detect concurrent modification. With the `MVMapConcurrent` implementation, read operations even on the newest version can happen concurrently with all other operations, without risk of corruption. This comes with slightly reduced speed in single threaded mode, the same as with other `ConcurrentHashMap` implementations. Write operations first read the relevant area from disk to memory (this can happen concurrently), and only then modify the data. The in-memory part of write operations is synchronized. For fully scalable concurrent write operations to a map (in-memory and to disk), the map could be split into multiple maps in different stores ('sharding'). The plan is to add such a mechanism later when needed. ### Log Structured Storage Internally, changes are buffered in memory, and once enough changes have accumulated, they are written in one continuous disk write operation. (According to a test, write throughput of a common SSD increases with write block size, until a block size of 2 MB, and then does not further increase.) By default, committed changes are automatically written once every second in a background thread, even if only little data was changed. Changes can also be written explicitly by calling `store()`. To avoid running out of memory, uncommitted changes are also written when needed, however they are rolled back when closing the store, or at the latest (when the store was not closed normally) when opening the store. When storing, all changed pages are serialized, optionally compressed using the LZF algorithm, and written sequentially to a free area of the file. Each such change set is called a chunk. All parent pages of the changed B-trees are stored in this chunk as well, so that each chunk also contains the root of each changed map (which is the entry point for reading this version of the data). There is no separate index: all data is stored as a list of pages. Per store, there is one additional map that contains the metadata (the list of maps, where the root page of each map is stored, and the list of chunks). There are usually two write operations per chunk: one to store the chunk data (the pages), and one to update the file header (so it points to the latest chunk). If the chunk is appended at the end of the file, the file header is only written at the end of the chunk. There is no transaction log, no undo log, and there are no in-place updates (however, unused chunks are overwritten by default). Old data is kept for at least 45 seconds (configurable), so that there are no explicit sync operations required to guarantee data consistency. An application can also sync explicitly when needed. To reuse disk space, the chunks with the lowest amount of live data are compacted (the live data is stored again in the next chunk). To improve data locality and disk space usage, the plan is to automatically defragment and compact data. Compared to traditional storage engines (that use a transaction log, undo log, and main storage area), the log structured storage is simpler, more flexible, and typically needs less disk operations per change, as data is only written once instead of twice or 3 times, and because the B-tree pages are always full (they are stored next to each other) and can be easily compressed. But temporarily, disk space usage might actually be a bit higher than for a regular database, as disk space is not immediately re-used (there are no in-place updates). ### Off-Heap and Pluggable Storage Storage is pluggable. The default storage is to a single file (unless pure in-memory operation is used). An off-heap storage implementation is available. This storage keeps the data in the off-heap memory, meaning outside of the regular garbage collected heap. This allows to use very large in-memory stores without having to increase the JVM heap (which would increase Java garbage collection pauses a lot). Memory is allocated using `ByteBuffer.allocateDirect`. One chunk is allocated at a time (each chunk is usually a few MB large), so that allocation cost is low. ### File System Abstraction, File Locking and Online Backup The file system is pluggable (the same file system abstraction is used as H2 uses). The file can be encrypted using a encrypting file system wrapper. Other file system implementations support reading from a compressed zip or jar file. The file system abstraction closely matches the Java 7 file system API. Each store may only be opened once within a JVM. When opening a store, the file is locked in exclusive mode, so that the file can only be changed from within one process. Files can be opened in read-only mode, in which case a shared lock is used. The persisted data can be backed up at any time, even during write operations (online backup). To do that, automatic disk space reuse needs to be first disabled, so that new data is always appended at the end of the file. Then, the file can be copied (the file handle is available to the application). It is recommended to use the utility class `FileChannelInputStream` to do this. For encrypted databases, both the encrypted (raw) file content, as well as the clear text content, can be backed up. ### Encrypted Files File encryption ensures the data can only be read with the correct password. Data can be encrypted as follows:
    MVStore s = new MVStore.Builder().
        fileName(fileName).
        encryptionKey("007".toCharArray()).
        open();
The following algorithms and settings are used: The password char array is cleared after use, to reduce the risk that the password is stolen even if the attacker has access to the main memory. The password is hashed according to the PBKDF2 standard, using the SHA-256 hash algorithm. The length of the salt is 64 bits, so that an attacker can not use a pre-calculated password hash table (rainbow table). It is generated using a cryptographically secure random number generator. To speed up opening an encrypted stores on Android, the number of PBKDF2 iterations is 10. The higher the value, the better the protection against brute-force password cracking attacks, but the slower is opening a file. The file itself is encrypted using the standardized disk encryption mode XTS-AES. Only little more than one AES-128 round per block is needed. ### Tools There is a tool (`MVStoreTool`) to dump the contents of a file. ### Exception Handling This tool does not throw checked exceptions. Instead, unchecked exceptions are thrown if needed. The error message always contains the version of the tool. The following exceptions can occur: `IllegalStateException` if a map was already closed or an IO exception occurred, for example if the file was locked, is already closed, could not be opened or closed, if reading or writing failed, if the file is corrupt, or if there is an internal error in the tool. For such exceptions, an error code is added to the exception so that the application can distinguish between different error cases. `IllegalArgumentException` if a method was called with an illegal argument. `UnsupportedOperationException` if a method was called that is not supported, for example trying to modify a read-only map or view. `ConcurrentModificationException` if the object is modified concurrently. ### Storage Engine for H2 The plan is to use the MVStore as the default storage engine for the H2 database in the future (supporting SQL, JDBC, transactions, MVCC, and so on). This is work in progress. To try it out, append `;MV_STORE=TRUE` to the database URL. In general, functionality and performance should be similar than the current default storage engine (the page store). There are a few features that have not been implemented yet or are not complete, for example there is still a file named `.h2.db`, and the `.lock.db` file is still used to lock a database (long term, the plan is to no longer use those files). ## Similar Projects and Differences to Other Storage Engines Unlike similar storage engines like LevelDB and Kyoto Cabinet, the MVStore is written in Java and can easily be embedded in a Java and Android application. The MVStore is somewhat similar to the Berkeley DB Java Edition because it is also written in Java, and is also a log structured storage, but the H2 license is more liberal. Like SQLite 3, the MVStore keeps all data in one file. Unlike SQLite 3, the MVStore uses is a log structured storage. The plan is to make the MVStore both easier to use as well as faster than SQLite 3. In a recent (very simple) test, the MVStore was about twice as fast as SQLite 3 on Android. The API of the MVStore is similar to MapDB (previously known as JDBM) from Jan Kotek, and some code is shared between MVStore and MapDB. However, unlike MapDB, the MVStore uses is a log structured storage. The MVStore does not have a record size limit. ## Current State The code is still experimental at this stage. The API as well as the behavior may partially change. Features may be added and removed (even thought the main features will stay). ## Requirements The MVStore is included in the latest H2 jar file. There are no special requirements to use it. The MVStore should run on any JVM as well as on Android. To build just the MVStore (without the database engine), run:
    ./build.sh jarMVStore
This will create the file `bin/h2mvstore-${version}.jar` (about 130 KB).