History[07][04][08][09][10]

Hypertable was released by the company Zvents at 2008, and Doug Judd promoted to the Hypertable. Baidu, the search engine in China, became project sponsor in January 2009. The development ended in March 2016.

Checkpoints[11][12]

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

Compression[13][14][15]

Over time, the RangeServers will write in-memory CellCaches to on-disk files, called CellStores. CellStores contain a series of sorted blocks of compressed sorted key/value pairs. These blocks are the minimum unit of data transfer from disk. User can choose the compressor used to compress CellStore blocks in each access group. The compressor option includes zlib, lzo, quicklz, snappy, bmz, none. The default compressor is quicklz.

Concurrency Control[16]

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

Data Model[05]

Hypertable uses a set of related columns.

Foreign Keys

Isolation Levels[14]

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

Joins[05]

Query Interface[17]

The Hypertable Query Language (HQL) allows you to create, modify, and query tables and invoke administrative commands. HQL is interpreted by the following interfaces: - The hypertable command line interface (ht shell), - The hql_exec and hql_query Thrift API methods, - The Hypertable::HqlInterpreter C++ class.

Storage Architecture[14]

Hypertable is capable of running on top of any filesystem. To achieve this, the system has abstracted the interface to the filesystem by sending all filesystem requests through a File System (FS) broker process. FS brokers have been developed for HDFS, MapR, Ceph, KFS, and local (for running on top of a local filesystem).

Storage Model

Storage Organization[14]

Stored Procedures

System Architecture[14]

The diagram below provides a high-level overview of the Hypertable system followed by a brief description of each system component.

Hyperspace - This is Hypertable's equivalent to Google's Chubby service. Hyperspace is a lock manager and provides a filesystem for storing small amounts of metadata.

Master - The master handles all meta operations such as creating and deleting tables. The master is also responsible for detecting range server failures and re-assigning ranges if necessary.

Range Server - Range servers are responsible for managing ranges of table data, handling all reading and writing of data.

FS Broker - Hypertable is capable of running on top of any filesystem. To achieve this, the system has abstracted the interface to the filesystem by sending all filesystem requests through a File System (FS) broker process. The FS broker provides a normalized filesystem interface and translates normalized filesystem requests into native filesystem requests and vice-versa. FS brokers have been developed for HDFS, MapR, Ceph, KFS, and local (for running on top of a local filesystem).

ThriftBroker - Provides an interface for applications written in any high-level language to communicate with Hypertable. The ThriftBroker is implemented with Apache Thrift and provides bindings for applications written in Java, PHP, Ruby, Python, Perl, and C++.