Mroonga blog

2018-08-29

Mroonga 8.06 has been released!

Mroonga is a MySQL storage engine that supports fast fulltext search and geolocation search. It is CJK ready. It uses Groonga as a storage and fulltext search engine.

Mroonga 8.06 has been released!

Changes

In this version, MySQL will be automatically restarted if you had already installed Mroonga and not installed Groonga 8.0.4 or later. Because Mroonga 8.06 requires Groonga 8.0.4 or later but it will not reloaded until MySQL is restarted.

The main changes are as follows.

Conclusion

See Release 8.06 - 2018-08-29 about detailed changes since 8.03.

Let's search by Mroonga!

2018-05-29

Mroonga 8.03 has been released!

Mroonga is a MySQL storage engine that supports fast fulltext search and geolocation search. It is CJK ready. It uses Groonga as a storage and fulltext search engine.

Mroonga 8.03 has been released!

Changes

The main changes are as follows. There are no big changes in this release.

  • [Docker] Added quick start guide link to Docker Hub.
    • The contributors are helping to maintain monthly. Thank you!
  • [CentOS] Supported MariaDB 10.3.7.
  • [CentOS] Supported MariaDB 10.2.15 and 10.1.33 (backported to 8.03).
  • [Windows] Supported MariaDB 10.1.33.

Conclusion

See Release 8.03 - 2018-05-29 about detailed changes since 8.02.

Let's search by Mroonga!

2018-04-29

Mroonga 8.02 has been released!

Mroonga is a MySQL storage engine that supports fast fulltext search and geolocation search. It is CJK ready. It uses Groonga as a storage and fulltext search engine.

Mroonga 8.02 has been released!

Changes

The main changes are as follows. We recommend you to upgrade because some bugs are fixed.

  • Supported Ubuntu 18.04 LTS (Bionic Beaver).
  • [CentOS][Percona Server] Supported upgrading from "< 5.6.34" and "< 5.7.21".
  • Fixed a crash bug when some complex condition in ORDER BY such as ORDER BY 1 + 1, id, content.
  • Fixed a bug that MATCH AGAINST condition is ignored if SQL containing such as AND (x = 1 OR x = 2) when condition push down is enabled.
  • Fixed a memory leak for column caches.

Conclusion

See Release 8.02 - 2018-04-29 about detailed changes since 8.01.

Let's search by Mroonga!

2018-03-29

Mroonga 8.01 has been released!

Mroonga is a MySQL storage engine that supports fast fulltext search and geolocation search. It is CJK ready. It uses Groonga as a storage and fulltext search engine.

Mroonga 8.01 has been released!

In this release, Mroonga requires latest Groonga 8.0.1 to fix bugs. It means that MySQL/MariaDB must be restarted to upgrade package correctly.

If you have already installed Mroonga via apt or yum, MySQL/MariaDB will be restarted automatically during upgrading package.

Changes

The main changes are as follows.

  • Fixed a bug that wrong cache for other database is used

Fixed a bug that wrong cache for other database is used

In this release, wrong cache related bug was fixed.

This bug occurs the following conditions are met.

  • Multiple database are created
  • Use mroonga_command() against one of them

If you don't use mroonga_command() in query, above conditions are not met, so this bug doesn't affect you.

Conclusion

See Release 8.01 - 2018-03-29 about detailed changes since 8.00.

Let's search by Mroonga!

2018-02-09

Mroonga 8.00 has been released!

Mroonga is a MySQL storage engine that supports fast fulltext search and geolocation search. It is CJK ready. It uses Groonga as a storage and fulltext search engine.

This is a major version up! But It keeps backward compatibility. You can upgrade to 8.0.0 without rebuilding database.

Mroonga 8.00 has been released!

Changes

The main changes are as follows.

  • When create hash index, tiny hash is used for reducing consumption of resources.
  • [percona57] Added gap lock detection support.

When create hash index, used tiny hash for reducing used resource

Hash index is less resouce to used from this release. Note:that rebuilding indexes are required to enable this feature for existence indexes

[percona57] Added gap lock detection support

a gap lock was being attempted while the transaction isolation level was either REPEATABLE READ or SERIALIZABLE, the following SQL error was returned to the client and no actual gap lock was taken on the affected rows.

ERROR 1105 (HY000): Using Gap Lock without full unique key in multi-table or multi-statement transactions is not allowed. You need to either rewrite queries to use all unique key columns in WHERE equal conditions, or rewrite to single-table, single-statement transaction.  Query: ALTER TABLE t ENGINE=InnoDB

From this release, as the above situation, gap lock will be taken on the affected rows.

Conclusion

See Release 8.00 - 2018-02-09 about detailed changes since 7.11.

Let's search by Mroonga!