News - 15 series#

Release 15.05 - 2025-04-08#

Improvements#

Added support for MraiaDB 10.6.21 and 10.11.11#

The are the latest MariaDB releases.

Release 15.04 - 2025-03-29#

Improvements#

Ubuntu: Dropped support for Ubuntu 20.04#

It will reach EOL on 2025-04.

AlmaLinux: Added support for Percona Server 8.4#

It’s available only for AlmaLinux 9 and Red Hat Enterprise Linux 9 compatible distributions.

Added support for MariaDB 11.8 partially#

MariaDB 11.8 isn’t GA yet but Mroonga is buildable with MariaDB 11.8.

MariaDB 11.8 uses utf8mb4_uca1400_* collations by default. groonga-normalizer-mysql 1.2.6 has a utf8mb4_uca1400_* compatible normalizer but it’s not integrated with Mroonga. It’ll be implemented in the next release!

Windows: Changed to use Visual Studio 2022 from 2019#

Our pre-built packages for old releases were built with Visual Studio 2019 but we use Visual Studio 2022 from this release. This will not be affected to users.

Release 15.00 - 2025-02-09#

This is our annual major release! This release doesn’t have any backward incompatible changes! So you can upgrade Mroonga without migrating your existing databases. You can still use your existing databases as-is.

Improvements#

mroonga_n_workers: Added support for parallel execution#

GH-877

You can set concurrency in Groonga by mroonga_n_workers. Some operations such as CREATE INDEX refer this server variable. You can use this to improve performance by using multiple CPU cores.

In general, you should set this in my.cnf not SET. Because this doesn’t change concurrency in the current session (at least for now). If you want to change this by SET, you need to set by SET GLOBAL and re-connect to MySQL.

MariaDB: Added support for MariaDB 10.5.28, 10.6.21, 10.11.11 and 11.4.5#

You can use Mroonga with the latest MariaDB releases.

Fixes#

Wrapper mode: Fixed a bug that wrapped engine’s index information may not be used correctly#

GH-634

If wrapped engine’s index information isn’t used correctly, MariaDB may not be able to use suitable index. It may cause a poor performance query execution.