Release notes of LindormTable - Lindorm - Alibaba Cloud Documentation Center

Lindorm releases new LindormTable versions to provide new features, fix known bugs, and improve user experience. This topic describes the release notes of LindormTable versions. This topic also provides usage notes on how to upgrade the LindormTable version of your Lindorm instance during off-peak hours.

View or upgrade the LindormTable version of a Lindorm instance

You can view the LindormTable version of an instance in the Lindorm console. For more information about how to upgrade LindormTable versions and precautions, see Upgrade the minor engine version of a Lindorm instance. 查看版本

Warning

When you upgrade the LindormTable version of an instance, the instance is restarted and may be temporarily disconnected. We recommend that you upgrade the LindormTable version during off-peak hours.
Lindorm checks the LindormTable version of each instance. If the Minor Version Upgrade button does not appear on the overview page of an instance, the latest LindormTable version is used in the instance.
Version updates may differ from region to region. The LindormTable version displayed in the Lindorm console prevails.

2.7

2.7.1

Release date

Category

Description

2024-07-11

New features

Expressions that include the MD5 or SHA256 function can be specified as secondary index keys. For more information, see Secondary index function expression (function_expression).
You can execute SQL statements to configure the maximum number of connections to LindormTable. For more information, see Supported configuration items.
Lindorm GanosBase supports S2 secondary indexes. For more information, see S2 secondary indexes.
S2 indexes can be used to query whether geometry objects intersect.

Optimized features

The performance of LindormTable when you query a single data record is improved.
Indexes can be created for the historical data in multiple index tables of a table at the same time.
The progress information of a secondary index when the index is built for historical data is enriched.
The stability of LindormTable and its compatibility with MySQL is improved. More MySQL syntaxes are supported by LindormTable.

2.6

2.6.5

Release date

Category

Description

2024-03-25

New features

The following two parameters can be configured for search indexes: INDEX_SETTINGS that specifies index attributes and mapping that specifies index key attributes. For more information, see Index key definition (index_key_definition) and Search index.
Lindorm GanosBase supports S2 secondary indexes. For more information, see S2 secondary indexes.
Lindorm GanosBase supports H3 functions that can be used to efficiently analyze or query spatio-temporal data based on H3 grids. For more information, see H3 functions.

Optimized features

The compatibility with MySQL syntax is improved and more MySQL syntaxes are supported.
The reuse of physical plans is supported by Lindorm SQL to improve query performance.
You can build secondary indexes for historical data even if the data is stored by using cold storage.
Issues related to the compatibility of Apache HBase clients with Lindorm are fixed. If you want to use an open source Apache HBase client to access Lindorm, we recommend that you upgrade the LindormTable version to 2.6.5 or later.

2.6.2

Release date	Category	Description
2023-11-08	New features	The MySQL compatibility feature is supported. For more information, see Use the MySQL protocol to develop applications (recommended).

2.5

2.5.6

Release date	Category	Description
2023-08-18	Optimized features	The compatibility issue with the HBase protocol is fixed. The following issue is fixed: Loads among multiple groups are not balanced. The stability of LindormTable is improved.

2.5.3

Release date

Category

Description

2023-05-24

New features

Wildcard columns are supported. For more information, see Wildcard columns.

Optimized features

The following issue is fixed: A short-circuit read or write that is performed by using a SQL statement may time out.
Note
For better read and write experience, we recommend that you update the engine version of your LindormTable to 2.5.3 or later.
The compatibility issue that may occur when you use an Apache HBase client to perform operations on ApsaraDB for HBase by using a batch interface is fixed.
The following issue is fixed: A large number of meta requests occur when you use an Apache HBase client.

2.5.2

Release date	Category	Description
2023-04-19	New features	Existing columns can be deleted from a table by using Lindorm SQL. For more information, see ALTER TABLE.
2023-04-19	Optimized features	The user experience of using SQL statements to access an HBase table is improved. For more information, see Use SQL statements to access an HBase table. The user experience of querying hot data and cold data that are separately stored is improved. Asynchronous audit logs are supported. The compatibility with Apache HBase clients is improved. The number of files that are monitored in a region is increased. The execution efficiency of the AGGREGATE statement is optimized. The CPU consumption caused by the expiration of data with a short time to live (TTL) is reduced.

2.4

2.4.3

Release date	Category	Description
2023-03-10	Optimized features	The user experience of Lindorm SQL is optimized. The stability of LindormTable is improved.

2.4.2

Release date	Category	Description
2022-12-13	New features	Open source Apache HBase clients can be used to access LindormTable. Hot and cold data separation can be performed based on custom time columns. If you use Lindorm SQL, we recommend that you use this feature. For more information, see Separately store hot data and cold data based on custom time columns.
2022-12-13	Optimized features	The user experience of JSON is optimized. The stability of LindormTable is improved.

2.4.1

Release date	Category	Description
2022-11-01	Optimized features	The user experience of Lindorm GanosBase is optimized. The bugs that are related to Lindorm SQL are fixed.

2.4.0

Release date	Category	Description
2022-10-09	New features	SQL statements can be used to access HBase tables. For more information, see Use SQL statements to access an HBase table.
2022-10-09	Optimized features	The user experience of Lindorm SQL is optimized.

2.3

2.3.4

Release date	Category	Description
2022-08-30	Optimized features	The user experience of Lindorm SQL is optimized.

2.3.3

Release date	Category	Description
2022-08-16	Optimized features	Hot data can be automatically identified and processed. The ST_DWithin and ST_DWithinSphere functions are supported by Lindorm GanosBase. The stability of LindormTable is improved.

2.3.2

Release date	Category	Description
2022-08-02	Optimized features	The syntax of Lindorm SQL statements is optimized. More features of Lindorm GanosBase are supported. For more information, see Overview.

2.3.1

Release date	Category	Description
2022-06-30	New features	Lindorm GanosBase is supported. For more information, see Overview.

2.2

Version number	Release date	Category	Description
2.2.21	2022-04-25	Optimized features	Direct memory consumption is reduced when data is written. The load balancing policy is optimized. The parameters of the compaction process are optimized and the values of the parameters can be automatically adjusted. The speed at which indexes are created is improved. The read and write performance of SQL statements is optimized.
2.2.20	2022-03-16	Optimized features	The write performance of large-size key values is optimized. Lindorm SQL can be used to read multiple versions of data and write data based on custom timestamps. Other performance issues are fixed.
2.2.19	2022-02-09	New features	Dynamic columns and SQL monitoring are supported for Lindorm SQL.
2.2.19	2022-02-09	Optimized features	The following bug is fixed: The metadata update is delayed after the attributes of Lindorm SQL tables are modified. Stability bugs are fixed.
2.2.18	2022-01-05	Optimized features	The performance of Lindorm SQL statements is optimized. The issues related to the time zones of the DATE or TIME type in Lindorm SQL statements are fixed. Stability bugs are fixed.
2.2.17	2021-12-17	Optimized features	The bugs that occur for Lindorm SQL statements are fixed. The speed at which the cold storage feature is released in regions is improved. If you use cold storage, we recommend that you upgrade the LindormTable version to a version that is later than V2.2.17.
2.2.16	2021-11-12	Optimized features	The syntax of Lindorm SQL is improved. If you use SQL statements, we recommend that you upgrade the LindormTable version to a version that is later than V2.2.16. For more information, see Lindorm SQL. The logic that is used to flush data to a disk is optimized. This prevents out-of-memory bugs when an excessive number of regions exist. Other bugs are fixed.
2.2.15	2021-10-18	Optimized features	Lindorm SQL is optimized to fix the following bugs: Tables fail to be created and data that require strong consistency fails to be read from tables. For more information, see Lindorm SQL. We recommend that you upgrade your LindormTable to this version or a later version.
2.2.12	2021-09-06	Optimized features	Compaction policies are optimized to improve efficiency. The amount of data that is returned for scan operations is optimized.
2.2.11	2021-08-25	New features	Lindorm SQL statements are supported. For more information, see Lindorm SQL. Secondary indexes are supported. For more information, see Secondary index.
2.2.10	2021-08-12	Optimized features	The issue that request errors occur due to network jitters for cold data is fixed.
2.2.9	2021-06-09	New features	A feature that allows you to dynamically generate the configurations of analyzers is added to SearchIndex, and some bugs are fixed.
2.2.8	2021-03-25	Optimized features	The memory usage issue that occurs while data is being compressed by using zstd is optimized.
2.2.7	2021-03-11	New features	A feature that allows you to export data from Lindorm in sequence is added. This feature must be used together with Lindorm Tunnel Service (LTS).
2.2.5	2021-01-07	New features	A feature that allows you to export incremental data of Lindorm is added. The feature must be used together with LTS.
2.2.1	2020-09-09	Optimized features	The SearchIndex feature is optimized and some bugs are fixed.

2.1

Version number	Release date	Category	Description
2.1.30	2020-10-26	Optimized features	The algorithm that is used to select flush regions when write hotspots occur is optimized.
2.1.26	2020-10-09	Optimized features	The memory overhead of BucketCache is optimized for clusters that use lower specifications.
2.1.25	2020-09-30	Optimized features	The volume of redundant data that is retrieved for reverse scans is decreased.
2.1.23	2020-09-22	Optimized features	Memory management is optimized for servers that use low memory specifications.
2.1.21	2020-07-20	Optimized features	We recommend that you upgrade your LindormTable to this version or a later version. The write throughput is optimized. The performance of reverse scans is optimized. The rate at which hot data is archived into cold storage is optimized.
2.1.17	2020-03-20	Optimized features	The SearchIndex feature is optimized.
2.1.15	2020-02-06	Optimized features	The SearchIndex feature is optimized and some bugs are fixed.
2.1.12	2019-12-16	Optimized features	The SearchIndex feature is optimized and the bugs that occur during bulk loading are fixed.
2.1.10	2019-11-16	New features	The SearchIndex feature is supported.
2.1.10	2019-11-16	Optimized features	The hot and cold data separation feature is optimized.
2.1.9	2019-10-08	New features	The SearchIndex feature is supported and some bugs are fixed. For more information about the feature, see SearchIndex.
2.1.8	2019-09-09	New features	The cold storage and hot and cold data separation features are supported. For more information, see Cold storage and Cold and hot data separation.