System Architecture

Shared-Disk

The architecture of the Hypertable is shown below.

Hyperspace - Hyperspace is a lock manager. It contains a filesystem to store some metadata. Equivalent to Google's Chubby service.

Master - The Master handles all the meta operations. It also detects range server failures. It can re-assign ranges if necessary.

Range Server - Range servers handle the reading and writing of data.

FS Broker - File System (FS) broker process all filesystem requests. FS brokers currently support HDFS, MapR, Ceph, KFS, and local.

ThriftBroker - ThriftBroker provides the application interface. It is implemented with Apache Thrift. It currently supports Java, PHP, Ruby, Python, Perl, and C++.

Joins

Not Supported

Hypertable does not support Joins.

Views

Not Supported

Storage Architecture

Disk-oriented

Hypertable is able to run on top of any filesystem. A File System (FS) broker process all filesystem requests. FS brokers currently support HDFS, MapR, Ceph, KFS, and local.

Storage Organization

Sorted Files

Query Interface

Custom API Command-line / Shell

Hypertable provides the Hypertable Query Language (HQL) to create, modify, and query tables. HQL can also be used to invoke administrative commands. HQL can be interpreted by hypertable command line interface (ht shell), Thrift API methods, and Hypertable::HqlInterpreter C++ class.

Storage Model

Custom

Stored Procedures

Not Supported

Concurrency Control

Multi-version Concurrency Control (MVCC)

Hypertable uses Multi-Version Concurrency Control (MVCC). It uses auto-assign timestamps as revision numbers.

Data Model

Column Family / Wide-Column

Hypertable uses a set of related columns.

Checkpoints

Consistent

Hypertable backup by outputting table data in random order. Hypertable will always be back into a consistent and operational state at the checkpoint.

Isolation Levels

Snapshot Isolation

Hypertable provides snapshot isolation for queries with 8-byte timestamps.

Foreign Keys

Not Supported