You can subscribe to this list here.
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(2) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2012 |
Jan
(2) |
Feb
(1) |
Mar
(3) |
Apr
(4) |
May
(2) |
Jun
(2) |
Jul
(4) |
Aug
(4) |
Sep
(5) |
Oct
(4) |
Nov
(7) |
Dec
(4) |
| 2013 |
Jan
(20) |
Feb
(35) |
Mar
(15) |
Apr
(5) |
May
(2) |
Jun
(2) |
Jul
(3) |
Aug
(3) |
Sep
(2) |
Oct
(2) |
Nov
(4) |
Dec
(3) |
| 2014 |
Jan
(3) |
Feb
(13) |
Mar
(14) |
Apr
(3) |
May
(8) |
Jun
(1) |
Jul
(5) |
Aug
(6) |
Sep
(12) |
Oct
(4) |
Nov
(4) |
Dec
(4) |
| 2015 |
Jan
(3) |
Feb
(7) |
Mar
(2) |
Apr
(7) |
May
(4) |
Jun
(4) |
Jul
(4) |
Aug
|
Sep
(7) |
Oct
(17) |
Nov
(7) |
Dec
(30) |
| 2016 |
Jan
(2) |
Feb
|
Mar
(7) |
Apr
(3) |
May
(2) |
Jun
(5) |
Jul
(1) |
Aug
(3) |
Sep
(9) |
Oct
(2) |
Nov
(2) |
Dec
(2) |
| 2017 |
Jan
(4) |
Feb
(2) |
Mar
(5) |
Apr
(3) |
May
(3) |
Jun
(3) |
Jul
(7) |
Aug
(3) |
Sep
|
Oct
(5) |
Nov
(2) |
Dec
(2) |
| 2018 |
Jan
(11) |
Feb
(3) |
Mar
(2) |
Apr
|
May
(4) |
Jun
(1) |
Jul
(1) |
Aug
(2) |
Sep
(2) |
Oct
(1) |
Nov
(3) |
Dec
(2) |
| 2019 |
Jan
(1) |
Feb
(2) |
Mar
(2) |
Apr
(1) |
May
(3) |
Jun
(1) |
Jul
(7) |
Aug
(9) |
Sep
(4) |
Oct
(2) |
Nov
(1) |
Dec
(1) |
| 2020 |
Jan
(4) |
Feb
|
Mar
(4) |
Apr
(3) |
May
(3) |
Jun
(5) |
Jul
(3) |
Aug
(2) |
Sep
(7) |
Oct
(2) |
Nov
(1) |
Dec
(7) |
| 2021 |
Jan
(2) |
Feb
(7) |
Mar
|
Apr
(2) |
May
(5) |
Jun
(4) |
Jul
(1) |
Aug
(6) |
Sep
(3) |
Oct
(2) |
Nov
(10) |
Dec
(5) |
| 2022 |
Jan
(1) |
Feb
(6) |
Mar
(3) |
Apr
(1) |
May
(1) |
Jun
(4) |
Jul
|
Aug
(4) |
Sep
(1) |
Oct
(1) |
Nov
|
Dec
|
| 2023 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2024 |
Jan
|
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Sutou K. <ko...@cl...> - 2024-03-06 06:03:15
|
Hi, No! We'll update Mroonga in a few months! Related: https://github.com/mroonga/mroonga/discussions/675 Thanks, -- kou In <mOL...@sm...> "[groonga-talk:569] Updates for mroonga" on Tue, 5 Mar 2024 17:26:17 +0100, Josep Sanz <jos...@gm...> wrote: > Hi team. > > I have detected that appear new releases for > groonga but not for mroonga. > > Are you planning to stop updating the mroonga > engine??? > > Thanks in advance. > > Josep. > > -- > Josep Sanz Campderrós > https://www.josepsanz.net > The SaltOS project > https://www.saltos.org |
|
From: Josep S. <jos...@gm...> - 2024-03-05 16:26:32
|
Hi team. I have detected that appear new releases for groonga but not for mroonga. Are you planning to stop updating the mroonga engine??? Thanks in advance. Josep. -- Josep Sanz Campderrós https://www.josepsanz.net The SaltOS project https://www.saltos.org |
|
From: Sutou K. <ko...@cl...> - 2023-07-06 01:11:06
|
Hi, There is no plan for SQLite3 support. If you don't want to use Groonga directly, PGroonga (PostgreSQL + Groonga) may be an option for you. Thanks, -- kou In <NZa...@tu...> "[groonga-talk:567] FWD: Support for sqlite3" on Wed, 5 Jul 2023 14:28:31 +0200 (CEST), Sagar Acharya via groonga-talk <gro...@li...> wrote: > > >> Dear folks, >> >> Are there any plans for supporting sqlite3 database for Groonga. I want to set up Groonga for my mini self-hosted server and sqlite3 is far more convenient and better to do so. >> >> Thanks for the wonderful project. >> >> Thanking you >> Sagar Acharya >> https://humaaraartha.in >> > > > _______________________________________________ > groonga-talk mailing list > gro...@li... > https://lists.sourceforge.net/lists/listinfo/groonga-talk |
|
From: Sagar A. <sag...@tu...> - 2023-07-05 12:46:55
|
> Dear folks, > > Are there any plans for supporting sqlite3 database for Groonga. I want to set up Groonga for my mini self-hosted server and sqlite3 is far more convenient and better to do so. > > Thanks for the wonderful project. > > Thanking you > Sagar Acharya > https://humaaraartha.in > |
|
From: Horimoto Y. <hor...@cl...> - 2022-10-13 00:40:03
|
Hi, We change the destination of release announcements to GitHub Discussions from a mailing list. Because the mailing list is instability because of we may have not been able to send to Mailing list a certain period. We can see release announcements as below URL in future. Groonga: https://github.com/groonga/groonga/discussions/categories/releases Mroonga: https://github.com/mroonga/mroonga/discussions/categories/releases Regards, |
|
From: 橋田 貴志 <ha...@cl...> - 2022-09-01 02:06:37
|
Hi,
Mroonga 12.07 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.
Document:
https://mroonga.org/docs/
How to install: Install Guide
https://mroonga.org/docs/install.html
How to upgrade: Upgrade Guide
https://mroonga.org/docs/upgrade.html
Blog:
https://mroonga.org/en/blog/2022/08/30/mroonga-12.07.html
Changes:
https://mroonga.org/docs/news.html#release-12.07
### Changes
The main changes are as follows.
### Improvements
* [CentOS], [AlmaLinux] Added support for MariaDB 10.3.36, 10.4.26,
10.5.17, 10.6.9, 10.7.5 and 10.8.4.
* [CentOS], [AlmaLinux] Added support for Percona Server 5.7.39-42.
* [CentOS], [AlmaLinux] Added support for Percona Server 8.0.29-21.
MySQL 8.0.29 used by Percona Server 8.0.29 has a critical issue. So
we do not recommend to use this version.
See MySQL 8.0.29 Release Notes
(https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-29.html) for
details about the issue.
### Fixes
* Fixed a bug to fail to install or upgrade Mroonga with install.sql.
Broken install.sql caused this bug. This bug had occurred since
Mroonga 12.06.
* Fixed a bug that mroonga_command() returns results with hex dump for
MySQL 8.0 and above.
mroonga_command() returns results with a correct character code form
this version.
* [AlmaLinux] Fixed an installation document for Mroonga on AlmaLinux 8.
|
|
From: 橋田 貴志 <ha...@cl...> - 2022-08-30 08:34:05
|
Hi, Groonga 12.0.7 has been released! https://groonga.org/docs/news.html#release-12-0-7 https://groonga.org/en/blog/2022/08/29/groonga-12.0.7.html Install: https://groonga.org/docs/install.html Characteristics: https://groonga.org/docs/characteristic.html The topics in this release: ### Improvements * Added a new function escalate(). (experimental) The escalate() function is similar to the existing match escalation ( Search ). We can use this function for any conditions. (The existing match escalation is just for one full text search by invert index.) The escalate() function is useful when we want to limit the number of results of a search. Even if we use --limit, we can limit the number of results of a search. However, --limit is evaluated after evaluating all conditions in our query. The escalate() function finish the evaluation of conditions at that point when the result set has greater than THRESHOLD records. In other words, The escalate() function may reduce the number of evaluating conditions. The syntax of the escalate() function as below:: escalate(THRESHOLD_1, CONDITION_1, THRESHOLD_2, CONDITION_2, ..., THRESHOLD_N, CONDITION_N) THRESHOLD_N is a positive number such as 0 and 29. CONDITION_N is a string that uses script_syntax such as number_column > 29. If the current result set has less than or equal to THRESHOLD_1 records, the corresponding CONDITION_1 is executed. Similarly, if the next result set has less than or equal to THRESHOLD_2 records, the corresponding CONDITION_2 is executed. If the next result set has greater than THRESHOLD_3 records, the escalate() function is finished. If all CONDITION s are executed, escalate(THRESHOLD_1, CONDITION_1, ..., THRESHOLD_N, CONDITION_N) is same as CONDITION_1 || ... || CONDITION_N. The escalate() function can be worked with logical operators such as && and &! :: number_column > 10 && escalate(THRESHOLD_1, CONDITION_1, ..., THRESHOLD_N, CONDITION_N) number_column > 10 &! escalate(THRESHOLD_1, CONDITION_1, ..., THRESHOLD_N, CONDITION_N) They are same as number_column > 10 && (CONDITION_1 || ... || CONDITION_N) and number_column > 10 &! (CONDITION_1 || ... || CONDITION_N) . However, these behaviors may be changed because they may not be useful. * [httpd] Updated bundled nginx to 1.23.1. * [select] Add a document for the --n_workers option. ### Fixes * Fixed a bug Groonga's response may be slow when we execute the request_cancel while executing a OR search. When the number of results of the OR search is many and a query has many OR conditions, Groonga may response slow with the "request_cancel" command. ### Known Issues * Currently, Groonga has a bug that there is possible that data is corrupt when we execute many additions, delete, and update data to vector column. * *< and *> only valid when we use query() the right side of filter condition. If we specify as below, *< and *> work as &&. * 'content @ "Groonga" *< content @ "Mroonga"' * Groonga may not return records that should match caused by GRN_II_CURSOR_SET_MIN_ENABLE. |
|
From: Horimoto Y. <hor...@cl...> - 2022-08-08 06:41:45
|
Hi, PGroonga 2.3.8 has been released! https://pgroonga.github.io/news/#version-2-3-8 This version is compatible with the before version. You can upgrade by steps in "Compatible case" in the Upgrade document. https://pgroonga.github.io/upgrade/#compatible-case Here are the important changes in this release * Added support for Unlogged Table. We can create a index of PGroonga on Unlogged Table. * [Debian] Dropped support for Debian 10 (buster). Because Debian 10 (buster) reaches EOL in August 2022. * [Ubuntu] Dropped ssupport for Ubuntu 21.10 (Impish Indri). Because Ubuntu 21.10 reached EOL in July 2022. * [pgroonga-query-expand] Added document for an example of how to search keywords using synonym groups in the document of pgroonga_query_expand(). |
|
From: Horimoto Y. <hor...@cl...> - 2022-08-05 04:03:08
|
Hi, Mroonga 12.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. Document: https://mroonga.org/docs/ How to install: Install Guide https://mroonga.org/docs/install.html How to upgrade: Upgrade Guide https://mroonga.org/docs/upgrade.html Blog: https://mroonga.org/en/blog/2022/08/04/mroonga-12.06.html Changes: https://mroonga.org/docs/news.html#release-12.06 ### Changes The main changes are as follows. ### Improvements * [CentOS] Added support for MySQL 5.7.39. * [CentOS], [AlmaLinux] Added support for MySQL 8.0.39. * [CentOS], [AlmaLinux] Added support for Percona Server 8.0.28-20. * [CentOS], [AlmaLinux] Added support for MariaDB 10.8. * [CentOS], [AlmaLinux] Dropped support for MariaDB 10.2. * [Debian] Dropped support for Debian 10 (buster). * Changed to not require to run update.sql for registering Mroonga to MySQL. Mroonga has required to run both install.sql and update.sql to register to MySQL since Mroonga 12.04. % mysql -u root < /usr/share/mroonga/install.sql % mysql -u root < /usr/share/mroonga/update.sql This improvement has changed Mroonga to only require to run install.sql to register to MySQL as before than Mroonga 12.04. % mysql -u root < /usr/share/mroonga/install.sql |
|
From: Horimoto Y. <hor...@cl...> - 2022-08-04 05:11:50
|
Hi, Groonga 12.0.6 has been released! https://groonga.org/docs/news.html#release-12-0-6 https://groonga.org/en/blog/2022/08/04/groonga-12.0.6.html Install: https://groonga.org/docs/install.html Characteristics: https://groonga.org/docs/characteristic.html The topics in this release: ### Improvements * Added new Munin plugins for groonga-delta. We can monitoring the following items by plugins for groonga-delta. * Whether groonga-delta-import can import or not .grn file on local storage. * Whether groonga-delta-import can import or not difference data of MySQL. * Whether groonga-delta-apply can apply imported data or not. * The total size of applying data. * [column_copy] Added support for weight vector. We can copy the value of weight vector by column_copy as below. table_create Tags TABLE_HASH_KEY ShortText [[0,0.0,0.0],true] table_create CopyFloat32Value TABLE_HASH_KEY ShortText [[0,0.0,0.0],true] column_create CopyFloat32Value source_tags COLUMN_VECTOR|WITH_WEIGHT|WEIGHT_FLOAT32 Tags [[0,0.0,0.0],true] column_create CopyFloat32Value destination_tags COLUMN_VECTOR|WITH_WEIGHT|WEIGHT_FLOAT32 Tags [[0,0.0,0.0],true] load --table CopyFloat32Value [ { "_key": "Groonga is fast!!!", "source_tags": { "Groonga": 2.8, "full text search": 1.5 } } ] [[0,0.0,0.0],1] column_copy CopyFloat32Value source_tags CopyFloat32Value destination_tags [[0,0.0,0.0],true] select CopyFloat32Value [ [ 0, 0.0, 0.0 ], [ [ [ 1 ], [ [ "_id", "UInt32" ], [ "_key", "ShortText" ], [ "destination_tags", "Tags" ], [ "source_tags", "Tags" ] ], [ 1, "Groonga is fast!!!", { "Groonga": 2.8, "full text search": 1.5 }, { "Groonga": 2.8, "full text search": 1.5 } ] ] ] ] * [Ubuntu] Dropped support for Ubuntu 21.10 (Impish Indri). Because Ubuntu 21.10 reached EOL in July 2022. * [Debian] Dropped Debian 10 (buster) support. Because Debian 10 reaches EOL in August 2022. ### Fixes * Fixed a bug that Groonga may crash when we execute drilldown in a parallel by n_workers option. * [select] Fixed a bug that the syntax error occurred when we specify a very long expression in --filter. Because the max stack size for the expression of --filter was 100 until now. ### Known Issues * Currently, Groonga has a bug that there is possible that data is corrupt when we execute many additions, delete, and update data to vector column. * *< and *> only valid when we use query() the right side of filter condition. If we specify as below, *< and *> work as &&. * 'content @ "Groonga" *< content @ "Mroonga"' * Groonga may not return records that should match caused by GRN_II_CURSOR_SET_MIN_ENABLE. |
|
From: Horimoto Y. <hor...@cl...> - 2022-06-30 04:13:05
|
Hi, Groonga 12.0.5 has been released! https://groonga.org/docs/news.html#release-12-0-5 https://groonga.org/en/blog/2022/06/29/groonga-12.0.5.html Install: https://groonga.org/docs/install.html Characteristics: https://groonga.org/docs/characteristic.html The topics in this release: ### Improvements * [select] Improved a little bit of performance for prefix search by search escalation. * [select] Added support for specifying a reference vector column with weight in drilldowns[LABEL]._key. If we specified a reference vector column with weight in drilldown's key, Groonga had returned incorrect results until now. For example, the following tag search had returned incorrect results until now. table_create Tags TABLE_PAT_KEY ShortText table_create Memos TABLE_HASH_KEY ShortText column_create Memos tags COLUMN_VECTOR|WITH_WEIGHT Tags column_create Memos date COLUMN_SCALAR Time load --table Memos [ {"_key": "Groonga is fast!", "tags": {"full-text-search": 100}, "date": "2014-11-16 00:00:00"}, {"_key": "Mroonga is fast!", "tags": {"mysql": 100, "full-text-search": 80}, "date": "2014-11-16 00:00:00"}, {"_key": "Groonga sticker!", "tags": {"full-text-search": 100, "sticker": 10}, "date": "2014-11-16 00:00:00"}, {"_key": "Rroonga is fast!", "tags": {"full-text-search": 100, "ruby": 20}, "date": "2014-11-17 00:00:00"}, {"_key": "Groonga is good!", "tags": {"full-text-search": 100}, "date": "2014-11-17 00:00:00"} ] select Memos \ --drilldowns[tags].keys tags \ --drilldowns[tags].output_columns _key,_nsubrecs [ [ 0, 1656480220.591901, 0.0005342960357666016 ], [ [ [ 5 ], [ [ "_id", "UInt32" ], [ "_key", "ShortText" ], [ "date", "Time" ], [ "tags", "Tags" ] ], [ 1, "Groonga is fast!", 1416063600.0, {"full-text-search":100} ], [ 2, "Mroonga is fast!", 1416063600.0, {"mysql":100,"full-text-search":80} ], [ 3, "Groonga sticker!", 1416063600.0, {"full-text-search":100,"sticker":10} ], [ 4, "Rroonga is fast!", 1416150000.0, {"full-text-search":100,"ruby":20} ], [ 5, "Groonga is good!", 1416150000.0, {"full-text-search":100} ] ], { "tags": [ [ 8 ], [ [ "_key", "ShortText" ], [ "_nsubrecs", "Int32" ] ], [ "full-text-search", 5 ], [ "f", 5 ], [ "mysql", 1 ], [ "f", 1 ], [ "sticker", 1 ], [ "f", 1 ], [ "ruby", 1 ], [ "f", 1 ] ] } ] ] The above query returns correct results as below since this release. select Memos --drilldowns[tags].keys tags --drilldowns[tags].output_columns _key,_nsubrecs [ [ 0, 0.0, 0.0 ], [ [ [ 5 ], [ [ "_id", "UInt32" ], [ "_key", "ShortText" ], [ "date", "Time" ], [ "tags", "Tags" ] ], [ 1, "Groonga is fast!", 1416063600.0, { "full-text-search": 100 } ], [ 2, "Mroonga is fast!", 1416063600.0, { "mysql": 100, "full-text-search": 80 } ], [ 3, "Groonga sticker!", 1416063600.0, { "full-text-search": 100, "sticker": 10 } ], [ 4, "Rroonga is fast!", 1416150000.0, { "full-text-search": 100, "ruby": 20 } ], [ 5, "Groonga is good!", 1416150000.0, { "full-text-search": 100 } ] ], { "tags": [ [ 4 ], [ [ "_key", "ShortText" ], [ "_nsubrecs", "Int32" ] ], [ "full-text-search", 5 ], [ "mysql", 1 ], [ "sticker", 1 ], [ "ruby", 1 ] ] } ] ] * [select] Added support for doing drilldown with a reference vector with weight even if we use query or filter, or post_filter. If we specified a reference vector column with weight in drilldown's key when we use query or filter, or post_filter, Groonga had returned incorrect results or errors until now. For example, the following query had been erred until now. table_create Tags TABLE_PAT_KEY ShortText table_create Memos TABLE_HASH_KEY ShortText column_create Memos tags COLUMN_VECTOR|WITH_WEIGHT Tags column_create Memos date COLUMN_SCALAR Time load --table Memos [ {"_key": "Groonga is fast!", "tags": {"full-text-search": 100}, "date": "2014-11-16 00:00:00"}, {"_key": "Mroonga is fast!", "tags": {"mysql": 100, "full-text-search": 80}, "date": "2014-11-16 00:00:00"}, {"_key": "Groonga sticker!", "tags": {"full-text-search": 100, "sticker": 10}, "date": "2014-11-16 00:00:00"}, {"_key": "Rroonga is fast!", "tags": {"full-text-search": 100, "ruby": 20}, "date": "2014-11-17 00:00:00"}, {"_key": "Groonga is good!", "tags": {"full-text-search": 100}, "date": "2014-11-17 00:00:00"} ] select Memos \ --filter true \ --post_filter true \ --drilldowns[tags].keys tags \ --drilldowns[tags].output_columns _key,_nsubrecs [ [ -22, 1656473820.734894, 0.03771400451660156, "[hash][add][ ] key size unmatch", [ [ "grn_hash_add", "hash.c", 3405 ] ] ], [ [ ] ] ] The above query returns correct results as below since this release. select Memos \ --filter true \ --post_filter true \ --drilldowns[tags].keys tags \ --drilldowns[tags].output_columns _key,_nsubrecs [ [ 0, 0.0, 0.0 ], [ [ [ 5 ], [ [ "_id", "UInt32" ], [ "_key", "ShortText" ], [ "date", "Time" ], [ "tags", "Tags" ] ], [ 1, "Groonga is fast!", 1416063600.0, { "full-text-search": 100 } ], [ 2, "Mroonga is fast!", 1416063600.0, { "mysql": 100, "full-text-search": 80 } ], [ 3, "Groonga sticker!", 1416063600.0, { "full-text-search": 100, "sticker": 10 } ], [ 4, "Rroonga is fast!", 1416150000.0, { "full-text-search": 100, "ruby": 20 } ], [ 5, "Groonga is good!", 1416150000.0, { "full-text-search": 100 } ] ], { "tags": [ [ 4 ], [ [ "_key", "ShortText" ], [ "_nsubrecs", "Int32" ] ], [ "full-text-search", 5 ], [ "mysql", 1 ], [ "sticker", 1 ], [ "ruby", 1 ] ] } ] ] ### Known Issues * Currently, Groonga has a bug that there is possible that data is corrupt when we execute many additions, delete, and update data to vector column. * *< and *> only valid when we use query() the right side of filter condition. If we specify as below, *< and *> work as &&. * 'content @ "Groonga" *< content @ "Mroonga"' * Groonga may not return records that should match caused by GRN_II_CURSOR_SET_MIN_ENABLE. |
|
From: Horimoto Y. <hor...@cl...> - 2022-06-10 01:51:31
|
Hi, PGroonga 2.3.7 has been released! https://pgroonga.github.io/news/#version-2-3-7 This version is compatible with the before version. You can upgrade by steps in "Compatible case" in the Upgrade document. https://pgroonga.github.io/upgrade/#compatible-case Here are the important changes in this release * Add support for pg_stat_progress_create_index. For example, we can get the progress for creating an index of PGroonga as below SQL. * SELECT * FROM pg_stat_progress_create_index; * [Ubuntu] Added support for Ubuntu 22.04. |
|
From: Horimoto Y. <hor...@cl...> - 2022-06-06 11:47:10
|
Hi, Mroonga 12.04 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. Document: https://mroonga.org/docs/ How to install: Install Guide https://mroonga.org/docs/install.html How to upgrade: Upgrade Guide https://mroonga.org/docs/upgrade.html Blog: https://mroonga.org/en/blog/2022/06/06/mroonga-12.04.html Changes: https://mroonga.org/docs/news.html#release-12.04 ### Changes The main changes are as follows. ### Improvements * [Server variables] Add a new status variable Mroonga_memory_map_size. We can get the total memory map size in bytes of Mroonga as below. mysql> SHOW STATUS LIKE 'Mroonga_memory_map_size'; +-------------------------+----------+ | Variable_name | Value | +-------------------------+----------+ | Mroonga_memory_map_size | 83406848 | +-------------------------+----------+ 1 row in set (0.00 sec) In Windows, If Mroonga uses up physical memory and swap area, Mroonga can’t more mapping memory than that. Therefore, we can control properly memory map size by monitoring this value even if the environment does have not enough memory. * [CentOS][AlmaLinux] Added support for Percona Server 8.0.28-19. * [CentOS][AlmaLinux] Added support for Percona Server 5.7.38-41. * [CentOS][AlmaLinux] Added support for MariaDB 10.2.44, 10.3.35, 10.4.25, 10.5.16, 10.6.8, and 10.7.4. ### Fixes * Fixed a bug that Mroonga may update failed. If this bug occurs, Mroonga is disabled after Mroonga update with such as “apt update”. In that case, we install Mroonga manually with the following procedure. % mysql -u root < /usr/share/mroonga/install.sql |
|
From: Horimoto Y. <hor...@cl...> - 2022-06-06 05:34:58
|
Hi, Groonga 12.0.4 has been released! https://groonga.org/docs/news.html#release-12-0-4 https://groonga.org/en/blog/2022/06/06/groonga-12.0.4.html Install: https://groonga.org/docs/install.html Characteristics: https://groonga.org/docs/characteristic.html The topics in this release: ### Improvements * [Ubuntu] Added support for Ubuntu 22.04 (Jammy Jellyfish). * We don't provide `groonga-benchmark`. Because nobody will not use it and we can't maintain it. * [status] Added a new item memory_map_size. We can get the total memory map size in bytes of Groonga with status command. status [ [ 0, 1654237168.304533, 0.0001480579376220703 ], { (omitted) "memory_map_size": 70098944 } ] For example, in Windows, if Groonga uses up physical memory and swap area, Groonga can't more mapping memory than that. Therefore, we can control properly memory map size by monitoring this value even if the environment does have not enough memory. ### Fixes * Fixed a bug Groonga's response may be slow when we execute request_cancel while executing a search. Especially, when the number of records of the search target is many, Groonga's response may be very slow. * Fixed a bug that string list can't be casted to int32 vector. For example, the following cast had failed. * ["10", "100"] -> [10, 100] This bug only occurs when we specify apache-arrow into input_type as the argument of load. This bug occurs in Groonga 12.0.2 or later. * Fixed a bug that Groonga Munin Plugins do not work on AlmaLinux 8 and CentOS 7. ### Known Issues * Currently, Groonga has a bug that there is possible that data is corrupt when we execute many additions, delete, and update data to vector column. * *< and *> only valid when we use query() the right side of filter condition. If we specify as below, *< and *> work as &&. * 'content @ "Groonga" *< content @ "Mroonga"' * Groonga may not return records that should match caused by GRN_II_CURSOR_SET_MIN_ENABLE. |
|
From: Horimoto Y. <hor...@cl...> - 2022-05-06 03:47:54
|
Hi, Mroonga 12.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. Document: https://mroonga.org/docs/ How to install: Install Guide https://mroonga.org/docs/install.html How to upgrade: Upgrade Guide https://mroonga.org/docs/upgrade.html Blog: https://mroonga.org/en/blog/2022/05/06/mroonga-12.03.html Changes: https://mroonga.org/docs/news.html#release-12.03 ### Changes The main changes are as follows. ### Improvements * [CentOS] Added support for Percona Server 5.7.37-40. * [CentOS] Added support for MySQL 5.7.38. * [CentOS][AlmaLinux] Added support for MySQL 8.0.29. ### Fixes * Fixed a bug that Mroonga may fail create the index on MariaDB 10.5.14. * Fixed a memory leak on full text search. This is occurred when order limit optimization is used. However, if we use MariaDB, this occurs even if we don't use order limit optimization. This bug had occurred since Mroonga 11.03. |
|
From: Horimoto Y. <hor...@cl...> - 2022-04-29 12:53:31
|
Hi, Groonga 12.0.3 has been released! https://groonga.org/docs/news.html#release-12-0-3 https://groonga.org/en/blog/2022/04/29/groonga-12.0.3.html Install: https://groonga.org/docs/install.html Characteristics: https://groonga.org/docs/characteristic.html The topics in this release: ### Improvements * [logical_count] Improved memory usage while logical_count executed. Up to now, Groonga had been keeping objects(objects are tables and columns and indexes, and so on) and temporary tables that were allocated while logical_count executed until the execution of logical_count finished. Groonga reduces reference immediately after processing a shard by this feature. Therefore, Groonga can release memory while logical_count executed. The usage of memory of Groonga may reduce because of these reasons. This improvement is only valid for the reference count mode. We can valid the reference count mode by setting GRN_ENABLE_REFERENCE_COUNT=yes. In addition, Groonga releases temporary tables dynamically while logical_count is executed by this feature. Therefore, the usage of memory of Groonga reduces. This improvement is valid even if we don't set the reference count mode. * [dump] Added support for MISSING_IGNORE/MISSING_NIL. If columns had MISSING_IGNORE/MISSING_NIL, the dump of these columns had failed until now. dump command supports these columns since this release. * [snippet],[snippet_html] Added support for text vector as input. For example, we can extract snippets of target text around search keywords against vector in JSON data as below. table_create Entries TABLE_NO_KEY column_create Entries title COLUMN_SCALAR ShortText column_create Entries contents COLUMN_VECTOR ShortText table_create Tokens TABLE_PAT_KEY ShortText --default_tokenizer TokenNgram --normalizer NormalizerNFKC130 column_create Tokens entries_title COLUMN_INDEX|WITH_POSITION Entries title column_create Tokens entries_contents COLUMN_INDEX|WITH_SECTION|WITH_POSITION Entries contents load --table Entries [ { "title": "Groonga and MySQL", "contents": [ "Groonga is a full text search engine", "MySQL is a RDBMS", "Mroonga is a MySQL storage engine based on Groonga" ] } ] select Entries\ --output_columns 'snippet_html(contents), contents'\ --match_columns 'title'\ --query Groonga [ [ 0, 0.0, 0.0 ], [ [ [ 1 ], [ [ "snippet_html", null ], [ "contents", "ShortText" ] ], [ [ "<span class=\"keyword\">Groonga</span> is a full text search engine", "Mroonga is a MySQL storage engine based on <span class=\"keyword\">Groonga</span>" ], [ "Groonga is a full text search engine", "MySQL is a RDBMS", "Mroonga is a MySQL storage engine based on Groonga" ] ] ] ] ] Until now, if we specified snippet* like --output_columns 'snippet_html(contents[1]), we could extract snippets of target text around search keywords against the vector as below. However, we didn't know which we should output elements. Because we didn't know which element was hit on search. select Entries\ --output_columns 'snippet_html(contents[0]), contents'\ --match_columns 'title'\ --query Groonga [ [ 0, 0.0, 0.0 ], [ [ [ 1 ], [ [ "snippet_html", null ], [ "contents", "ShortText" ] ], [ [ "<span class=\"keyword\">Groonga</span> is a full text search engine" ], [ "Groonga is a full text search engine", "MySQL is a RDBMS", "Mroonga is a MySQL storage engine based on Groonga" ] ] ] ] ] * [vector_join] Added a new function vector_join(). This function can concatenate each elements. We can specify delimiter in the second argument in this function. For example, we could execute snippet() and snippet_html() against vector that concatenate each elements as below. plugin_register functions/vector table_create Entries TABLE_NO_KEY column_create Entries title COLUMN_SCALAR ShortText column_create Entries contents COLUMN_VECTOR ShortText table_create Tokens TABLE_PAT_KEY ShortText --default_tokenizer TokenNgram --normalizer NormalizerNFKC130 column_create Tokens entries_title COLUMN_INDEX|WITH_POSITION Entries title column_create Tokens entries_contents COLUMN_INDEX|WITH_SECTION|WITH_POSITION Entries contents load --table Entries [ { "title": "Groonga and MySQL", "contents": [ "Groonga is a full text search engine", "MySQL is a RDBMS", "Mroonga is a MySQL storage engine based on Groonga" ] } ] select Entries\ --output_columns 'snippet_html(vector_join(contents, "\n")), contents'\ --match_columns 'title'\ --query Groonga --output_pretty yes [ [ 0, 1650849001.524027, 0.0003361701965332031 ], [ [ [ 1 ], [ [ "snippet_html", null ], [ "contents", "ShortText" ] ], [ [ "<span class=\"keyword\">Groonga</span> is a full text search engine\nMySQL is a RDBMS\nMroonga is a MySQL storage engine based on <span class=\"keyword\">Groonga</span>" ], [ "Groonga is a full text search engine","MySQL is a RDBMS","Mroonga is a MySQL storage engine based on Groonga" ] ] ] ] ] * [Indexing] Ignore too large a token like online index construction. Groonga doesn't occur error, but Groonga ignores too large a token when we execute static index construction. However, Groonga output warning in this case. ### Fixes * Fixed a bug that we may be not able to add a key to a table of patricia trie. This bug occurs in the following conditon. * If a table of patricia trie already has a key. * If the additional key is 4096 bytes. ### Known Issues * Currently, Groonga has a bug that there is possible that data is corrupt when we execute many additions, delete, and update data to vector column. * *< and *> only valid when we use query() the right side of filter condition. If we specify as below, *< and *> work as &&. * 'content @ "Groonga" *< content @ "Mroonga"' * Groonga may not return records that should match caused by GRN_II_CURSOR_SET_MIN_ENABLE. |
|
From: Horimoto Y. <hor...@cl...> - 2022-03-29 07:30:40
|
Hi, Mroonga 12.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. Document: https://mroonga.org/docs/ How to install: Install Guide https://mroonga.org/docs/install.html How to upgrade: Upgrade Guide https://mroonga.org/docs/upgrade.html Blog: https://mroonga.org/en/blog/2022/03/29/mroonga-12.02.html Changes: https://mroonga.org/docs/news.html#release-12.02 ### Changes The main changes are as follows. ### Improvements * Dropped support wrapper mode with MySQL 8.0 or later. * Added support for disabling a back trace by the server variable. We can disable a back trace by "SET GLOBAL mroonga_enable_back_trace = false;". * Added support for float32 weight vector. We can store weight as float32. We need to add WEIGHT_FLOAT32 flag when we define a column to use this feature. * [CentOS], [AlamLinux] Added support for MariaDB 10.3.34, 10.4.24, 10.5.15, 10.6.7, and 10.7.3. * [CentOS] Added support for MariaDB 10.2.43. * [CentOS], [AlamLinux] Added support for Percona Server 8.0.27-18. * Added support for MISSING_* and INVALID_* flags Please refer to https://groonga.org/docs/news.html#release-12-0-2 about details of these flags. |
|
From: Horimoto Y. <hor...@cl...> - 2022-03-29 06:43:58
|
Hi, Groonga 12.0.2 has been released! https://groonga.org/docs/news.html#release-12-0-2 https://groonga.org/en/blog/2022/03/29/groonga-12.0.2.html Install: https://groonga.org/docs/install.html Characteristics: https://groonga.org/docs/characteristic.html The topics in this release: ### Improvements * [logical_range_filter] Added support for reducing reference immediately after processing a shard. Groonga had reduced reference all shards when the finish of logical_range_filter until now. Groonga reduces reference immediately after processing a shard by this feature. The usage of memory may reduce while logical_range_filter executes by this feature. This feature is only valid for the reference count mode. We can valid the reference count mode by setting GRN_ENABLE_REFERENCE_COUNT=yes. Normally, Groonga keep objects(tables and column and index, and so on) that Groonga opened even once on memory. However, if we open many objects, Groonga uses much memory. In the reference count mode release objects that are not referenced anywhere from memory. The usage of memory of Groonga may reduce by this. * We increased the stability of the feature of recovering on crashes. This feature is experimental and it is disabled by default. Therefore, the following improvements are no influence on ordinary users. * We fixed a bug that the index was broken when Groonga crashed. * We fixed a bug that might remain a lock. * We fixed a bug that Groonga crashed while it was recovering the crash. * Improved performance for mmap if anonymous mmap available. The performance of Groonga is improved a bit by this improvement. * [Indexing] Added support for the static index construction against the following types of columns. * The non-reference vector column with weight * The reference vector column with weight * The reference scalar column These columns have not supported the static index construction until now. Therefore, the time of making the index has longed even if we set the index against these columns after we loaded data into them. By this improvement, the time of making the index is short in this case. * [column_create] Added new flags MISSING_* and INVALID_*. We added the following new flags for column_create. * MISSING_ADD * MISSING_IGNORE * MISSING_NIL * INVALID_ERROR * INVALID_WARN * INVALID_IGNORE Normally, if the data column is a reference data column and the nonexistent key is specified, a new record for the nonexistent key is newly created automatically. The behavior that Groonga adds the key automatically into the column of reference destination is useful in the search like tag search. Because Groonga adds data automatically when we load data. However, this behavior is inconvenient if we need the other data except for the key. Because a record that only has the key exists. We can change this behavior by using flags that are added in this release. * MISSING_ADD: This is the default value. This is the same behavior as the current. If the data column is a reference data column and the nonexistent key is specified, a new record for the nonexistent key is newly created automatically. * MISSING_IGNORE: If the data column is a reference data column and the nonexistent key is specified, the nonexistent key is ignored. If the reference data column is a scalar column, the value is GRN_ID_NIL. If the reference data column is a vector column, the element is just ignored as below :: ["existent1", "nonexistent", "existent2"] -> ["existent1" "existent2"] * MISSING_NIL: If the data column is a reference data column and the nonexistent key is specified, the nonexistent key in a scalar column and a vector column is treated as GRN_ID_NIL :: ["existent1", "nonexistent", "existent2"] -> ["existent1", "" (GRN_ID_NIL), "existent2"] * INVALID_ERROR: This is the default value. This is the same behavior as the current except an error response of a vector column case. If we set the invalid value (e.g.: XXX for UInt8 scalar column), the set operation is treated as an error. If the data column is a scalar column, load reports an error in log and response. If the data column is a vector column, load reports an error in log but doesn't report an error in response. This is an incompatible change. * INVALID_WARN: If we set the invalid value (e.g.: XXX for UInt8 scalar column), a warning message is logged and the set operation is ignored. If the target data column is a reference vector data column, MISSING_IGNORE and MISSING_NIL are used to determine the behavior. * INVALID_IGNORE: If we set the invalid value (e.g.: XXX for UInt8 scalar column), the set operation is ignored. If the target data column is a reference vector data column, MISSING_IGNORE and MISSING_NIL are used to determine the behavior. * [dump][column_list] Added support for MISSING_* and INVALID_* flags. These commands doesn't show MISSING_ADD and INVALID_ERROR flags to keep backward compatibility. Because these flags show the default behavior. * [schema] Added support for MISSING_* and INVALID_* flags. MISSING_AND and INVALID_ERROR flags aren't shown in flags to keep backward compatibility. However, new missing and invalid keys are added to each column. * We provided the package of Amazon Linux 2. * [Windows] Dropped support for building with Visual Studio 2017. Because we could not use windows-2016 image on GitHub Actions. ### Known Issues * Currently, Groonga has a bug that there is possible that data is corrupt when we execute many additions, delete, and update data to vector column. * *< and *> only valid when we use query() the right side of filter condition. If we specify as below, *< and *> work as &&. * 'content @ "Groonga" *< content @ "Mroonga"' * Groonga may not return records that should match caused by GRN_II_CURSOR_SET_MIN_ENABLE. |
|
From: Horimoto Y. <hor...@cl...> - 2022-03-01 03:19:53
|
Hi, Groonga 12.0.1 has been released! https://groonga.org/docs/news.html#release-12-0-1 https://groonga.org/en/blog/2022/02/28/groonga-12.0.1.html Install: https://groonga.org/docs/install.html Characteristics: https://groonga.org/docs/characteristic.html The topics in this release: ### Improvements * [query_expand] Added a support for synonym group. Until now, We had to each defined a keyword and synonyms of the keyword as below when we use the synonym search. table_create Thesaurus TABLE_PAT_KEY ShortText --normalizer NormalizerAuto # [[0, 1337566253.89858, 0.000355720520019531], true] column_create Thesaurus synonym COLUMN_VECTOR ShortText # [[0, 1337566253.89858, 0.000355720520019531], true] load --table Thesaurus [ {"_key": "mroonga", "synonym": ["mroonga", "tritonn", "groonga mysql"]}, {"_key": "groonga", "synonym": ["groonga", "senna"]} ] In the above case, if we search mroonga, Groonga search mroonga OR tritonn OR "groonga mysql" as we intended. However, if we search tritonn, Groonga search only tritonn. If we want to search tritonn OR mroonga OR "groonga mysql" even if we search tritonn, we need had added a definition as below. load --table Thesaurus [ {"_key": "tritonn", "synonym": ["tritonn", "mroonga", "groonga mysql"]}, ] In many cases, if we expand mroonga to mroonga OR tritonn OR "groonga mysql", we feel we want to expand tritonn and "groonga mysql" to mroonga OR tritonn OR "groonga mysql". However, until now, we had needed additional definitions in such a case. Therefore, if target keywords for synonyms are many, we are troublesome to define synonyms. Because we need to define many similar definitions. In addition, when we remove synonyms, we are troublesome because we need to execute remove against many records. We can make a group by deciding on a representative synonym record since this release. For example, the all following keywords are the "mroonga" group. load --table Synonyms [ {"_key": "mroonga": "representative": "mroonga"} ] load --table Synonyms [ {"_key": "tritonn": "representative": "mroonga"}, {"_key": "groonga mysql": "representative": "mroonga"} ] In this case, mroonga is expanded to mroonga OR tritonn OR "groonga mysql". In addition, tritonn and "groonga mysql" are also expanded to mroonga OR tritonn OR "groonga mysql". When we want to remove synonyms, we execute just remove against a target record. For example, if we want to remove "groonga mysql" from synonyms, we just remove {"_key": "groonga mysql": "representative": "mroonga"}. * [query_expand] Added a support for text vector and index. We can use text vector in a synonym group as below. table_create SynonymGroups TABLE_NO_KEY [[0,0.0,0.0],true] column_create SynonymGroups synonyms COLUMN_VECTOR ShortText [[0,0.0,0.0],true] table_create Synonyms TABLE_PAT_KEY ShortText [[0,0.0,0.0],true] column_create Synonyms group COLUMN_INDEX SynonymGroups synonyms [[0,0.0,0.0],true] load --table SynonymGroups [ ["synonyms"], [["rroonga", "Ruby groonga"]], [["groonga", "rroonga", "mroonga"]] ] [[0,0.0,0.0],2] query_expand Synonyms.group "rroonga" [ [ 0, 0.0, 0.0 ], "((rroonga) OR (Ruby groonga) OR (groonga) OR (rroonga) OR (mroonga))" ] * Added support for disabling a backtrace by the environment variable. We can disable output a backtrace by using GRN_BACK_TRACE_ENABLE. If we set GRN_BACK_TRACE_ENABLE=no, Groonga doesn't output a backtrace. Groonga output backtrace to a stack area. Therefore, Groonga may crash because Groonga uses up stack area depending on the OS. In such cases, we can avoid crashes by using GRN_BACK_TRACE_ENABLE=no. * [select] Improved performance for --slices. * [Windows] Added support for Visual Studio 2022. * [select] Added support for specifing max intervals for each elements in near search. For example, we can specify max intervals for each phrase in a near phrase search. We make documentation for this feature in the future. Therefore, we will make more details later. * [groonga-server-http] We could use groonga-server-http even if Groonga of RPM packages. ### Fixes * [Windows] Fixed a crash bug when Groonga output backtrace. ### Known Issues * Currently, Groonga has a bug that there is possible that data is corrupt when we execute many additions, delete, and update data to vector column. * *< and *> only valid when we use query() the right side of filter condition. If we specify as below, *< and *> work as &&. * 'content @ "Groonga" *< content @ "Mroonga"' * Groonga may not return records that should match caused by GRN_II_CURSOR_SET_MIN_ENABLE. |
|
From: Horimoto Y. <hor...@cl...> - 2022-02-10 00:50:37
|
Hi, Rroonga 12.0.0 has been released! Rroonga is the Ruby bindings for Groonga. https://ranguba.org/#about-rroonga Changes ------- Here are changes since 11.0.6: https://ranguba.org/rroonga/en/file.news.html#12-0-0 We dropped support to the package for Windows include built Groonga and Rroonga from 10.0.1. However, how to install doesn't change. About the merit of dropping support of fat gem, please refer to the following document. https://www.clear-code.com/blog/2020/9/3.html Rroonga will become to installs Groonga package for the MSYS2 automatically when installs since this version. About Rroonga ------------- Here are two important things in Rroonga. 1. Providing *Ruby-ish* API to use Groonga. 2. Providing *fast* operations like Groonga. They mean that Rroonga provides easy to use API without decreasing Groonga's speed. Install ------- % gem install rroonga Tutorial -------- There are a tutorial that uses irb: https://ranguba.org/rroonga/en/file.tutorial.html If you are a beginner, please try it. Thanks, |
|
From: Horimoto Y. <hor...@cl...> - 2022-02-10 00:32:34
|
Hi, Mroonga 12.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. Document: https://mroonga.org/docs/ How to install: Install Guide https://mroonga.org/docs/install.html How to upgrade: Upgrade Guide https://mroonga.org/docs/upgrade.html Blog: https://mroonga.org/en/blog/2022/02/09/mroonga-12.00.html Changes: https://mroonga.org/docs/news.html#release-12.00 ### Changes The main changes are as follows. ### Improvements * [Ubuntu] Added support for the latest version of mysql-server package for Ubuntu. We supported the following versions. * Ubuntu 18.04 LTS (bionic) mysql-server (5.7.37-0ubuntu0.18.04.1) * Ubuntu 20.04 LTS (focal) mysql-server (8.0.28-0ubuntu0.20.04.3) * Ubuntu 21.10 LTS (impish) mysql-server (8.0.28-0ubuntu0.21.10.3) * [CentOS] Added support for MariaDB 10.2.42, 10.3.33, 10.4.23, 10.5.14, and 10.6.6. * [AlmaLinux] Added support for MariaDB 10.3.33, 10.4.23, 10.5.14, and 10.6.6. |
|
From: Horimoto Y. <hor...@cl...> - 2022-02-09 08:32:24
|
Hi, Groonga 12.0.0 has been released! https://groonga.org/docs/news.html#release-12-0-0 https://groonga.org/en/blog/2022/02/09/groonga-12.0.0.html Install: https://groonga.org/docs/install.html Characteristics: https://groonga.org/docs/characteristic.html The topics in this release: ### Improvements * [sub_filter] Added a new option pre_filter_threshold. We can change the value of GRN_SUB_FILTER_PRE_FILTER_THRESHOLD by this option. If the number of records is less than GRN_SUB_FILTER_PRE_FILTER_THRESHOLD when Groonga executes sub_filter, Groonga execute sub_filter against records that have been already narrowed down. We can use -1 to always use this optimization. * [index_column_have_source_record] Added a new function index_column_have_source_record(). We can confirm whether a token that is existing in the index is included in any of the records that are registered in Groonga or not. Groonga does not remove a token even if the token become never used from records in Groonga by updating records. Therefore, for example, when we use the feature of autocomplete, Groonga may return a token that is not included in any of the records as candidates for search words. However, we can become that we don’t return the needless token by using this function. Because this function can detect a token that is not included in any of the records. * [NormalizerNFKC130] Added a new option strip This option removes spaces from the start and the end as below. normalize \ 'NormalizerNFKC121("strip", true, \ "report_source_offset", true)' \ " hello world\t! \t " \ WITH_CHECKS|WITH_TYPES [ [ 0, 0.0, 0.0 ], { "normalized": "hello world!", "types": [ "alpha", "alpha", "alpha", "alpha", "alpha", "others", "alpha", "alpha", "alpha", "alpha", "alpha|blank", "symbol|blank" ], "checks": [ 3, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 2 ], "offsets": [ 0, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 14 ] } ] * [select] Added new arguments drilldown_max_n_target_records and drilldown[${LABEL}].max_n_target_records. We can specify the max number of records of the drilldown target table (filtered result) to use drilldown. If the number of filtered result is larger than the specified value, some records in filtered result aren’t used for drilldown. The default value of this arguments are -1. If these arguments are set -1, Groonga uses all records for drilldown. This argument is useful when filtered result may be very large. Because a drilldown against large filtered result may be slow. We can limit the max number of records to be used for drilldown by this feature. Here is an example to limit the max number of records to be used for drilldown. The last 2 records, {\"_id\": 4, \"tag\": \"Senna\"} and {\"_id\": 5, \"tag\": \"Senna\"}, aren’t used. table_create Entries TABLE_HASH_KEY ShortText column_create Entries content COLUMN_SCALAR Text column_create Entries n_likes COLUMN_SCALAR UInt32 column_create Entries tag COLUMN_SCALAR ShortText table_create Terms TABLE_PAT_KEY ShortText --default_tokenizer TokenBigram --normalizer NormalizerAuto column_create Terms entries_key_index COLUMN_INDEX|WITH_POSITION Entries _key column_create Terms entries_content_index COLUMN_INDEX|WITH_POSITION Entries content load --table Entries [ {"_key": "The first post!", "content": "Welcome! This is my first post!", "n_likes": 5, "tag": "Hello"}, {"_key": "Groonga", "content": "I started to use Groonga. It's very fast!", "n_likes": 10, "tag": "Groonga"}, {"_key": "Mroonga", "content": "I also started to use Mroonga. It's also very fast! Really fast!", "n_likes": 15, "tag": "Groonga"}, {"_key": "Good-bye Senna", "content": "I migrated all Senna system!", "n_likes": 3, "tag": "Senna"}, {"_key": "Good-bye Tritonn", "content": "I also migrated all Tritonn system!", "n_likes": 3, "tag": "Senna"} ] select Entries \ --limit -1 \ --output_columns _id,tag \ --drilldown tag \ --drilldown_max_n_target_records 3 [ [ 0, 1337566253.89858, 0.000355720520019531 ], [ [ [ 5 ], [ [ "_id", "UInt32" ], [ "tag", "ShortText" ] ], [ 1, "Hello" ], [ 2, "Groonga" ], [ 3, "Groonga" ], [ 4, "Senna" ], [ 5, "Senna" ] ], [ [ 2 ], [ [ "_key", "ShortText" ], [ "_nsubrecs", "Int32" ] ], [ "Hello", 1 ], [ "Groonga", 2 ] ] ] ] * [httpd] Updated bundled nginx to 1.21.6. |
|
From: Josep S. <jos...@sa...> - 2022-02-01 21:14:03
|
Hi Horimoto Yasuhiro. I confirm that the arrow-lib package has been updated successfully. Thanks by your great work!!! Josep. -- Josep Sanz Campderrós https://www.josepsanz.net The SaltOS project https://www.saltos.org El 2022-01-26 01:49:48, Horimoto Yasuhiro escribió: > Hello Josep Sanz, > > I'm sorry for the late response. > We resolved this problem. > > We think that this problem is resolved by the next release(Groonga > 11.1.2). > However, if arrow-libs update a major version, this problem reproduces. > In this case, we will handle that by rebuilding the Groonga package. > > Best Regards, > > From: Josep Sanz <jos...@sa...> > Subject: [groonga-talk:542] Re: [ANN] Mroonga 11.10 > Date: Fri, 3 Dec 2021 10:36:48 +0100 > >> Hi Horimoto Yasuhiro. >> >> Thanks by your response. >> >> I'm can wait without problem!!! >> >> Thanks in advance. >> >> Josep. >> >> -- >> Josep Sanz Campderrós >> http://www.josepsanz.net >> The SaltOS project >> http://www.saltos.org >> >> El 2021-12-03 10:12:34, Horimoto Yasuhiro >> escribió: >> >>> Hello, >>> >>> Thank you for your report. >>> We were able to reproduce this problem in our >> environment. >>> >>> Probably, we need to update the Groonga package >> for CentOS to resolve >>> this problem. >>> We fixing this problem now. >>> Could you please wait for a few days? >>> >>> Best Regards, >>> >>> From: Josep Sanz <jos...@sa...> >>> Subject: [groonga-talk:540] Re: [ANN] Mroonga >> 11.10 >>> Date: Wed, 1 Dec 2021 15:59:03 +0100 >>> >>>> Hi team. >>>> >>>> I get this error when I try to do an update in >>>> centos 7: >>>> >>>> --> Running transaction check >>>> ---> Package arrow-libs.x86_64 0:6.0.0-1.el7 >> will >>>> be updated >>>> --> Processing Dependency: arrow-libs = 6.0.0 >> for >>>> package: >>>> groonga-libs-11.1.0-1.el7.x86_64 >>>> ---> Package arrow-libs.x86_64 0:6.0.1-1.el7 >> will >>>> be an update >>>> --> Finished Dependency Resolution >>>> Error: Package: >> groonga-libs-11.1.0-1.el7.x86_64 >>>> (@groonga-centos) >>>> Requires: arrow-libs = 6.0.0 >>>> Removing: arrow-libs-6.0.0-1.el7.x86_64 >>>> (@groonga-centos) >>>> arrow-libs = 6.0.0-1.el7 >>>> Updated By: >>>> arrow-libs-6.0.1-1.el7.x86_64 (groonga-centos) >>>> arrow-libs = 6.0.1-1.el7 >>>> Available: >>>> arrow-libs-0.3.1.20170506-1.el7.centos.x86_64 >>>> (groonga-centos) >>>> arrow-libs = >>>> 0.3.1.20170506-1.el7.centos >>>> Available: >>>> arrow-libs-0.3.1.20170508-1.el7.centos.x86_64 >>>> (groonga-centos) >>>> arrow-libs = >>>> 0.3.1.20170508-1.el7.centos >>>> Available: >>>> arrow-libs-0.3.1.20170510-1.el7.centos.x86_64 >>>> (groonga-centos) >>>> arrow-libs = >>>> 0.3.1.20170510-1.el7.centos >>>> Available: >>>> arrow-libs-0.3.1.20170512-1.el7.centos.x86_64 >>>> (groonga-centos) >>>> arrow-libs = >>>> 0.3.1.20170512-1.el7.centos >>>> Available: >>>> arrow-libs-0.3.1.20170517-1.el7.centos.x86_64 >>>> (groonga-centos) >>>> arrow-libs = >>>> 0.3.1.20170517-1.el7.centos >>>> Available: >>>> arrow-libs-0.4.1.20170524-1.el7.centos.x86_64 >>>> (groonga-centos) >>>> arrow-libs = >>>> 0.4.1.20170524-1.el7.centos >>>> Available: >>>> arrow-libs-0.5.0.20170612-1.el7.centos.x86_64 >>>> (groonga-centos) >>>> arrow-libs = >>>> 0.5.0.20170612-1.el7.centos >>>> Available: >>>> arrow-libs-0.6.0.20170726-1.el7.centos.x86_64 >>>> (groonga-centos) >>>> arrow-libs = >>>> 0.6.0.20170726-1.el7.centos >>>> Available: >>>> arrow-libs-2.0.0-1.el7.x86_64 (groonga-centos) >>>> arrow-libs = 2.0.0-1.el7 >>>> Available: >>>> arrow-libs-3.0.0-1.el7.x86_64 (groonga-centos) >>>> arrow-libs = 3.0.0-1.el7 >>>> Available: >>>> arrow-libs-4.0.0-1.el7.x86_64 (groonga-centos) >>>> arrow-libs = 4.0.0-1.el7 >>>> Available: >>>> arrow-libs-4.0.1-1.el7.x86_64 (groonga-centos) >>>> arrow-libs = 4.0.1-1.el7 >>>> Available: >>>> arrow-libs-5.0.0-1.el7.x86_64 (groonga-centos) >>>> arrow-libs = 5.0.0-1.el7 >>>> >>>> The solution for me was use the "yum update >>>> --exclude arrow-libs", but I >>>> think that the new mroonga package should use >> the >>>> latest arrow-libs??? >>>> >>>> It's true my conjecture??? >>>> >>>> Thanks in advance. >>>> >>>> Josep. >>>> >>>> -- >>>> Josep Sanz Campderrós >>>> http://www.josepsanz.net >>>> The SaltOS project >>>> http://www.saltos.org >>>> >>>> El 2021-11-30 05:45:24, Horimoto Yasuhiro >>>> escribió: >>>> >>>>> Hi, >>>>> >>>>> Mroonga 11.10 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. >>>>> >>>>> Document: >>>>> https://mroonga.org/docs/ >>>>> >>>>> How to install: Install Guide >>>>> https://mroonga.org/docs/install.html >>>>> >>>>> How to upgrade: Upgrade Guide >>>>> https://mroonga.org/docs/upgrade.html >>>>> >>>>> Blog: >>>>> >>>> >> https://mroonga.org/en/blog/2021/11/29/mroonga-11.10.html >>>>> >>>>> Changes: >>>>> >> https://mroonga.org/docs/news.html#release-11.10 >>>>> >>>>> ### Improvements >>>>> >>>>> * [AlamLinux] Added support for Mroonga on >>>> AlamLinux 8. >>>>> >>>>> * [AlamLinux] Added support for MySQL 8.0.27. >>>>> >>>>> * There are below restrictions in the MySQL >> 8.0 >>>> package. >>>>> >>>>> * [Wrapper mode] Wrapper mode is not supported >>>> yet. >>>>> >>>>> * [Storage mode] Storage mode does not support >>>> the following >>>>> feature. >>>>> >>>>> * The feature of relevant to the optimization. >>>>> >>>>> * [AlamLinux] Added support for Percona Server >>>> 8.0.26. >>>>> >>>>> * [AlamLinux] Added support for MariaDB >> 10.3.32, >>>> 10.4.22, 10.5.13, and >>>>> 10.6.5. >>>>> >>>>> * [CentOS] Added support for MariaDB 10.2.41, >>>> 10.3.32, 10.4.22, 10.5.13, >>>>> and 10.6.5. >>>>> >>>>> * [Ubuntu] Added support for MySQL 8.0 on >> Ubuntu >>>> 21.04 (Hirsute Hippo) >>>>> and 21.10 (Impish Indri). >>>>> >>>>> * There are below restrictions in the MySQL >> 8.0 >>>> package. >>>>> >>>>> * [Wrapper mode] Wrapper mode is not supported >>>> yet. >>>>> >>>>> * [Storage mode] Storage mode does not support >>>> the following >>>>> feature. >>>>> >>>>> * The feature of relevant to the optimization. >>>>> >>>>> ### Fixes >>>>> >>>>> * [CentOS] Fixed a bug that we have not >> provided >>>> the package of Mroonga >>>>> for MariaDB 10.6. >>>>> >>>>> * [Optimizations] Fixed a bug that Mroonga >> apply >>>> the optimization of row >>>>> count wrongly. >>>>> >>>>> Normally, Mroonga apply the optimization of >> row >>>> count >>>>> when the SELECT fetches only COUNT(*) and >>>> condition >>>>> in WHERE can be processed only by index. >>>>> >>>>> However, Mroonga applied the optimization of >> row >>>> count >>>>> even if Mroonga couldn't process condition in >>>> WHERE only by index as >>>>> below case >>>>> by this bug. >>>>> >>>>> Consequently, the result of SELECT COUNT(*) >>>> WHERE ... is wrong. >>>>> >>>>> CREATE TABLE roles ( >>>>> id INT >>>>> ); >>>>> >>>>> INSERT INTO roles VALUES (1), (2), (3), (4), >>>> (5); >>>>> >>>>> CREATE TABLE users ( >>>>> id INT, >>>>> role_id INT, >>>>> INDEX (role_id) >>>>> ); >>>>> >>>>> INSERT INTO users VALUES (10, 1); >>>>> INSERT INTO users VALUES (11, 2); >>>>> INSERT INTO users VALUES (13, 3); >>>>> INSERT INTO users VALUES (14, 4); >>>>> INSERT INTO users VALUES (15, 5); >>>>> INSERT INTO users VALUES (20, 1); >>>>> INSERT INTO users VALUES (21, 2); >>>>> INSERT INTO users VALUES (23, 3); >>>>> INSERT INTO users VALUES (24, 4); >>>>> INSERT INTO users VALUES (25, 5); >>>>> >>>>> SELECT COUNT(*) >>>>> FROM ( >>>>> SELECT roles.id >>>>> FROM roles >>>>> LEFT JOIN users ON users.id <= 100 AND >>>>> users.role_id = roles.id >>>>> ) roles_users; >>>>> >>>>> * Fixed a bug that Mroonga doesn't set proper >>>> encoding >>>>> on condition push down for 'STRING_FIELD ='. >>>>> >>>>> Mroonga executes condition push down for >>>> 'STRING_FIELD =' in the >>>>> following case. >>>>> However, Mroonga doesn't set proper encoding >> in >>>> search keywords at this >>>>> time. >>>>> Consequently, Mroonga fails to normalize >> search >>>> keywords. >>>>> >>>>> CREATE TABLE memos ( >>>>> id INT PRIMARY KEY, >>>>> title TEXT, >>>>> INDEX (title) >>>>> ) ENGINE=Mroonga DEFAULT CHARSET=utf8mb4; >>>>> >>>>> INSERT INTO memos VALUES (1, 'Groonga'); >>>>> INSERT INTO memos VALUES (2, 'Mroonga'); >>>>> >>>>> SELECT * >>>>> FROM memos >>>>> WHERE title = 'mroonga' >>>>> ORDER BY id; >>>>> >>>>> >> _______________________________________________ >>>>> groonga-talk mailing list >>>>> gro...@li... >>>>> >>>> >> https://lists.sourceforge.net/lists/listinfo/groonga-talk >>>> >>> >>> _______________________________________________ >>> groonga-talk mailing list >>> gro...@li... >>> >> https://lists.sourceforge.net/lists/listinfo/groonga-talk >> > > _______________________________________________ > groonga-talk mailing list > gro...@li... > https://lists.sourceforge.net/lists/listinfo/groonga-talk |
|
From: Horimoto Y. <hor...@cl...> - 2022-02-01 00:17:03
|
Hi, Mroonga 11.13 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. Document: https://mroonga.org/docs/ How to install: Install Guide https://mroonga.org/docs/install.html How to upgrade: Upgrade Guide https://mroonga.org/docs/upgrade.html Blog: https://mroonga.org/en/blog/2022/01/29/mroonga-11.13.html Changes: https://mroonga.org/docs/news.html#release-11.13 ### Changes The main changes are as follows. ### Improvements * [CentOS] Added support for MySQL 5.7.37. * [CentOS]、[AlmaLinux] Added support for MySQL 8.0.28. There are below restrictions in the MySQL 8.0 package. * [Wrapper mode] Wrapper mode is not supported yet. * [Storage mode] Storage mode does not support the following feature. * The functions related to optimization. * [CentOS]、[AlmaLinux] Added support for Percona Server 8.0.26-17. |
|
From: Horimoto Y. <hor...@cl...> - 2022-02-01 00:07:29
|
Hi, Groonga 11.1.3 has been released! https://groonga.org/docs/news.html#release-11-1-3 https://groonga.org/en/blog/2022/01/29/groonga-11.1.3.html Install: https://groonga.org/docs/install.html Characteristics: https://groonga.org/docs/characteristic.html The topics in this release: ### Improvements * [snippet] Added support for using the keyword of 32 or more. We could not specify the keyword of 32 or more with snippet until now. However, we can specify the keyword of 32 or more by this improvement as below. table_create Entries TABLE_NO_KEY column_create Entries content COLUMN_SCALAR ShortText load --table Entries [ {"content": "Groonga is a fast and accurate full text search engine based on inverted index. One of the characteristics of Groonga is that a newly registered document instantly appears in search results. Also, Groonga allows updates without read locks. These characteristics result in superior performance on real-time applications.\nGroonga is also a column-oriented database management system (DBMS). Compared with well-known row-oriented systems, such as MySQL and PostgreSQL, column-oriented systems are more suited for aggregate queries. Due to this advantage, Groonga can cover weakness of row-oriented systems.\nThe basic functions of Groonga are provided in a C library. Also, libraries for using Groonga in other languages, such as Ruby, are provided by related projects. In addition, groonga-based storage engines are provided for MySQL and PostgreSQL. These libraries and storage engines allow any application to use Groonga. See usage examples."}, {"content": "In widely used DBMSs, updates are immediately processed, for example, a newly registered record appears in the result of the next query. In contrast, some full text search engines do not support instant updates, because it is difficult to dynamically update inverted indexes, the underlying data structure.\nGroonga also uses inverted indexes but supports instant updates. In addition, Groonga allows you to search documents even when updating the document collection. Due to these superior characteristics, Groonga is very flexible as a full text search engine. Also, Groonga always shows good performance because it divides a large task, inverted index merging, into smaller tasks."} ] select Entries \ --output_columns ' \ snippet(content, \ "groonga", "inverted", "index", "fast", "full", "text", "search", "engine", "registered", "document", \ "results", "appears", "also", "system", "libraries", "for", "mysql", "postgresql", "column-oriented", "dbms", \ "basic", "ruby", "projects", "storage", "allow", "application", "usage", "sql", "well-known", "real-time", \ "weakness", "merging", "performance", "superior", "large", "dynamically", "difficult", "query", "examples", "divides", \ { \ "default_open_tag": "[", \ "default_close_tag": "]", \ "width" : 2048 \ })' [ [ 0, 1643165838.691991, 0.0003311634063720703 ], [ [ [ 2 ], [ [ "snippet", null ] ], [ [ "[Groonga] is a [fast] and accurate [full] [text] [search] [engine] based on [inverted] [index]. One of the characteristics of [Groonga] is that a newly [registered] [document] instantly [appears] in [search] [results]. [Also], [Groonga] [allow]s updates without read locks. These characteristics result in [superior] [performance] on [real-time] [application]s.\n[Groonga] is [also] a [column-oriented] database management [system] ([DBMS]). Compared with [well-known] row-oriented [system]s, such as [MySQL] and [PostgreSQL], [column-oriented] [system]s are more suited [for] aggregate queries. Due to this advantage, [Groonga] can cover [weakness] of row-oriented [system]s.\nThe [basic] functions of [Groonga] are provided in a C library. [Also], [libraries] [for] using [Groonga] in other languages, such as [Ruby], are provided by related [projects]. In addition, [groonga]-based [storage] [engine]s are provided [for] [MySQL] and [PostgreSQL]. These [libraries] and [storage] [engine]s [allow] any [application] to use [Groonga]. See [usage] [examples]." ] ], [ [ "In widely used [DBMS]s, updates are immediately processed, [for] example, a newly [registered] record [appears] in the result of the next [query]. In contrast, some [full] [text] [search] [engine]s do not support instant updates, because it is [difficult] to [dynamically] update [inverted] [index]es, the underlying data structure.\n[Groonga] [also] uses [inverted] [index]es but supports instant updates. In addition, [Groonga] [allow]s you to [search] [document]s even when updating the [document] collection. Due to these [superior] characteristics, [Groonga] is very flexible as a [full] [text] [search] [engine]. [Also], [Groonga] always shows good [performance] because it [divides] a [large] task, [inverted] [index] [merging], into smaller tasks." ] ] ] ] ] * [NormalizerNFKC130] Added a new option remove_symbol. This option removes symbols (e.g. #, !, “, &, %, …) from the string that the target of normalizing as below. normalize 'NormalizerNFKC130("remove_symbol", true)' "#This & is %% a pen." WITH_TYPES [ [ 0, 1643595008.729597, 0.0005540847778320312 ], { "normalized": "this is a pen", "types": [ "alpha", "alpha", "alpha", "alpha", "others", "others", "alpha", "alpha", "others", "others", "alpha", "others", "alpha", "alpha", "alpha" ], "checks": [ ] } ] * [AlmaLinux] Added support for AlmaLinux 8 on ARM64. * [httpd] Updated bundled nginx to 1.21.5. * [Documentation] Fixed a typo in ruby_eval. * [Ubuntu] Dropped Ubuntu 21.04 (Hirsute Hippo) support. Because Ubuntu 21.04 reached EOL January 20, 2022. ### Fixes * [load] Fixed a crash bug when we load data with specifying a nonexistent column. This bug only occurs when we specify apache-arrow into input_type as the argument of load. * Fixed a bug that the version up of Groonga failed Because the version up of arrow-libs on which Groonga depends. However, if arrow-libs update a major version, this problem reproduces. In this case, we will handle that by rebuilding the Groonga package. ### Known Issues * Currently, Groonga has a bug that there is possible that data is corrupt when we execute many additions, delete, and update data to vector column. * *< and *> only valid when we use query() the right side of filter condition. If we specify as below, *< and *> work as &&. * 'content @ "Groonga" *< content @ "Mroonga"' * Groonga may not return records that should match caused by GRN_II_CURSOR_SET_MIN_ENABLE. |