DBMS > Apache Drill vs. Coveo vs. Hypertable vs. Kinetica vs. SAP HANA

System Properties Comparison Apache Drill vs. Coveo vs. Hypertable vs. Kinetica vs. SAP HANA

Editorial information provided by DB-Engines

Name

Hypertable has stopped its further development with March 2016 and is removed from the DB-Engines ranking.

Description

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

AI-powered hosted search, recommendation and personalization platform providing tools for both low-code and full-code development

An open source BigTable implementation based on distributed file systems such as Hadoop

Fully vectorized database across both GPUs and CPUs

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Document store
Relational DBMS

Search engine

Wide column store

Relational DBMS

Secondary database models

Spatial DBMS
Time Series DBMS

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	2.02
Rank	#124	Overall
	#22	Document stores
	#59	Relational DBMS

Score	2.11
Rank	#118	Overall
	#11	Search engines

Score	0.66
Rank	#234	Overall
	#107	Relational DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Website

drill.apache.org

www.coveo.com

www.kinetica.com

www.sap.com/products/hana.html

Technical documentation

drill.apache.org/docs

docs.coveo.com

docs.kinetica.com

help.sap.com/hana

Developer

Apache Software Foundation

Coveo

Hypertable Inc.

Kinetica

SAP

Initial release

2012

2009

2012

2010

Current release

1.20.3, January 2023

0.9.8.11, March 2016

7.1, August 2021

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

Open Source

GNU version 3. Commercial license available

commercial

Cloud-based only

Only available as a cloud service

yes

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

C, C++

Server operating systems

Linux
OS X
Windows

hosted

Linux
OS X
Windows

an inofficial Windows port is available

Linux

Appliance or cloud-service

Data scheme

schema-free

hybrid - fields need to be configured prior to indexing, but relationships can be exploited at query time without pre-configuration

schema-free

yes

Typing

predefined data types such as float or date

yes

XML support

Some form of processing data in XML format, e.g. support for XML data structures, and/or support for XPath, XQuery or XSLT.

Secondary indexes

yes

restricted

only exact value or prefix value scans

yes

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

SQL-like DML and DDL statements

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

RESTful HTTP API

C++ API
Thrift

JDBC
ODBC
RESTful HTTP API

JDBC
ODBC

Supported programming languages

C++

C#
Java
JavaScript
Python

C++
Java
Perl
PHP
Python
Ruby

C++
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

SQLScript, R

Triggers

yes

triggers when inserted values for one or more columns fall within a specified range

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor on file system level

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

Depending on the underlying data source

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

Depending on the underlying data source

yes

GPU vRAM or System RAM

yes

User concepts

Access control

Depending on the underlying data source

granular access controls, API key management, content filters

Access rights for users and roles on table level

yes

More information provided by the system vendor

We invite representatives of system vendors to contact us for updating and extending the system information,
and for displaying vendor-provided information such as key customers, competitive advantages and market metrics.