News - 14 series#

Release 14.08 - 2024-09-25#

Improvements#

We use CMake for building instead of the GNU Autotools.

Using configure is deprecated. We recommend using cmake to build from source.

Please refer [Others] about how to build from source with cmake.

Fixes#

Fixed a bug that SELECT returned wrong result when we used multiple primary keys and primary keys included VARBINARY or BLOB type column. [GH-783][Reported by Jérome Perrin]

If this bug occurred, the following query retrieved nothing.
```
CREATE TABLE logs (
  id INT,
  content VARBINARY(256),
  PRIMARY KEY (id, content)
) ENGINE=Mroonga DEFAULT CHARSET=utf8mb4;

INSERT INTO logs(id, content) VALUES (1, 'aaa');
INSERT INTO logs(id, content) VALUES (2, 'bbb');

SELECT * FROM logs WHERE content = 'aaa';
```
This bug only occurred in Mroonga 14.07.

This bug doesn’t break an index. So, we don’t need to execute REINDEX command after this fix.

Thanks#

Jérome Perrin

Release 14.07 - 2024-09-06#

Improvements#

[AlmaLinux][Debian GNU/Linux][Ubuntu] Added support for MySQL community 8.4.2.
[AlmaLinux][Debian GNU/Linux][Ubuntu] Added support for MySQL community 8.0.39.
[AlmaLinux] Added support for Percona Server 8.0.37-29.
[Ubuntu] Added support for MySQL 8.0.39
[AlmaLinux] Added support for MariaDB 11.4.3, 10.11.9, 10.6.19, and 10.5.26.
[Ubuntu] Added support for MariaDB 10.6.18 and 10.11.8.
Disable descending index support [GitHub #764][Reported by Josep Sanz]

If we don’t add support for descending index with MariaDB >= 10.8, Mroonga returns wrong result with descending index. So, we disable descending index support now. However, we may re-try it later.

By the way, if we use descending index with MySQL >= 8.0, MySQL returns error.

Fixes#

Fix a crash bug with concurrent FLUSH TABLES and INSERT. [GitHub #743][Reported by Watson]

Thanks#

Josep Sanz
Watson

Release 14.04 - 2024-06-12#

Improvements#

[AlmaLinux] Added support for MariaDB 10.5.25, 10.6.18, and 10.11.8.
[Ubuntu] Added support for MariaDB 10.11.7.
[Ubuntu] Added support for MariaDB 10.6.18.
[Debian GNU/Linux] Added support for MariaDB 10.11.8.
[Ubuntu] Added support for MySQL 8.0.36.
[AlmaLinux][Debian GNU/Linux][Ubuntu] Added support for MySQL Community Server 8.0.37.
[AlmaLinux][Debian GNU/Linux][Ubuntu] Added support for MySQL Community Server 8.4.
[AlmaLinux] Added support for Percona Server 8.0.36-28.
[Ubuntu] Added support for Ubuntu 24.04 (Noble Numbat).
Dropped support MySQL Community Server 5.7.

Because MySQL Community Server 5.7 reached EOL.
Dropped support Percona Server 5.7

Because Percona Server for MySQL 5.7 reached EOL.
Dropped support for MariaDB 10.4.

Because MariaDB 10.4 will reach EOL on 2024-06-18.
Dropped support for MariaDB 10.7, 10.8, and 10.9.

Because MariaDB 10.7, 10.8, and 10.9 reached EOL.
Dropped support for MariaDB 10.10.

Because the support term of MariaDB 10.10 is short.
Dropped support for Amazon Linux 2.

Because Groonga already dropped support for Amazon Linux 2.
Dropped support for CentOS 7.

Because CentOS 7 reached EOL.
[Debian GNU/Linux] Dropped support for Debian GNU/Linux bullseye.

Because Debian GNU/Linux bullseye will reach EOL on 2024-07.
Added functionality to output an error when Mroonga’s UDF is used while Mroonga is uninitialized. [MDEV-21166][Reported by Ian Gilfillan.]

Before this fix, using Mroonga’s UDF without initializing Mroonga (not having run INSTALL PLUGIN mroonga) would cause a crash. This patch changes the output from a crash to logging an error.

Fixes#

[Wrapper mode] Fixed memory leaks in cases where engines not supporting online DDL are wrapped.

In general, DDL operations like ALTER TABLE block access to the target table while in progress to maintain exclusive control. However, some storage engines allow operations on the target table during these operations (they can also be executed exclusively). The capability to operate on a table during such DDL operations is referred to as online DDL.

The issue addressed occurs when wrapping storage engines that do not support online DDL in Mroonga’s wrapper mode. It does not occur in storage mode or when using a combination of wrapper mode + InnoDB.
[Storage mode] Fixed a bug causing crashes when inserting into tables with compressed VARCHAR or TEXT columns. [MDEV-31966][Reported by Elena Stepanova.]

This issue occurs only in storage mode and not in wrapper mode.

Thanks#

Ian Gilfillan
Elena Stepanova