null+****@clear*****
null+****@clear*****
2012年 1月 25日 (水) 21:41:20 JST
Kouhei Sutou 2012-01-25 21:41:20 +0900 (Wed, 25 Jan 2012)
New Revision: c604b2e1848f7a1312ce143181d59e7a0ed42fcd
Log:
[doc] groonga -> mroonga.
Modified files:
doc/source/conf.py
doc/source/reference.rst
doc/source/userguide.rst
doc/source/userguide/storage.rst
doc/source/userguide/wrapper.rst
Modified: doc/source/conf.py (+2 -2)
===================================================================
--- doc/source/conf.py 2012-01-25 21:35:48 +0900 (6c1a7ea)
+++ doc/source/conf.py 2012-01-25 21:41:20 +0900 (4f61712)
@@ -42,7 +42,7 @@ master_doc = 'index'
# General information about the project.
project = u'mroonga'
-copyright = u'2009-' + unicode(datetime.today().year) + u', groonga project'
+copyright = u'2009-' + unicode(datetime.today().year) + u', mroonga project'
# The version info for the project you're documenting, acts as replacement for
# |version| and |release|, also used in various other places throughout the
@@ -206,7 +206,7 @@ htmlhelp_basename = 'mroongadoc'
# (source start file, target name, title, author, documentclass [howto/manual]).
latex_documents = [
('index', 'mroonga.tex', u'mroonga Documentation',
- u'groonga project', 'manual'),
+ u'mroonga project', 'manual'),
]
# The name of an image file (relative to this directory) to place at the top of
Modified: doc/source/reference.rst (+30 -30)
===================================================================
--- doc/source/reference.rst 2012-01-25 21:35:48 +0900 (4986e46)
+++ doc/source/reference.rst 2012-01-25 21:41:20 +0900 (6188323)
@@ -9,7 +9,7 @@ List of available SQL commands
* ``ALTER TABLE table_name ADD COLUMN column_name TEXT``
* ``ALTER TABLE table_name ADD FULLTEXT INDEX index_name (column_name)``
* ``ALTER TABLE table_name ADD SPATIAL KEY index_name (geometry_column_name)``
-* ``ALTER TABLE table_name ENGINE = groonga``
+* ``ALTER TABLE table_name ENGINE = mroonga``
* ``ALTER TABLE table_name RENAME new_table_name``
* ``COMMIT``
* ``CREATE FULLTEXT INDEX index_name ON table_name(column_name)``
@@ -23,8 +23,8 @@ List of available SQL commands
* ``CREATE TABLE table_name (... INDEX USING BTREE (column_name))``
* ``CREATE TABLE table_name (... PRIMARY KEY (column_name))``
* ``CREATE TABLE table_name (...) CAHRSET UTF8``
-* ``CREATE TABLE table_name (...) ENGINE=groonga COMMENT = 'ENGINE "InnoDB"'``
-* ``CREATE TABLE table_name (...) ENGINE=groonga``
+* ``CREATE TABLE table_name (...) ENGINE=mroonga COMMENT = 'ENGINE "InnoDB"'``
+* ``CREATE TABLE table_name (...) ENGINE=mroonga``
* ``CREATE TABLE table_name (\`_id\` INT)``
* ``CREATE TABLE table_name (\`_id\` INT, KEY(_id) USING HASH)``
* ``CREATE TABLE table_name (column_name BIGINT)``
@@ -69,7 +69,7 @@ List of available SQL commands
* ``INSERT INTO ... VALUES ...``
* ``INSERT INTO table_name (column_name, ...) SELECT ... FROM other_table_name``
* ``REPLACE INTO table_name SELECT ... FROM other_table_name ...``
-* ``SELECT * FROM information_schema.plugins WHERE plugin_name = "groonga"``
+* ``SELECT * FROM information_schema.plugins WHERE plugin_name = "mroonga"``
* ``SELECT * FROM table_name FORCE INDEX(index_name) WHERE ...``
* ``SELECT * FROM table_name ORDER BY column_name ASC LIMIT ...``
* ``SELECT * FROM table_name ORDER BY column_name ASC``
@@ -119,7 +119,7 @@ List of server variables
Here are the explanations of server variables that are introduced by mroonga.
-groonga_default_parser
+mroonga_default_parser
^^^^^^^^^^^^^^^^^^^^^^
The default parser of the full text search.
@@ -130,7 +130,7 @@ Here is an example to use ``TokenBigramSplitSymbolAlphaDigit`` as a fulltext sea
.. code-block:: sql
:linenos:
- SET GLOBAL groonga_default_parser=TokenBigramSplitSymbolAlphaDigit;
+ SET GLOBAL mroonga_default_parser=TokenBigramSplitSymbolAlphaDigit;
CREATE TABLE diaries (
id INT PRIMARY KEY AUTO_INCREMENT,
body TEXT,
@@ -138,86 +138,86 @@ Here is an example to use ``TokenBigramSplitSymbolAlphaDigit`` as a fulltext sea
) DEFAULT CHARSET UTF8;
-groonga_libgroonga_version
+mroonga_libgroonga_version
^^^^^^^^^^^^^^^^^^^^^^^^^^
The version string of the groonga library.
Here is an example SQL to confirm the using groonga library version::
- mysql> SHOW VARIABLES LIKE 'groonga_libgroonga_version';
+ mysql> SHOW VARIABLES LIKE 'mroonga_libgroonga_version';
+----------------------------+------------------+
| Variable_name | Value |
+----------------------------+------------------+
- | groonga_libgroonga_version | 1.2.8-9-gbf05b82 |
+ | mroonga_libgroonga_version | 1.2.8-9-gbf05b82 |
+----------------------------+------------------+
1 row in set (0.00 sec)
-groonga_log_file
+mroonga_log_file
^^^^^^^^^^^^^^^^
The path of the log file of mroonga. The default value is ``groonga.log``.
Here is an example transcript to change log file to ``/tmp/mroonga.log``::
- mysql> SHOW VARIABLES LIKE 'groonga_log_file';
+ mysql> SHOW VARIABLES LIKE 'mroonga_log_file';
+------------------+-------------+
| Variable_name | Value |
+------------------+-------------+
- | groonga_log_file | groonga.log |
+ | mroonga_log_file | groonga.log |
+------------------+-------------+
1 row in set (0.00 sec)
- mysql> SET GLOBAL groonga_log_file = "/tmp/mroonga.log";
+ mysql> SET GLOBAL mroonga_log_file = "/tmp/mroonga.log";
Query OK, 0 rows affected (0.00 sec)
- mysql> SHOW VARIABLES LIKE 'groonga_log_file';
+ mysql> SHOW VARIABLES LIKE 'mroonga_log_file';
+------------------+------------------+
| Variable_name | Value |
+------------------+------------------+
- | groonga_log_file | /tmp/mroonga.log |
+ | mroonga_log_file | /tmp/mroonga.log |
+------------------+------------------+
1 row in set (0.00 sec)
-groonga_log_level
+mroonga_log_level
^^^^^^^^^^^^^^^^^
The output level of mroonga log file. The default value is ``NOTICE``.
Here is an example transcript to change log level to ``DEBUG`` that logs many messages for debugging::
- mysql> SHOW VARIABLES LIKE 'groonga_log_level';
+ mysql> SHOW VARIABLES LIKE 'mroonga_log_level';
+-------------------+--------+
| Variable_name | Value |
+-------------------+--------+
- | groonga_log_level | NOTICE |
+ | mroonga_log_level | NOTICE |
+-------------------+--------+
1 row in set (0.00 sec)
- mysql> SET GLOBAL groonga_log_level = "debug";
+ mysql> SET GLOBAL mroonga_log_level = "debug";
Query OK, 0 rows affected (0.00 sec)
- mysql> SHOW VARIABLES LIKE 'groonga_log_level';
+ mysql> SHOW VARIABLES LIKE 'mroonga_log_level';
+-------------------+-------+
| Variable_name | Value |
+-------------------+-------+
- | groonga_log_level | DEBUG |
+ | mroonga_log_level | DEBUG |
+-------------------+-------+
1 row in set (0.00 sec)
-groonga_version
+mroonga_version
^^^^^^^^^^^^^^^
The version string of mroonga.
Here is an example SQL to confirm the running mroonga version::
- mysql> SHOW VARIABLES LIKE 'groonga_version';
+ mysql> SHOW VARIABLES LIKE 'mroonga_version';
+-----------------+-------+
| Variable_name | Value |
+-----------------+-------+
- | groonga_version | 1.10 |
+ | mroonga_version | 1.10 |
+-----------------+-------+
1 row in set (0.00 sec)
@@ -226,7 +226,7 @@ List of status variables
Here are the explanations of status variables that are introduced by mroonga.
-groonga_count_skip
+mroonga_count_skip
^^^^^^^^^^^^^^^^^^
This value is increased when 'fast line count feature' is used.
@@ -234,15 +234,15 @@ You can use this value to check if the feature is working when you enable it.
Here is an example how to check it::
- mysql> SHOW STATUS LIKE 'groonga_count_skip';
+ mysql> SHOW STATUS LIKE 'mroonga_count_skip';
+--------------------+-------+
| Variable_name | Value |
+--------------------+-------+
- | groonga_count_skip | 0 |
+ | mroonga_count_skip | 0 |
+--------------------+-------+
1 row in set (0.00 sec)
-groonga_fast_order_limit
+mroonga_fast_order_limit
^^^^^^^^^^^^^^^^^^^^^^^^
This value is increased when 'fast ORDER BY LIMIT feature' is used.
@@ -250,10 +250,10 @@ You can use this value to check if the feature is working when you enable it.
Here is an example how to check it::
- mysql> SHOW STATUS LIKE 'groonga_fast_order_limit';
+ mysql> SHOW STATUS LIKE 'mroonga_fast_order_limit';
+--------------------------+-------+
| Variable_name | Value |
+--------------------------+-------+
- | groonga_fast_order_limit | 0 |
+ | mroonga_fast_order_limit | 0 |
+--------------------------+-------+
1 row in set (0.00 sec)
Modified: doc/source/userguide.rst (+4 -4)
===================================================================
--- doc/source/userguide.rst 2012-01-25 21:35:48 +0900 (150c960)
+++ doc/source/userguide.rst 2012-01-25 21:41:20 +0900 (89d378c)
@@ -20,7 +20,7 @@ By using SHOW ENGINES command, you can check if mroonga is installed. ::
+------------+---------+------------------------------------------------------------+--------------+------+------------+
| Engine | Support | Comment | Transactions | XA | Savepoints |
+------------+---------+------------------------------------------------------------+--------------+------+------------+
- | groonga | YES | Fulltext search, column base | NO | NO | NO |
+ | mroonga | YES | Fulltext search, column base | NO | NO | NO |
| MRG_MYISAM | YES | Collection of identical MyISAM tables | NO | NO | NO |
| CSV | YES | CSV storage engine | NO | NO | NO |
| MyISAM | DEFAULT | Default engine as of MySQL 3.23 with great performance | NO | NO | NO |
@@ -29,11 +29,11 @@ By using SHOW ENGINES command, you can check if mroonga is installed. ::
+------------+---------+------------------------------------------------------------+--------------+------+------------+
6 rows in set (0.00 sec)
-If you see "groonga" storage engine like above, the installation is well done.
+If you see "mroonga" storage engine like above, the installation is well done.
If not installed, invoke INSTALL PLUGIN command like below. ::
- mysql> INSTALL PLUGIN groonga SONAME 'ha_mroonga.so';
+ mysql> INSTALL PLUGIN mroonga SONAME 'ha_mroonga.so';
Running modes
-------------
@@ -53,7 +53,7 @@ The structure of the storage mode is the following. You use it instead of existi
:align: center
With the wrapper mode, groonga is used for full text search function only, and another existing storage engine like InnoDB is used for storing data.
-By using wrapper mode, you combine InnoDB that is well-use as the storage engine and groonga that is a proven full text search engine, and you can use it as the stable database having the fast full text search function.
+By using wrapper mode, you combine InnoDB that is well-use as the storage engine and mroonga that is a proven full text search engine, and you can use it as the stable database having the fast full text search function.
The structure of the wrapper mode is the following. Full text search related operations are done by mroonga, and other operations are done by existing storage engines like MyISAM, InnoDB etc.
Mroonga is located between SQL Handler that processes SQL and an existing storage engine, thus all data goes through mroonga
Modified: doc/source/userguide/storage.rst (+24 -24)
===================================================================
--- doc/source/userguide/storage.rst 2012-01-25 21:35:48 +0900 (855e83e)
+++ doc/source/userguide/storage.rst 2012-01-25 21:41:20 +0900 (126acb8)
@@ -8,13 +8,13 @@ Here we explain how to use storage mode of mroonga
How to use full text search
---------------------------
-After confirming the installation, let's create a table. The important point is to specify mroonga by ``ENGINE = groonga``. ::
+After confirming the installation, let's create a table. The important point is to specify mroonga by ``ENGINE = mroonga``. ::
mysql> CREATE TABLE diaries (
-> id INT PRIMARY KEY AUTO_INCREMENT,
-> content VARCHAR(255),
-> FULLTEXT INDEX (content)
- -> ) ENGINE = groonga DEFAULT CHARSET utf8;
+ -> ) ENGINE = mroonga DEFAULT CHARSET utf8;
Query OK, 0 rows affected (0.10 sec)
We put data by INSERT. ::
@@ -87,13 +87,13 @@ MySQL has the following syntax to specify the parser [#parser]_ for full text se
FULLTEXT INDEX (content) WITH PARSER parser_name
-To use this syntax, you need to register all parsers in MySQL beforehand. On the other hand, groonga can dynamically add a tokeniser, that is a parser in MySQL. So if use this syntax in mroonga, tokenisers that are added in groonga dynamically cannot be supported. We think that this limitation decreases the convenience, and we choose our own syntax using COMMENT like the following. ::
+To use this syntax, you need to register all parsers in MySQL beforehand. On the other hand, mroonga can dynamically add a tokeniser, that is a parser in MySQL. So if use this syntax in mroonga, tokenisers that are added in mroonga dynamically cannot be supported. We think that this limitation decreases the convenience, and we choose our own syntax using COMMENT like the following. ::
FULLTEXT INDEX (content) COMMENT 'parser "TokenMecab"'
.. note::
- ``COMMENT`` in ``FULLTEXT INDEX`` is only supported MySQL 5.5 or later. If you use MySQL 5.1, use ``groonga_default_parser`` variable described below.
+ ``COMMENT`` in ``FULLTEXT INDEX`` is only supported MySQL 5.5 or later. If you use MySQL 5.1, use ``mroonga_default_parser`` variable described below.
You can specify one of following values as the parser.
@@ -160,16 +160,16 @@ You can specify the default parser by passing ``--with-default-parser`` option i
./configure --with-default-parser TokenMecab ...
-Or you can set ``groonga_default_parser`` variable in my.cnf or by SQL. If you specify it in my.cnf, the change will not be lost after restarting MySQL, but you need to restart MySQL to make it effective. On the other hand, if you set it in SQL, the change is effective immediately, but it will be lost when you restart MySQL.
+Or you can set ``mroonga_default_parser`` variable in my.cnf or by SQL. If you specify it in my.cnf, the change will not be lost after restarting MySQL, but you need to restart MySQL to make it effective. On the other hand, if you set it in SQL, the change is effective immediately, but it will be lost when you restart MySQL.
my.cnf::
[mysqld]
- groonga_default_parser=TokenMecab
+ mroonga_default_parser=TokenMecab
SQL::
- mysql> SET GLOBAL groonga_default_parser = TokenMecab;
+ mysql> SET GLOBAL mroonga_default_parser = TokenMecab;
Query OK, 0 rows affected (0.00 sec)
How to use geolocation search
@@ -184,7 +184,7 @@ For the table definition for geolocation search, you need to define a POINT type
-> name VARCHAR(255),
-> location POINT NOT NULL,
-> SPATIAL INDEX (location)
- -> ) ENGINE = groonga;
+ -> ) ENGINE = mroonga;
Query OK, 0 rows affected (0.06 sec)
To store data, you create POINT type data by using geomFromText() function like in MyISAM. ::
@@ -223,7 +223,7 @@ To get the record ID, you need to create a column named ``_id`` when you create
-> _id INT,
> content VARCHAR(255),
-> UNIQUE KEY (_id) USING HASH
- -> ) ENGINE = groonga;
+ -> ) ENGINE = mroonga;
Query OK, 0 rows affected (0.04 sec)
Tye typo of _id column should be integer one (TINYINT, SMALLINT, MEDIUMINT, INT or BIGINT).
@@ -236,7 +236,7 @@ So you need to exclude it from setting columns, or you need to use ``null`` as i
mysql> INSERT INTO memos VALUES (null, "今夜はさんま。");
Query OK, 1 row affected (0.00 sec)
- mysql> INSERT INTO memos VALUES (null, "明日はgroongaをアップデート。");
+ mysql> INSERT INTO memos VALUES (null, "明日はmroongaをアップデート。");
Query OK, 1 row affected (0.00 sec)
mysql> INSERT INTO memos VALUES (null, "帰りにおだんご。");
@@ -252,7 +252,7 @@ To get the record ID, you invoke SELECT with _id column. ::
| _id | content |
+------+------------------------------------------+
| 1 | 今夜はさんま。 |
- | 2 | 明日はgroongaをアップデート。 |
+ | 2 | 明日はmroongaをアップデート。 |
| 3 | 帰りにおだんご。 |
| 4 | 金曜日は肉の日。 |
+------+------------------------------------------+
@@ -296,24 +296,24 @@ Here is the example of the log. ::
The default log level is NOTICE, i.e. we have important information only and we don't have debug information etc.).
-You can get the log level by ``groonga_log_level`` system variable, that is a global variable. You can also modify it dynamically by using SET phrase. ::
+You can get the log level by ``mroonga_log_level`` system variable, that is a global variable. You can also modify it dynamically by using SET phrase. ::
- mysql> SHOW VARIABLES LIKE 'groonga_log_level';
+ mysql> SHOW VARIABLES LIKE 'mroonga_log_level';
+-------------------+--------+
| Variable_name | Value |
+-------------------+--------+
- | groonga_log_level | NOTICE |
+ | mroonga_log_level | NOTICE |
+-------------------+--------+
1 row in set (0.00 sec)
- mysql> SET GLOBAL groonga_log_level=DUMP;
+ mysql> SET GLOBAL mroonga_log_level=DUMP;
Query OK, 0 rows affected (0.00 sec)
- mysql> SHOW VARIABLES LIKE 'groonga_log_level';
+ mysql> SHOW VARIABLES LIKE 'mroonga_log_level';
+-------------------+-------+
| Variable_name | Value |
+-------------------+-------+
- | groonga_log_level | DUMP |
+ | mroonga_log_level | DUMP |
+-------------------+-------+
1 row in set (0.00 sec)
@@ -353,7 +353,7 @@ Imagine that we have a table with 20 columns like below. ::
c12 VARCHAR(20),
...
c20 DATETIME
- ) ENGINE = groonga DEFAULT CHARSET utf8;
+ ) ENGINE = mroonga DEFAULT CHARSET utf8;
When we run SELECT phrase like the following, mroonga reads data from columns that are referred by SELECT phrase and WHERE phrase only (and it does not access columns that not required internally).
@@ -376,15 +376,15 @@ In the following SELECT, for example, needless read of columns are skipped and y
You can check if this optimisation works or not by the status variable. ::
- mysql> SHOW STATUS LIKE 'groonga_count_skip';
+ mysql> SHOW STATUS LIKE 'mroonga_count_skip';
+--------------------+-------+
| Variable_name | Value |
+--------------------+-------+
- | groonga_count_skip | 1 |
+ | mroonga_count_skip | 1 |
+--------------------+-------+
1 row in set (0.00 sec)
-Each time the optimisation for counting rows works, ``groonga_count_skip`` status variable value is increased.
+Each time the optimisation for counting rows works, ``mroonga_count_skip`` status variable value is increased.
Note : This optimisation is implemented by using the index. It only works in the case where we records can be specified only by the index.
@@ -405,15 +405,15 @@ In the SELECT example below, ORDER BY LIMIT is processed in groonga only and the
You can check if this optimisation works or not by the status variable. ::
- mysql> SHOW STATUS LIKE 'groonga_fast_order_limit';
+ mysql> SHOW STATUS LIKE 'mroonga_fast_order_limit';
+--------------------------+-------+
| Variable_name | Value |
+--------------------------+-------+
- | groonga_fast_order_limit | 1 |
+ | mroonga_fast_order_limit | 1 |
+--------------------------+-------+
1 row in set (0.00 sec)
-Each time the optimisation for counting rows works, ``groonga_fast_order_limit`` status variable value is increased.
+Each time the optimisation for counting rows works, ``mroonga_fast_order_limit`` status variable value is increased.
Note : This optimisation is targeting queries like "select ... match against order by _score desc limit X, Y" only, and it works if all of the following conditions are right.
Modified: doc/source/userguide/wrapper.rst (+17 -17)
===================================================================
--- doc/source/userguide/wrapper.rst 2012-01-25 21:35:48 +0900 (4ef491b)
+++ doc/source/userguide/wrapper.rst 2012-01-25 21:41:20 +0900 (42f75f7)
@@ -22,13 +22,13 @@ In wrapper mode, mroonga works in wrapping an existing storage engine. To specif
How to use full text search
---------------------------
-After confirming the installation, let's create a table. The important point is to specify mroonga by ``ENGINE = groonga``. ::
+After confirming the installation, let's create a table. The important point is to specify mroonga by ``ENGINE = mroonga``. ::
mysql> CREATE TABLE diaries (
-> id INT PRIMARY KEY AUTO_INCREMENT,
-> content VARCHAR(255),
-> FULLTEXT INDEX (content)
- -> ) ENGINE = groonga COMMENT = 'engine "innodb"' DEFAULT CHARSET utf8;
+ -> ) ENGINE = mroonga COMMENT = 'engine "innodb"' DEFAULT CHARSET utf8;
Query OK, 0 rows affected (0.52 sec)
We put data by INSERT. ::
@@ -97,13 +97,13 @@ MySQL has the following syntax to specify the parser [#parser]_ for full text se
FULLTEXT INDEX (content) WITH PARSER parser_name
-To use this syntax, you need to register all parsers in MySQL beforehand. On the other hand, groonga can dynamically add a tokeniser, that is a parser in MySQL. So if use this syntax in mroonga, tokenisers that are added in groonga dynamically cannot be supported. We think that this limitation decreases the convenience, and we choose our own syntax using COMMENT like the following. ::
+To use this syntax, you need to register all parsers in MySQL beforehand. On the other hand, mroonga can dynamically add a tokeniser, that is a parser in MySQL. So if use this syntax in mroonga, tokenisers that are added in mroonga dynamically cannot be supported. We think that this limitation decreases the convenience, and we choose our own syntax using COMMENT like the following. ::
FULLTEXT INDEX (content) COMMENT 'parser "TokenMecab"'
.. note::
- ``COMMENT`` in ``FULLTEXT INDEX`` is only supported MySQL 5.5 or later. If you use MySQL 5.1, use ``groonga_default_parser`` variable described below.
+ ``COMMENT`` in ``FULLTEXT INDEX`` is only supported MySQL 5.5 or later. If you use MySQL 5.1, use ``mroonga_default_parser`` variable described below.
You can specify one of following values as the parser.
@@ -170,16 +170,16 @@ You can specify the default parser by passing ``--with-default-parser`` option i
./configure --with-default-parser TokenMecab ...
-Or you can set ``groonga_default_parser`` variable in my.cnf or by SQL. If you specify it in my.cnf, the change will not be lost after restarting MySQL, but you need to restart MySQL to make it effective. On the other hand, if you set it in SQL, the change is effective immediately, but it will be lost when you restart MySQL.
+Or you can set ``mroonga_default_parser`` variable in my.cnf or by SQL. If you specify it in my.cnf, the change will not be lost after restarting MySQL, but you need to restart MySQL to make it effective. On the other hand, if you set it in SQL, the change is effective immediately, but it will be lost when you restart MySQL.
my.cnf::
[mysqld]
- groonga_default_parser=TokenMecab
+ mroonga_default_parser=TokenMecab
SQL::
- mysql> SET GLOBAL groonga_default_parser = TokenMecab;
+ mysql> SET GLOBAL mroonga_default_parser = TokenMecab;
Query OK, 0 rows affected (0.00 sec)
Logging
@@ -197,24 +197,24 @@ Here is the example of the log. ::
The default log level is NOTICE, i.e. we have important information only and we don't have debug information etc.).
-You can get the log level by ``groonga_log_level`` system variable, that is a global variable. You can also modify it dynamically by using SET phrase. ::
+You can get the log level by ``mroonga_log_level`` system variable, that is a global variable. You can also modify it dynamically by using SET phrase. ::
- mysql> SHOW VARIABLES LIKE 'groonga_log_level';
+ mysql> SHOW VARIABLES LIKE 'mroonga_log_level';
+-------------------+--------+
| Variable_name | Value |
+-------------------+--------+
- | groonga_log_level | NOTICE |
+ | mroonga_log_level | NOTICE |
+-------------------+--------+
1 row in set (0.00 sec)
- mysql> SET GLOBAL groonga_log_level=DUMP;
+ mysql> SET GLOBAL mroonga_log_level=DUMP;
Query OK, 0 rows affected (0.00 sec)
- mysql> SHOW VARIABLES LIKE 'groonga_log_level';
+ mysql> SHOW VARIABLES LIKE 'mroonga_log_level';
+-------------------+-------+
| Variable_name | Value |
+-------------------+-------+
- | groonga_log_level | DUMP |
+ | mroonga_log_level | DUMP |
+-------------------+-------+
1 row in set (0.00 sec)
@@ -247,21 +247,21 @@ Tritonn took no specific countermeasure for this issue, but it introduced a work
Mroonga also has the optimisation for ORDER BY LIMIT.
-In the SELECT example below, ORDER BY LIMIT is processed in groonga only and the minimal records are passed to MySQL. ::
+In the SELECT example below, ORDER BY LIMIT is processed in mroonga only and the minimal records are passed to MySQL. ::
SELECT * FROM t1 WHERE MATCH(c2) AGAINST("hoge") ORDER BY c1 LIMIT 1;
You can check if this optimisation works or not by the status variable. ::
- mysql> SHOW STATUS LIKE 'groonga_fast_order_limit';
+ mysql> SHOW STATUS LIKE 'mroonga_fast_order_limit';
+--------------------------+-------+
| Variable_name | Value |
+--------------------------+-------+
- | groonga_fast_order_limit | 1 |
+ | mroonga_fast_order_limit | 1 |
+--------------------------+-------+
1 row in set (0.00 sec)
-Each time the optimisation for counting rows works, ``groonga_fast_order_limit`` status variable value is increased.
+Each time the optimisation for counting rows works, ``mroonga_fast_order_limit`` status variable value is increased.
Note : This optimisation is targeting queries like "select ... match against order by _score desc limit X, Y" only, and it works if all of the following conditions are right.