News - 15 series#

Release 15.0.3 - 2025-03-10#

Improvements#

Offline index construction: Added support for parallel construction with TABLE_HASH_KEY lexicon#

Parallel offline index construction iterates sorted terms internally. TABLE_PAT_KEY and TABLE_PAT_KEY can do it effectively because they are based on tree. But TABLE_HASH_KEY can’t do it effectively because it’s not based on tree. So we didn’t support parallel offline index construction with TABLE_HASH_KEY lexicon.

This release adds support for parallel offline index construction with TABLE_HASH_KEY lexicon. It sort terms in a normal way. So it’s not so effective. Parallel offline index construction with TABLE_HASH_KEY lexicon will be slower than TABLE_PAT_KEY/TABLE_DAT_KEY. But it may be faster than sequential offline index construction with TABLE_HASH_KEY lexicon.

Release 15.0.2 - 2025-02-21#

Fixes#

Offline index construction: Fixed a bug that options may be ignored in parallel construction#

Groonga may ignore options of Normalizers, Tokenizers and/or Token filters in the target index when offline index construction is executed in parallel.

This issue may occur when:

If NormalizerTable is used and this happens, the offline index construction is failed. Because NormalizerTable has a required parameter. If options are ignored, the required parameter is missing.

Release 15.0.1 - 2025-02-20#

Improvements#

[Ubuntu] Dropped support for Ubuntu 20.04 (Focal Fossa)#

Ubuntu 20.04 will reach EOL in May 2025, so support for it has been dropped starting with this release.

Release 15.0.0 - 2025-02-09#

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

Improvements#

TABLE_PAT_KEY: Added support for Float32 as key type#

GH-2211

TABLE_PAT_KEY encodes/decodes numeric keys for fast search internally. So TABLE_PAT_KEY must know how to encode/decode keys. TABLE_PAT_KEY didn’t know how to encode/decode Float32 before this release. Now, TABLE_PAT_KEY can encode/decode Float32. So you can use Float32 as a TABLE_PAT_KEY key type like other numeric types such as Int32 and Float now.