News - 7 series#
Release 7.11 - 2018-01-29#
Improvements#
[test] Added a test case for sub query and order limit optimization. [GitHub#184] [Reported by Kazuki Hamasaki]
[rpm][centos] Supported 10.3.
[deb][ubuntu] Supported MariaDB 10.1 for Ubuntu 17.10 (Artful Aadvark)
Fixes#
[Mroonga_n_pooling_contexts] Fixed a bug that value is reset unexpectedly by
FLUSH STATUS
.[maradb10.3] Fixed a build error which is caused by renamed constant variable (
HA_MUST_USE_TABLE_CONDITION_PUSHDOWN
is renamed toHA_CAN_TABLE_CONDITION_PUSHDOWN
).[macOS] Removed obsolete install guide and updated link to latest documentation [Reported by Ryuji AMANO]
[rpm][centos] Supported MariaDB 10.2.12. [GitHub#186] [Reported by Shota Suzuki]
[rpm][centos] Supported Percona Server 5.7.20-19.
[Ubuntu] Dropped Ubuntu 17.04 (Zesty Zapus) support. It has reached EOL at Jan 13, 2018.
Thanks#
Kazuki Hamasaki
Ryuji AMANO
Shota Suzuki
Release 7.10 - 2017-12-29#
Improvements#
Updated required Groonga version to 7.1.0. You need to restart MySQL after you upgrade to Mroonga 7.10.
[mariadb10.3] Supported MariaDB 10.3.
[rpm][centos] Supported MariaDB 10.2.11.
[rpm][centos] Supported MariaDB 10.1.30.
[rpm][centos] Supported Percona Server 5.7.20.
[rpm][centos] Supported Percona Server 5.6.38.
[Optimizations] Enable count_skip optimization for multi-column index.
Supported condition push down and added related new variables.
[Mroonga_condition_push_down] Added
Mroonga_condition_push_down
.[mroonga_condition_push_down_type] Added
mroonga_condition_push_down_type
. The default value isONE_FULL_TEXT_SEARCH
. It means that condition push down is enabled only whenWHERE
clause has oneMATCH AGAINST
condition. If the valueALL
is set, condition push down is always used (ALL
is experimental for now. We are glad if you use it and tell us if it got faster or not).
Supported column cache when to get fixed size column value to improve performance.
Renamed a function
last_insert_grn_id
tomroonga_last_insert_grn_id
to add missingmroonga_
prefix.last_insert_grn_id
is deprecated. [GitHub#177] [Reported by Ian Gilfillan][Mroonga_n_pooling_contexts] Added a new status variable to show the number of pooling contexts for mroonga_command().
[
FLUSH TABLES
] Added clearing pooling contexts for mroonga_command() support.
Thanks#
Ian Gilfillan
Release 7.09 - 2017-11-29#
Improvements#
[rpm][centos] Supported MariaDB 10.2.10.
[rpm][centos] Supported MariaDB 10.1.29.
Fixed not to require sed to run tests. [Patch by Sergei Golubchik]
[cmake] Changed to skip Mroonga related configurations on without Mroonga build. [Patch by Vladislav Vaintroub]
Thanks#
Sergei Golubchik
Vladislav Vaintroub
Release 7.08 - 2017-10-29#
Improvements#
Supported table level
flags
option. You can specifyTABLE_HASH_KEY
,TABLE_PAT_KEY
,TABLE_DAT_KEY
, andKEY_LARGE
table options. [groonga-dev, 04494] [Reported by Masanori Miyashita][rpm][centos] Supported MySQL 5.6.38-2 and 5.7.20-1.
[Ubuntu] Supported Ubuntu 17.10 (Artful Aardvark).
Thanks#
Masanori Miyashita
Release 7.07 - 2017-10-12#
Improvements#
[mroonga_query_expand] Added
mroonga_query_expand
UDF. If you prepare synonyms table in advance, you can get expanded synonym in your query bymroonga_query_expanded
. Note that Groonga 7.0.6 or later version is required to use this function.[rpm][centos] Supported Percona Server 5.7.19-17.1. [Reported by tigersun2000]
[rpm][centos] Supported MariaDB 5.5.56-2. [Reported by akiko_pusu]
[rpm][centos] Supported MariaDB 10.1/10.2 provided by MariaDB.
Fixes#
Fixed a bug that wrong database may be used on “DROP DATABASE”. This bug may cause a crash because internal “mroonga_operations” table is removed unexpectedly. It may happen when the following two conditions are true:
There are multiple databases that uses Mroonga.
“DROP DATABASE” against no longer Mroonga tables exist.
As unexpected result, “DROP DATABASE x” may remove “mroonga_operations” table on existing “y” database.
Fix a crash bug after CHECK TABLE is used. [GitHub#167] [Reported by GMO Media, Inc.]
[deb][mariadb10] Added missing dependency to lsb-release package for preinst and postrm maintainer script. [GitHub#169] [Patch by Tatsuki Sugiura]
Thanks#
@tigersun2000
@akiko_pusu
GMO Media, Inc.
Tatsuki Sugiura
Release 7.06 - 2017-08-29#
Improvements#
[mroonga_highlight_html()] Added usage about
mroonga_highlight_html
.Supported generated column. It is useful to full-text search for partially extracted content from JSON column. [GitHub#159,#160,#163] [Patch by Naoya Murakami]
Added mroonga_enable_operations_recording. variable. [GitHub#158] [Patch by Naoya Murakami]
Supported virtual column for MariaDB 10.2 and MySQL 5.7. It supports
VIRTUAL
type. [GitHub#161,#162] [Patch by Naoya Murakami]Supported MariaDB 10.1.26.
[rpm][centos] Supported Percona Server 5.6.36 rel82.1 and 5.7.18-16. [Gitter/ja:59894500bc46472974622cbd] [Reported by @tigersun2000_twitter]
[rpm][centos] Supported MySQL 5.6.37 and 5.7.19 on CentOS 7. [groonga-dev,04441] [Reported by Kagami Hiroshi]
Thanks#
Naoya Murakami
@tigersun2000_twitter
Kagami Hiroshi
Release 7.05 - 2017-07-29#
Improvements#
Supported Groonga query log. Use
mroonga_query_log_file
variable to use this feature. [GitHub#148]Supported MariaDB 10.2.7. [groonga-dev,04397] [Reported by Tomohiro ‘Tomo-p’ KATO]
[mroonga_command()] Supported database name that has special name such as
db-1
for example. It contains special character-
.[mroonga_command()] Supported auto command syntax escape feature. It makes easy to use Groonga functionality from Mroonga.
Supported MariaDB 5.5.57.
[rpm][centos] Supported MySQL 5.6.37-2 and MySQL 5.7.19-1 on CentOS 6. [groonga-dev,04403] [Reported by Kagami Hiroshi]
[Ubuntu] Dropped Ubuntu 16.10 (Yekkety Yak) support. It has reached EOL at July 20, 2017.
[mroonga_highlight_html()] Supported a function to highlight target column or text.
Fixes#
Fixed a crash bug when there is no active index internally. [Gitter:groonga/ja:596714a5c101bc4e3a7db4e5] [Reported by K Torimoto]
Thanks#
K Torimoto
Tomohiro ‘Tomo-p’ KATO
Kagami Hiroshi
Release 7.04 - 2017-06-29#
Improvements#
Supported to show error message when failed to create a table for matched records. This kind of error occurs when indexes are broken. This error message helps to identify problem.
[Debian GNU/Linux] Supported Debian 9 (stretch).
Fixes#
Fixed a crash bug that missing
NULL
check before callinggrn_table_setoperation
causes. Such a crash bug occurs when indexes are broken.
Release 7.03 - 2017-05-29#
Improvements#
[Limitations] Updated limitations about NULL in column. [Gitter/ja] [Reported by @bignum_twitter]
Supported
INDEX_MEDIUM
andINDEX_SMALL
flags. [GitHub#141] [Patch by Naoya Murakami][CentOS] Supported recent Percona Server 5.6.36 and 5.7.18. [Reported by @pinpikokun]
Thanks#
@bignum_twitter
@pinpikokun
Naoya Murakami
Release 7.02 - 2017-04-29#
Improvements#
Fixes#
[CentOS] Fixed build error with MySQL 5.6.36 and MySQL 5.7.18.
[cmake] Fixed missing link to
libgroonga
when mroonga is bundled andlibgroonga
isn’t bundled. [GitHub#137] [Patch by Naoya Murakami]
Thanks#
Naoya Murakami
Release 7.01 - 2017-03-29#
Improvements#
[CentOS] Dropped CentOS 5 support because of EOL.
[Storage mode] Supported
ALTER TABLE ADD/DROP FOREIGN KEY
.[Storage mode] Supported fast
ORDER LIMIT
withENUM
. [groonga-dev,04277] [Reported by murata satoshi]Supported
COMPRESS_ZSTD
column compression flag. [GitHub#133] [Patch by Naoya Murakami][Server variables] Added documentation about mroonga_libgroonga_support_zstd variable. [GitHub#133] [Patch by Naoya Murakaimi]
[Install] Changed to recommend
https://packages.groonga.org
for downloading resources.
Fixes#
[Storage mode] Fixed update error for log-bin and
UPDATE
with collatedPRIMARY KEY
. [GitHub#132] [Reported by kitora]Fixed a bug that
FOREIGN KEY
is dumped unexpectedly even though you didn’t set it. [groonga-dev,04276] [Reported by murata satoshi]
Thanks#
kitora
murata satoshi
Naoya Murakami
Release 7.00 - 2017-02-09#
Improvements#
[CentOS] Changed to ensure enabling EPEL to install package.
Supported
FOREIGN KEY
constrain onUPDATE
andDELETE
parent row. In the previous versions, onlyFOREIGN KEY
constrain onINSERT
is supported.[Storage mode] Supported updating row even though its table has primary key with ROW binlog format. In the previous version, it causes update statement error. [GitHub#130] [Reported by kitora]
Thanks#
kitora