GridGain 9.1.0 Release Notes

GridGain 9.1.0 introduces secondary columnar storage, a new JSON license format, reworked node and cluster configuration, and numerous SQL and client improvements.

Overview

GridGain 9.1.0 is a big milestone release with support for new storage type, big license changes and a host of improvements and enhancements.

Major Changes

Configuration Changes

This release features a major rework of node and cluster configuration, making configuration names more consistent and reorganizing some parameters.

Below is the summary of the changes:

Configuration property names now include the units used.
Multiple system-related properties were combined in ignite.system configuration.
Eviction and expiration configurations are now combined under ignite.table configuration.
Several configuration options were renamed.

Previously used configurations must be updated for this release.

License Changes

With this release, GridGain 9 license format is changed. Previously issued license keys will continue to work.

New licenses are provided in JSON format, simplifying their usage in REST requests and CLI.

New Features

Secondary Columnar Storage

This release brings support for secondary columnar storage. The columnar package is included in the release package.

If columnar storage is enabled, you can use it to store the second instance of data in it, providing a way to search data in columnar format.

To set up columnar storage for your tables:

Create a new storage profile with columnar storage engine:

node config update "ignite.storage.profiles:{columnar_storage{engine:columnar}}"

Restart the node to apply configuration changes.
Then, include this profile in a distribution zone you use. Distribution zone can also include the storage profile to that will be used to write data:
```
CREATE ZONE myZone WITH STORAGE_PROFILES='default, columnar_storage';
```

Create a new table that has a SECONDARY STORAGE PROFILE specified and uses columnar storage for it:

CREATE TABLE Person (  id int primary key,  city_id int,  name varchar,  age int,  company varchar) PRIMARY ZONE MYZONE PRIMARY STORAGE PROFILE 'default' SECONDARY ZONE MYZONE SECONDARY STORAGE PROFILE 'columnar_storage';

In this release, you can only specify secondary storage for new tables. You can also specify separate distribution zones for primary and columnar storage.

When data is written to the primary storage, it will automatically be propagated to secondary storage. To read data from columnar storage, use the use_secondary_storage query hint:

SELECT /*+ use_secondary_storage */ * FROM Person;

For more information on columnar storage, see Columnar Storage documentation.

Streamer Support in Kafka Sink

Kafka Sink now supports receiving data via data streamer.

To enable data streamer support, specify the name of the receiver class in the ignite.streamer.receiver.class.name kafka sink configuration property. You can specify the deployment units containing the class in the ignite.streamer.receiver.deployment.units property.

Expanded COPY INTO Syntax

The COPY INTO command syntax is expanded with new optional parameters that help support importing data from CSV files with various syntax rules. The following parameters were added:

quoteChar - defines the quote character;
escapeChar - defines the character to use for escaping a separator or quote;
ignoreLeadingWhiteSpace - defines if leading whitespace are ignored;
ignoreQuotations - defines if quoted elements are ignored;
strictQuotes - defines if characters outside the quoted elements are ignored.

These parameters can be specified in the WITH clause, for example:

COPY FROM '/path/to/dir/data.csv'
INTO Table1 (name, age)
FORMAT CSV
WITH 'quoteChar'='~'

Expanded Continuous Queries

Continuous query API was expanded with new properties:

The TableRowEventBatch#watermark property can be used to create a watermark that can be used to continue the continuous query from the specific batch of data in case of interrupted connection or other issues.
The ContinuousQueryOptions#enableEmptyBatches, if set to true, allows empty batches in continuous queries. These batches will be sent only when there is no load, and can be used to update the watermark.

Improvements and Fixed Issues

Issue ID

Known Limitations

Data Restoration After Data Rebalance

Currently, data rebalance may cause partition distribution to change and cause issues with snapshots and data recovery. In particular:

It is currently not possible to restore a LOCAL snapshot if data rebalance happened after snapshot creation. This will be addressed in one of the upcoming releases.
It is currently not possible to perform point-in-time recovery if data rebalance happened after table creation. This will be addressed in one of the upcoming releases.

Data Center Replication With Complex Topologies

Complex Data Center Replication topologies (for example, the ones involving cycles) of 3 or more data centers are not supported. This will be addressed in an upcoming releases.

SQL Performance in Complex Scenarios

There are known issues with the performance of SQL read-write transactions in complex read-write scenarios. These issues will be addressed in an upcoming releases.

We Value Your Feedback

Your comments and suggestions are always welcome. You can reach us here: http://support.gridgain.com/.

Last updated 8 days ago

Was this helpful?