Groonga 12.0.7 has been released
Groonga 12.0.7 has been released!
How to install: Install
Here are important changes in this release:
Added a new function
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.)
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,
--limitis 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
THRESHOLDrecords. 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_Nis a positive number such as 0 and 29.
CONDITION_Nis a string that uses script_syntax such as
number_column > 29.
If the current result set has less than or equal to
THRESHOLD_1records, the corresponding
CONDITION_1is executed. Similarly, if the next result set has less than or equal to
THRESHOLD_2records, the corresponding
CONDITION_2is executed. If the next result set has greater than
escalate()function is finished.
CONDITIONs are executed,
escalate(THRESHOLD_1, CONDITION_1, ..., THRESHOLD_N, CONDITION_N)is same as
CONDITION_1 || ... || CONDITION_N.
escalate()function can be worked with logical operators such as
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
Fixed a bug Groonga's response may be slow when we execute the
request_cancelwhile 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.
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.
*>only valid when we use
query()the right side of filter condition. If we specify as below,
'content @ "Groonga" *< content @ "Mroonga"'
Groonga may not return records that should match caused by
Please refert to the following news for more details.
Let's search by Groonga!