Added support for lexicon_flags parameter.

• We can add KEY_LARGE flag to a USING HASH (non full-text search index) index as below by this parameter.

  CREATE TABLE memos (
    id INT UNSIGNED PRIMARY KEY,
    title VARCHAR(64) NOT NULL,
    UNIQUE INDEX (title) USING HASH COMMENT 'lexicon_flags "KEY_LARGE"'
  ) DEFAULT CHARSET=utf8mb4;
  

[CentOS] Added support for MySQL 5.6.51, 5.7.33, and 8.0.23.

• There are below restrictions in the MySQL 8.0 package.

  • [Wrapper mode] Wrapper mode is not supported yet.

  • [Storage mode] JSON data type is not supported yet.

[Storage mode] Added support for customize table flags. [Gitter][Reported by Shinichi Takayanagi]

• Until now, we can’t customize table flags in storage mode.

• We can customize table flags as below since this release.

  CREATE TABLE terms (
    term VARCHAR(64) NOT NULL PRIMARY KEY
  ) COMMENT='flags "TABLE_HASH_KEY|KEY_LARGE"'
    DEFAULT CHARSET=utf8mb4;
  

• Please refer to the following URL about customizable items.

  • https://groonga.org/ja/docs/reference/commands/table_create.html#flags

[Ubuntu] Added support for Ubuntu 20.10 (Groovy Gorilla).

[CentOS] Added support for Percona Server 8.0.22.

[CentOS] Added support for MariaDB 10.2.36, 10.3.27, 10.4.17, and 10.5.8

[CentOS] Added support for Percona Server 5.6.50, 5.7.32, and 8.0.21.

[CentOS] Added support for MySQL 5.6.50, 5.7.32, and 8.0.22.

• There are below restrictions in the MySQL 8.0 package.

  • [Wrapper mode] Wrapper mode is not supported yet.

  • [Storage mode] JSON data type is not supported yet.

Dropped support for MariaDB 10.1 except Ubuntu 18.04 LTS.

• Because MariaDB 10.1 is EOL.

• However, we have only supported MariaDB 10.1 for Ubintu 18.04 LTS

  • Because MariaDB 10.1 has supported yet on it.

Dropped support for CentOS 6.

• Because CentOS 6 is EOL.

[mroonga_snippet_html()] Added support for customizing normalizer.

• We can use custom normalizer instead of the default normalizer(NromalizerAuto) by using table_name and index_name.

  • We specify target table name to table_name as below.

  • We specify index name that is specified on target table to index_name as below.

  SET NAMES utf8mb4;
  
  CREATE TABLE memos (
  content text,
  fulltext index content_index (content)
  COMMENT 'normalizer "NormalizerNFKC121(\'unify_kana\', true)"'
  ) DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
  
  SELECT mroonga_snippet_html('This is Mroonga（ムルンガ）.',
  'memos' as table_name,
  'content_index' as index_name,
  'むるんが') as snippet;
  
  snippet
  <div class="snippet">This is Mroonga（<span class="keyword">ムルンガ</span>）.</div>
  

  • We can also use mixing search by query and search by keywords by this modification.

  • For example as below, we can highlight keywords that we both specify by AS query and AS snippet.

    SET NAMES utf8mb4;
    SELECT mroonga_snippet_html('Mroonga has two running modes.
    
    One is “storage mode”, that is the default mode, and we use Groonga for both storing data and searching. With this mode, you can have full benefits of Groonga described above, like fast data update, lock-free full text search and geolocation search. But it does not support transactions.
    
    Another one is “wrapper mode”, that adds full text search function on other storage engines like MyISAM or InnoDB. With this mode, you can use Groonga’s fast full text search with having the benefits of the storage engine, ex. transaction in InnoDB. But you cannot have benefits from Groonga’s read-lock free characteristic. And you might have the performance bottle neck in the storage engine in updating data.',
    'lock storage' AS query,
    'update' AS snippet;
    
    snippet
    <div class="snippet"><span class="keyword">storage</span> mode”, that is the default mode, and we use Groonga for both storing data and searching. With this mode, you can have full benefits of Groonga described above, like fast data <span class="keyword">update</span>, <span class="keyword">lock</span>-fr</div><div class="snippet">text search function on other <span class="keyword">storage</span> engines like MyISAM or InnoDB. With this mode, you can use Groonga’s fast full text search with having the benefits of the <span class="keyword">storage</span> engine, ex. transaction in In</div><div class="snippet">noDB. But you cannot have benefits from Groonga’s read-<span class="keyword">lock</span> free characteristic. And you might have the performance bottle neck in the <span class="keyword">storage</span> engine in updating data.</div>
    

Added support for WITH_WEIGHT column flag.

• This flag require Groonga 10.0.2 or later.

• We can insert vector with weight as below by this flag.

  CREATE TABLE tags (
    name VARCHAR(64) PRIMARY KEY
  ) DEFAULT CHARSET=utf8mb4;
  
  CREATE TABLE bugs (
    tags TEXT COMMENT 'flags "COLUMN_VECTOR|WITH_WEIGHT", type "tags"',
    FULLTEXT INDEX bugs_tags (tags) COMMENT 'table "tags", flags "WITH_WEIGHT"'
  ) DEFAULT CHARSET=utf8mb4;
  
  INSERT INTO bugs VALUES ('{"package": 100, "priority": 5}');
  

Dropped support for MariaDB 5.5 in CentOS7.

[CentOS] Added support for MySQL 5.6.48, 5.7.30, 8.0.20