Groonga 11.1.0 has been released
Groonga 11.1.0 has been released!
How to install: Install
Changes
Here are important changes in this release:
Improvements
-
load Added support for ISO 8601 time format.
loadsupport the following format by this modification.- YYYY-MM-ddThh:mm:ss.sZ
- YYYY-MM-ddThh:mm:ss.s+10:00
- YYYY-MM-ddThh:mm:ss.s-10:00
We can also use
tandzcharacters instead ofTandZin this syntax. We can also use/character instead of-in this syntax. However, note that this is not an ISO 8601 format. This format is present for compatibility. -
select Added a new
query_flagsDISABLE_PREFIX_SEARCH.We can use the prefix search operators
^and*as search keywords byDISABLE_PREFIX_SEARCHas below.This feature is useful if we want to search documents including
^and*.table_create Users TABLE_PAT_KEY ShortText load --table Users [ {"_key": "alice"}, {"_key": "alan"}, {"_key": "ba*"} ] select Users \ --match_columns "_key" \ --query "a*" \ --query_flags "DISABLE_PREFIX_SEARCH" [[0,0.0,0.0],[[[1],[["_id","UInt32"],["_key","ShortText"]],[3,"ba*"]]]]table_create Users TABLE_PAT_KEY ShortText load --table Users [ {"_key": "alice"}, {"_key": "alan"}, {"_key": "^a"} ] select Users \ --query "_key:^a" \ --query_flags "ALLOW_COLUMN|DISABLE_PREFIX_SEARCH" [[0,0.0,0.0],[[[1],[["_id","UInt32"],["_key","ShortText"]],[3,"^a"]]]] -
select Added a new
query_flagsDISABLE_AND_NOT.We can use
AND NOToperators-as search keywords byDISABLE_AND_NOTas below.This feature is useful if we want to search documents including
-.table_create Users TABLE_PAT_KEY ShortText load --table Users [ {"_key": "alice"}, {"_key": "bob"}, {"_key": "cab-"} ] select Users --match_columns "_key" --query "b - a" --query_flags "DISABLE_AND_NOT" [[0,0.0,0.0],[[[1],[["_id","UInt32"],["_key","ShortText"]],[3,"cab-"]]]]
Fixes
- [The browser based administration tool] Fixed a bug that a search query that is inputted to non-administration mode is sent even if we input checks to the checkbox for the administration mode of a record list.
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 usequery()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.
Conclusion
Please refert to the following news for more details.
Let's search by Groonga!