News¶

Release 5.06 - 2015-08-31¶

Improvements¶

Supported MariaDB 10.1 that is built as embedded server. [MDEV-8508][GitHub#66] [Reported by Sergei Golubchik]
[rpm][mysql55-mroonga] Updated build target MySQL version. [groonga-dev,03421] [Reported by Hiroshi Kagami]

Fixes¶

[rpm][percona-server-56-mroonga] Fixed a crash bug. [GitHub#70] [Patch by GMO Media, Inc.]
Fixed a crash bug when any opening table exists on shutdown. [GitHub#71] [Reported by GMO Media, Inc.]

Thanks¶

GMO Media, Inc.
Sergei Golubchik
Hiroshi Kagami

Release 5.05 - 2015/07/29¶

Improvements¶

[Ubuntu] Dropped Ubuntu 14.10 (Utopic Unicorn) support. It had been End of Life on July 23, 2015.
[rpm][CentOS] Updated to the latest MySQL 5.6 (5.6.26-2) on CentOS 6/7.
[rpm][CentOS] Updated to the latest Percona Server 5.6 (5.6.25-rel73.1) on CentOS 6.

Fixes¶

Fixed a bug that search results are reduced for multiple column index with range condition (e.g. < in WHERE date < '2015-07-01'). [groonga-dev,03332] [GitHub#65] [Reported by foamcentime]
[storage] Fixed memory leaks. [MDEV-8520] [Report by Elena Stepanova]

Thanks¶

foamcentime
Elena Stepanova
Sergei Golubchik

Release 5.04 - 2015/06/29¶

Improvements¶

[rpm][mysql56-community-mroonga][percona-server-56-mroonga] Start mysqld when mysqld is not running within rpm-installation. (This topic is at 5.03-2) [GitHub#58] [Patch by GMO Media, Inc.]
[mariadb10.1] Followed recent API changes.

[mariadb] Supported custom parameters in DDL. This feature can be used only with MariaDB.

Supported TOKENIZER parameter for FULLTEXT IDNEX

CREATE TABLE diaries (
  id int PRIMARY KEY AUTO_INCREMENT,
  body text,
  FULLTEXT INDEX body_index (body) TOKENIZER='TokenBigramSplitSymbolAlphaDigit'
) ENGINE = Mroonga COMMENT = 'engine "InnoDB"' DEFAULT CHARSET = utf8;

Supported NORMALIZER parameter for FULLTEXT IDNEX and normal INDEX

CREATE TABLE memos (
  id INT NOT NULL PRIMARY KEY,
  content TEXT NOT NULL,
  FULLTEXT INDEX (content) NORMALIZER='NormalizerAuto'
) ENGINE = Mroonga COMMENT = 'engine "InnoDB"' DEFAULT CHARSET = utf8;

Supported TOKEN_FILTERS parameter for FULLTEXT IDNEX

CREATE TABLE memos (
  content VARCHAR(64) NOT NULL,
  FULLTEXT INDEX (content) TOKEN_FILTERS='TokenFilterStopWord,TokenFilterStopWord'
) ENGINE = Mroonga COMMENT = 'engine "InnoDB"' DEFAULT CHARSET = utf8;

Supported FLAGS parameter for FULLTEXT INDEX and normal INDEX

CREATE TABLE memos (
  content VARCHAR(64) NOT NULL,
  FULLTEXT INDEX (content) FLAGS='WITH_POSITION|WITH_WEIGHT'
) ENGINE = Mroonga COMMENT = 'engine "InnoDB"' DEFAULT CHARSET = utf8;

Supported GROONGA_TYPE parameter for field

CREATE TABLE tags (
  name VARCHAR(64) PRIMARY KEY
) ENGINE = Mroonga COMMENT = 'engine "InnoDB"' DEFAULT CHARSET = utf8 COLLATE = utf8_bin;

CREATE TABLE bugs (
  id INT UNSIGNED PRIMARY KEY,
  tag VARCHAR(64) GROONGA_TYPE='tags'
) ENGINE = Mroonga COMMENT = 'engine "InnoDB"' DEFAULT CHARSET = utf8;

[storage] Report error for invalid datetime related value on STRICT_TRANS_TABLES. [groonga-dev,03299] [Suggested by GMO Media, Inc.]

It's backward incompatible change. For example:

Prepare (common)

mysql> CREATE TABLE timestamps (
    ->   id INT PRIMARY KEY AUTO_INCREMENT,
    ->   create_dt DATETIME
    -> ) ENGINE = Mroonga DEFAULT CHARSET = utf8;
Query OK, 0 rows affected (0.09 sec)

mysql> SET sql_mode='';
Query OK, 0 rows affected (0.01 sec)

mysql> INSERT INTO timestamps (create_dt) VALUES ("2001-00-00 00:00:00");
Query OK, 1 row affected, 1 warning (0.00 sec)

mysql> SHOW WARNINGS;
+---------+------+------------------------------------------------+
| Level   | Code | Message                                        |
+---------+------+------------------------------------------------+
| Warning | 1265 | Data truncated for column 'create_dt' at row 1 |
+---------+------+------------------------------------------------+
1 row in set (0.00 sec)

mysql> SELECT * FROM timestamps;
+----+---------------------+
| id | create_dt           |
+----+---------------------+
|  1 | 2001-01-01 00:00:00 |
+----+---------------------+
1 row in set (0.00 sec)

mysql> SET sql_mode='STRICT_TRANS_TABLES';
Query OK, 0 rows affected (0.01 sec)

Before (5.03 or earlier)

mysql> INSERT INTO timestamps (create_dt) VALUES ("2002-00-00 00:00:00");
ERROR 1265 (01000): Data truncated for column 'create_dt' at row 1

mysql> SELECT * FROM timestamps;
+----+---------------------+
| id | create_dt           |
+----+---------------------+
|  1 | 2001-01-01 00:00:00 |
|  2 | 2002-01-01 00:00:00 |
+----+---------------------+
2 rows in set (0.00 sec)

After (5.04 or later)

mysql> INSERT INTO timestamps (create_dt) VALUES ("2002-00-00 00:00:00");
ERROR 22003: Out of range value for column 'create_dt' at row 1

mysql> SELECT * FROM timestamps;
+----+---------------------+
| id | create_dt           |
+----+---------------------+
|  1 | 2001-01-01 00:00:00 |
+----+---------------------+
1 row in set (0.00 sec)

Changed keyword to use custom tokenizer to tokenizer from parser.
- In index comment: parser -> tokenizer.
- Server variable: mroonga_default_parser -> mroonga_default_tokenizer.
- parser and mroonga_default_parser are deprecated but they are available at least Mroonga 6.XX.
Renamed parameter name for flags of index column.
- index_flags -> flags.
- index_flags is deprecated but it will be usable on Mroonga 6.XX. It may be removed at Mroonga 7.00.
[storage] Show error message when nonexistent Groonga type is specified to column.
[storage] Renamed parameter name for column's Groonga type.
- type -> groonga_type.
- type is deprecated but it will be usable on Mroonga 6.XX. It may be removed at Mroonga 7.00.

Thanks¶

GMO Media, Inc.

Release 5.03 - 2015/05/29¶

Improvements¶

mariadb10.1: Followed recent API changes.
Supported FT_SORTED flag which is internally used in MySQL. It improves compatibility with MySQL and can reduces redundant sorting in MySQL.
mysql57: Followed recent API changes.

Fixes¶

[storage] Fixed a bug that unique index doesn't work for invalid datetime. This bug is occurred when invalid datetime is inserted. The unique index is created for invalid datetime instead of actual truncated datetime. [groonga-dev,03219] [Reported by Hiroshi Kagami]
[multiple column key] Fixed a potential bug that decoding value is broken. This bug may occurs because proper byte order conversion between network and host is missing on decoding.
[windows] Fixed a bug that needless groonga-normalizer-mysql plugin search is ran when it is embedded into Mroonga. [GitHub#53] [Reported by torinky]
Fixed wrong keyword length when query includes Pragma. This bug causes that it doesn't hit expected search results. [GitHub#54] [Patch by Naoya Murakami]
[storage] Fixed a bug that unique check is ignored for multiple connections. [groonga-dev,03243] [Reported by Hiroshi Kagami]

Thanks¶

Hiroshi Kagami
torinky
Naoya Murakami

Release 5.02 - 2015/04/29¶

Improvements¶

[doc] Updated Release procedure (XXX not yet translated) procedure documentation
[storage] Improved performance to estimate the number of records in range. In the previous versions, Mroonga counts real the number of records in range. There is a performance penalty if huge number of records exists. Note that it requires Groonga 5.0.2 or later. [groonga-dev,03150] [Reported by Masato Shimada]
[experimental] Added mroonga_max_n_records_for_estimate variable to limit the max number of records to estimate. It reduces the estimation cost when there are many target records.
[rpm][centos] Updated to build against the latest MySQL 5.6.
[wrapper] Supported fast order by limit optimization for primary key sort. [Reported by Tsugunori Nashiro]
Supported Debian 8.0 (Jessie)
Supported Ubuntu 15.04 (Vivid Vervet)

Fixes¶

[doc] Fixed old links to Windows package [Reported by METAL_GEAR_mkII]
[storage][mysql56] Fixed a crash bug by duplicated ORDER BY columns. It's occurred when "fast order limit" optimization is detected with duplicated ORDER BY columns in SQL. Note that this bug doesn't affect to MySQL 5.5. [GitHub#50] [Reported by GMO Media, Inc.]

Thanks¶

Masato Shimada
Tsugunori Nashiro
METAL_GEAR_mkII
GMO Media, Inc.

Release 5.01 - 2015/03/29¶

Improvements¶

[storage] Supported PARTITION BY RANGE. Note that this feature is not supported on MariaDB 10. This limitation is derived from MariaDB 10 architecture about removing .par file.
[mysql56] Disabled in-place ALTER TABLE for PRIMARY KEY. This change is derived from Groonga's limitation because Groonga doesn't support to change table key type. [Reported by Hiromitsu KATO]
Dropped Visual Studio 2010 and Visual Studio 2012 support. Use Visual Studio 2013 or later to build Mroonga. [GitHub#45]
[windows] Added Visual Studio 2015 build support.
Supported to specify options by table comment when primary key is using hash by PRIMARY KEY (...) USING HASH. [GitHub#46] [Patch by Naoya Murakami]
Supported index column flags by index comment. You can specify NONE, WITH_POSITION, WITH_SECTION and WITH_WEIGHT as index column flags. Use FULLTEXT INDEX (...) COMMENT 'index_flags "WITH_POSITION|WITH_SECTION"' for example. [GitHub#47] [Patch by Naoya Murakami]
Supported to build with MySQL 5.7.
[rpm][centos] Supported Percona Server 5.6.x on CentOS 6/7. [Tested on CentOS 6 by Yoshino]
Supported utf8_unicode_520_ci and utf8mb4_unicode_520_ci. To support these collations, Mroonga now requires groonga-normalizer-mysql 1.0.9.

Fixes¶

Changed to store score in float. This backward incompatible change is derived from the Groonga DB API change in Groonga 5.0.1. There may be a case the value of score is different.
Added missing error check when failed to create multiple column index in in-place ALTER TABLE.
[mariadb] Fixed crash bug when SET variable is used. This bug depends on MariaDB version. (<= 5.5.41 and <= 10.0.16)
[rpm][centos] Fixed release number for CentOS 7. [GitHub#44] [Reported by CharAz]
[mariadb55] Fixed install failure after installing and uninstalling Mroonga.

Thanks¶

Hiromitsu KATO
Naoya Murakami
Yoshino
CharAz

Release 5.00 - 2015/02/09¶

Bump version to 5.00!

Improvements¶

[appveyor] Supported Windows CI on AppVeyor. We can get notification about build failure on Windows at once. Subscribe to groonga-mysql-commit@lists.sourceforge.jp if you want build status.
[rpm][centos] Build against MySQL 5.6.23-2 on MySQL yum repository. [groonga-dev,03083][Reported by Kohei Aochi]

mroonga - An open-source storage engine for fast fulltext search with MySQL.

News¶

Release 5.06 - 2015-08-31¶

Improvements¶

Fixes¶

Thanks¶

Release 5.05 - 2015/07/29¶

Improvements¶

Fixes¶

Thanks¶

Release 5.04 - 2015/06/29¶

Improvements¶

Thanks¶

Release 5.03 - 2015/05/29¶

Improvements¶

Fixes¶

Thanks¶

Release 5.02 - 2015/04/29¶

Improvements¶

Fixes¶

Thanks¶

Release 5.01 - 2015/03/29¶

Improvements¶

Fixes¶

Thanks¶

Release 5.00 - 2015/02/09¶

Improvements¶

Fixes¶

Thanks¶

Past releases¶

Table Of Contents

This Page