What's New in MariaDB Enterprise ColumnStore 5?
This page is part of MariaDB's Documentation.
The parent of this page is: What's new in older releases?
Topics on this page:
Overview
MariaDB Enterprise ColumnStore 5 is included with MariaDB Enterprise Server 10.5.
The new features in MariaDB Enterprise ColumnStore 5 are listed below.
MariaDB Enterprise Server Convergence
MariaDB has been continually improving the integration of MariaDB Enterprise ColumnStore with MariaDB Enterprise Server:
In MariaDB ColumnStore 1.2 and earlier, MariaDB ColumnStore required special custom-built releases of MariaDB Server.
MariaDB Enterprise ColumnStore 1.4 was included with the standard MariaDB Enterprise Server 10.4 releases. It was the first release to integrate with a standard ES release using the ColumnStore storage engine plugin.
MariaDB Enterprise ColumnStore 1.5 was included with the standard MariaDB Enterprise Server 10.5 releases up to ES 10.5.5-3. It was the first release to replace the Operations/Administration/Maintenance (OAM) API with the more modern Cluster Management API (CMAPI), which is still in use.
Starting with ES 10.5.6-4, MariaDB Enterprise ColumnStore 5 is included with the standard MariaDB Enterprise Server 10.5 releases.
MariaDB Enterprise ColumnStore 5 simplifies the installation procedure. Installing the ColumnStore storage engine is similar to installing other storage engines for MariaDB Enterprise Server.
Available Versions
The version of MariaDB Enterprise ColumnStore 5 depends on the version of MariaDB Enterprise Server being used:
ES Version | Enterprise ColumnStore Version |
---|---|
Installation
MariaDB Enterprise ColumnStore 5 simplifies the installation procedure. Installing the ColumnStore storage engine is similar to installing other storage engines for MariaDB Enterprise Server.
For single-node and multi-node Enterprise ColumnStore 5 deployments, the ColumnStore storage engine, the ColumnStore command-line interfaces, and other internal ColumnStore components are deployed by installing a single package in addition to the MariaDB Enterprise Server package.
For multi-node Enterprise ColumnStore 5 deployments, the Cluster Management API (CMAPI) server must be deployed by installing another package.
Installing Enterprise ColumnStore 5 no longer requires running columnstore-post-install
or postConfigure.
Enterprise ColumnStore 5 can be installed to run as a non-root user.
Note
To install this version, see "Deploy".
Clients
MariaDB Enterprise ColumnStore 5 adds support for Microsoft Power BI Direct Query Adapter.
Administration
MariaDB Enterprise ColumnStore 5 simplifies administration.
Enterprise ColumnStore 5 no longer includes or supports mcsadmin.
For single-node and multi-node Enterprise ColumnStore 5 deployments, the Enterprise ColumnStore 5 service is administered by systemd:
Operation | Command |
Start |
|
Stop |
|
Restart |
|
Enable during startup |
|
Disable during startup |
|
Status |
|
For multi-node Enterprise ColumnStore 5 deployments, systemd is not used to stop and start the Enterprise ColumnStore 5 services. Cluster Management API (CMAPI) server runs on every node and ensures that the Enterprise ColumnStore 5 services are running. CMAPI server provides a REST API that can be used to perform administrative operations:
Endpoint Path | Method | Action |
---|---|---|
| Adds a ColumnStore node | |
| Sets all ColumnStore nodes to read-only or read-write | |
| Removes a ColumnStore node | |
| Shuts down ColumnStore on all nodes | |
| Starts ColumnStore on all nodes | |
| Checks the status of ColumnStore |
The Cluster Management API (CMAPI) service is administered by systemd:
Operation | Command |
Start |
|
Stop |
|
Restart |
|
Enable during startup |
|
Disable during startup |
|
Status |
|
Multi-Node
MariaDB Enterprise ColumnStore 5 supports multi-node deployments for high availability and load balancing. Multi-node Enterprise ColumnStore 5 requires an odd number of ColumnStore nodes with a minimum of 3.
Multi-node Enterprise ColumnStore 5 requires MariaDB MaxScale 2.5 for high availability and load balancing. Multi-node Enterprise ColumnStore requires at least one MaxScale node. For highly available load balancing, multiple MaxScale nodes can be used by configuring cooperative locking.
Multi-node Enterprise ColumnStore 5 requires CMAPI server to be running on every ColumnStore node. CMAPI server provides a REST API that can be used to perform administrative operations
S3-Compatible Object Storage
MariaDB Enterprise ColumnStore supports S3-compatible object storage.
S3-compatible object storage is optional, but highly recommended. If S3-compatible object storage is used, Enterprise ColumnStore requires the Storage Manager directory to use shared local storage (such as NFS) for high availability.
S3-compatible object storage is:
Compatible: Many object storage services are compatible with the Amazon S3 API.
Economical: S3-compatible object storage is often very low cost.
Flexible: S3-compatible object storage is available for both cloud and on-premises deployments.
Limitless: S3-compatible object storage is often virtually limitless.
Resilient: S3-compatible object storage is often low maintenance and highly available, since many services use resilient cloud infrastructure.
Scalable: S3-compatible object storage is often highly optimized for read and write scaling.
Secure: S3-compatible object storage is often encrypted-at-rest.
Many S3-compatible object storage services exist. MariaDB Corporation cannot make guarantees about all S3-compatible object storage services, because different services provide different functionality.
If you have any questions about using specific S3-compatible object storage with MariaDB Enterprise ColumnStore, contact us.
Enterprise ColumnStore 5 supports IAM roles with S3-compatible object storage.
Supersedes 1.5
MariaDB Enterprise ColumnStore 5 supersedes MariaDB Enterprise ColumnStore 1.5 and includes the changes in MariaDB Enterprise ColumnStore 1.5.3.