DBMS > Apache Impala vs. Google BigQuery vs. Splunk vs. Ultipa

System Properties Comparison Apache Impala vs. Google BigQuery vs. Splunk vs. Ultipa

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

Large scale data warehouse service with append-only tables

Analytics Platform for Big Data

High performance Graph DBMS supporting HTAP high availability cluster deployment

Primary database model

Relational DBMS

Search engine

Graph DBMS

Secondary database models

Document store

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

Score	10.63
Rank	#40	Overall
	#24	Relational DBMS

Score	52.67
Rank	#19	Overall
	#13	Relational DBMS

Score	93.02
Rank	#13	Overall
	#2	Search engines

Score	0.11
Rank	#338	Overall
	#32	Graph DBMS

Website

impala.apache.org

cloud.google.com/bigquery

www.splunk.com

www.ultipa.com

Technical documentation

impala.apache.org/impala-docs.html

cloud.google.com/bigquery/docs

docs.splunk.com/Documentation/Splunk

www.ultipa.com/document

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Google

Splunk Inc.

Ultipa

Initial release

2013

2010

2003

2019

Current release

4.1.0, June 2022

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

Limited free edition and free developer edition available

commercial

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

C++

Server operating systems

Linux

hosted

Linux
OS X
Solaris
Windows

Data scheme

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.

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like DML and DDL statements

yes

Splunk Search Processing Language for search commands

APIs and other access methods

JDBC
ODBC

RESTful HTTP/JSON API

HTTP REST

RESTful HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C#
Java
JavaScript
PHP
Python
Ruby

C++
Go
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

user defined functions

in JavaScript

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

Transaction concepts

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

Since BigQuery is designed for querying data

A 'Transaction' in Splunk has a different meaning: grouping related events into a single one for later searching

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

In-memory capabilities

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

User concepts

Access control

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

Access rights for users and roles

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.