Arenadata QuickMarts
Arenadata QuickMarts (ADQM) is a cluster column-oriented DBMS built on ClickHouse. ADQM generates various online analytical reports based on vast amounts of information stored in flat marts. ADQM is much faster than traditional DBMS.
TOP-10 popular articles
This article describes the parameters that can be configured for ADQM services via ADCM.
A dictionary is a key/value data store that is fully or partially stored in the RAM of the ADQM server and can be used as a reference to substitute data values by keys in the final sample.
Learn about the minimum software requirements for servers of an ADQM cluster.
Sharding is a database design principle that suggests locating parts of the same table on different shards. A shard is a cluster node that can consist of one or more replicas. Replicas are servers that duplicate data within a shard. SELECT and INSERT queries can be sent to any replica of a shard, there is no dedicated master.
To connect to ADQM, you can use clickhouse-client — a standard ClickHouse command-line client that allows you to run SQL queries and view their results in your terminal application. Once ADQM is installed, clickhouse-client is available on each server of the ADQM cluster.
This article provides examples that demonstrate how to perform the basic operations with ADQM/ClickHouse tables using the clickhouse-client console client.
Learn about the minimum hardware requirements for servers of an ADQM cluster.
A geo-distributed cluster is a cluster whose nodes are located in several geographically distant data centers. This solution ensures high reliability of the system, which will remain operational even if one of the data centers fails.
Indexing is a technique to improve database performance. Indexes are special data structures that allow a database server to quickly find requested rows by values of a key column (or column set) without a full table scan.
ADQM writes general and error text logs that can be useful for analyzing the causes of different errors. Additionally, you can enable logs of other types (for example, collect information about query execution, dependent views, threads, stack traces) that will be saved to special system tables in ADQM.