Glossary
- ADB
-
Arenadata DB is a distributed analytical data storage built on the open-source massively parallel system Greengage DB.
- ADBM
-
Arenadata DB Backup Manager (ADBM) is a fault-tolerant system for ADB binary backups management built on the base of pgBackRest.
- ADB Control
-
Arenadata DB Control (ADB Control) is a real-time Arenadata DB query monitoring system.
- Append-optimized table
-
A type of table where data is optimized for bulk loading. They are suitable for OLAP (online analytical processing) workloads.
- Backup configuration
-
A set of options in Arenadata DB Backup Manager (ADBM) that defines how to manage binary database backups: where to store them, what compression type to use, and so on.
- Backup manager
-
a component that lets you manage backup configuration in the ADB Control UI.
- Bundle
-
A delivery unit in ADCM designed to facilitate product installation and deployment. It’s an archive containing software packages, configuration file templates, and Ansible tasks that define operations to be performed on the taget system.
- Connector
-
Connector is a component that facilitates data exchange between ADB and external data sources. For example, ADB ClickHouse Connector, ADB to Kafka Connector, and Kafka to ADB Connector.
- Cluster
-
A system of interconnected nodes comprising a coordinator node and multiple segment nodes, all based on PostgreSQL database instances, that process data in parallel.
- Data flow
-
In ADBM, a data flow is the process of moving backup data between the source and the target cluster to implement Disaster Recovery. In ADB Control, you can create a data flow configuration to define the backup and restore parameters, such as the restore type (
CopyorStreaming) and restore points. - Differential backup
-
A type of backup, which contains only those database files that have changed since the last full backup was launched.
- Distribution
-
Distribution is the mechanism for spreading table rows across multiple segments in a parallel processing architecture. Every table in ADB has a distribution policy.
- Enterprise Tools
-
Arenadata Enterprise Tools or ET is a solution that provides the necessary infrastructure for Arenadata product deployment in environments with limited internet access.
- External table
-
External table is a table definition that points to data stored outside ADB, allowing you to query external files as if they were regular database tables. External tables use protocol for connecting to a data source. Internal protocols include FILE, GPFDIST, and HTTP.
- FDW
-
Foreign data wrappers are libraries that are used by foreign table to communicate with a remote data source.
- Foreign table
-
Table definition that allows you to access data residing outside the database. Foreign tabes use foreign servers to represent remote databases and foreign data wrappers (FDW) to communicate with a remote data source.
- Full backup
-
A type of database where the entire database content is backed up.
- GUC
-
Global User Configuration is a set of server configuration parameters that allow ADB administrators to manage the DBMS state and configuration.
- Heap table
-
A type of table where data is stored in an unsorted collection. They are suitable for OLTP (online transaction processing) workloads.
- Incremental backup
-
A type of backup, which contains only those database files that have changed since the last backup of any other type was launched (full, differential, or incremental).
- Interconnect
-
The network that facilitates data movement between the coordinator and segments.
- Coordinator
-
The node that acts as the entry point to the database and coordinates segment workloads. It is used by end users to submit queries. Formerly known as master.
- Mirror segment
-
A mirror segment is a node that provides high availability support for primary segments. If a primary segment becomes unavailable, the system automatically fails over to the mirror copy.
- Partitioning
-
Partitioning is a technique to split a table into smaller, more manageable parts called partitions in order to increase query performance.
- Primary segment
-
A primary segment is an active node that stores data, receives query plans, and executes queries.
- PXF
-
Greenplum Platform Extension Framework (PXF) is a library that allows ADB to query external data sources. PXF includes built-in connectors (such as those allowing you to access HDFS, Hive, and HBase), and users can also create their own connectors. In ADB, PXF is represented as a service that you can manage using the ADCM web interface.
- Restore point
-
In ADBM, a restore point is a named recovery point, which is the minimum unit of data consistency granularity in ADB clusters.
- Segment
-
A segment is an instance of the PostgreSQL database that stores and processes its set of data.
- Service
-
A cluster component that provides specific functionality. Using the Mapping mechanism, you can define on which hosts particular services should be installed.
- Standby coordinator
-
A component that serves as a warm backup for the primary coordinator instance. It uses write-ahead logging (WAL) to stay synchronized with the primary coordinator.
- Tablespace
-
A logical name for a physical directory on the filesystem where a database can store its data files (such as tables and indexes). This lets you optimize performance by placing frequently accessed data on high-speed storage while storing historical or less critical data on lower-tier storage.
- Timeline
-
A mechanism that is used in ADBM to distinguish the WAL series generated after the database recovery at the specified restore point from those created in the original database history (before the restore action application).
- Transaction
-
A logical unit that groups one or more SQL statements. These statements are then treated as a single operation — either all of them or none of them succeed. You can monitor transactions on the Monitoring page of ADB Control.
- User mapping
-
A configuration that links a local database user to a user on an external database to provide access to that database. User mapping is required for using Foreign Data Wrappers (FDW).
- WAL
-
Write-Ahead Logging is a technique that ensures data integrity by forcing all database modifications to be written to a persistent, append-only log before the corresponding data pages are updated on disk. WAL plays a central role in Point-in-Time Recovery (PITR) that is used in ADBM.