rroonga 5.0.0-x86-mingw32 → 5.0.1-x86-mingw32

data/vendor/local/share/doc/groonga/ja/html/_sources/reference/commands/column_list.txt

@@ -46,7 +46,7 @@ All parameters are required.
 ``table``
 """""""""
 
-It specifies the name of table to be listed columns.
+Specifies the name of table to be listed columns.
 
 Return value
 ------------

data/vendor/local/share/doc/groonga/ja/html/_sources/reference/commands/column_rename.txt

@@ -69,17 +69,17 @@ All parameters are required.
 ``table``
 """""""""
 
-It specifies the name of table that has the column to be renamed.
+Specifies the name of table that has the column to be renamed.
 
 ``name``
 """"""""
 
-It specifies the column name to be renamed.
+Specifies the column name to be renamed.
 
 ``new_name``
 """"""""""""
 
-It specifies the new column name.
+Specifies the new column name.
 
 
 Return value

data/vendor/local/share/doc/groonga/ja/html/_sources/reference/commands/delete.txt

@@ -83,20 +83,20 @@ Parameters
 
 ``table``
 
-  It specifies the name of table to delete the records.
+  Specifies the name of table to delete the records.
 
 ``key``
 
-  It specifies the key of record to delete. If you use the table with TABLE_NO_KEY, the key is just ignored.
+  Specifies the key of record to delete. If you use the table with TABLE_NO_KEY, the key is just ignored.
   (Use ``id`` parameter in such a case)
 
 ``id``
 
-  It specifies the id of record to delete. If you specify ``id`` parameter, you must not specify ``key`` parameter.
+  Specifies the id of record to delete. If you specify ``id`` parameter, you must not specify ``key`` parameter.
 
 ``filter``
 
-  It specifies the expression of grn_expr to identify the record. If you specify ``filter`` parameter,
+  Specifies the expression of grn_expr to identify the record. If you specify ``filter`` parameter,
   you must not specify ``key`` and ``id`` parameter.
 
 Return value

data/vendor/local/share/doc/groonga/ja/html/_sources/reference/commands/load.txt

@@ -27,7 +27,7 @@ This section describes all parameters.
 
 ``values``
 
-  It specifies values loaded to records.
+  Specifies values loaded to records.
   Values should satisfy ``input_type`` format.
   If you specify "json" as ``input_type``, you can choose a format from below:
 
@@ -48,15 +48,15 @@ This section describes all parameters.
 
 ``table``
 
-  It specifies a table name you want to add records.
+  Specifies a table name you want to add records.
 
 ``columns``
 
-  It specifies column names in added records with comma separations.
+  Specifies column names in added records with comma separations.
 
 ``ifexists``
 
-  It specifies executed ``grn_expr`` string when the same primary key
+  Specifies executed ``grn_expr`` string when the same primary key
   as added records already exists in your table.
   If ``ifexists`` specifies ``grn_expr`` string (default: true) and
   its value is true, values in other (all columns excluding ``_key``
@@ -64,7 +64,7 @@ This section describes all parameters.
 
 ``input_type``
 
-  It specifies an input format for ``values``. It supports JSON only.
+  Specifies an input format for ``values``. It supports JSON only.
 
 Usage
 -----

data/vendor/local/share/doc/groonga/ja/html/_sources/reference/commands/lock_clear.txt

@@ -38,14 +38,14 @@ target object. It means that all locks in the database are cleared.
 Usage
 -----
 
-Here is an example to clear all locks in the database::
+Here is an example to clear all locks in the database:
 
 .. groonga-command
 .. include:: ../../example/reference/commands/lock_clear/database.log
 .. lock_clear
 
 Here is an example to clear locks of ``Entry`` table and ``Entry``
-table columns::
+table columns:
 
 .. groonga-command
 .. include:: ../../example/reference/commands/lock_clear/table.log
@@ -53,7 +53,7 @@ table columns::
 .. column_create Entry body COLUMN_SCALAR Text
 .. lock_clear Entry
 
-Here is an example to clear the lock of ``Site.title`` column::
+Here is an example to clear the lock of ``Site.title`` column:
 
 .. groonga-command
 .. include:: ../../example/reference/commands/lock_clear/column.log
@@ -69,7 +69,7 @@ This section describes all parameters.
 ``target_name``
 """""""""""""""
 
-It specifies the name of table or column.
+Specifies the name of table or column.
 
 If you don't specify it, database is used for the target object.
 

data/vendor/local/share/doc/groonga/ja/html/_sources/reference/commands/logical_count.txt

@@ -0,0 +1,173 @@
+.. -*- rst -*-
+
+.. highlightlang:: none
+
+.. groonga-command
+.. database: logical_count
+
+``logical_count``
+=================
+
+Summary
+-------
+
+.. note::
+
+   This command is an experimental feature.
+
+.. versionadded:: 5.0.0
+
+``logical_count`` is a command to count matched records even though actual records are stored into parted tables. It is useful for users because there is less need to care about maximum records of table :doc:`/limitations`.
+
+Note that this feature is not matured yet, so there are some limitations.
+
+* Create parted tables which contains "_YYYYMMDD" postfix. It is hardcoded, so you must create tables by each day.
+* Load proper data into parted tables on your own.
+
+Syntax
+------
+
+``logical_count`` command has seven parameters.
+
+The required parameters are ``logical_table`` and ``shard_key``::
+
+  logical_count logical_table
+                shard_key
+                [min]
+                [min_border]
+                [max]
+                [max_border]
+                [filter]
+
+Usage
+-----
+
+Register ``sharding`` plugin to use ``logical_count`` command in advance.
+
+.. groonga-command
+.. register sharding
+
+Note that ``logical_count`` is implemented as an experimental plugin, and the specification may be changed in the future.
+
+Here is the simple example which shows how to use this feature. Let's consider to count specified logs which are stored into multiple tables.
+
+Here is the schema and data.
+
+.. groonga-command
+.. include:: ../../example/reference/commands/logical_count/setup_schema.log
+.. table_create Logs_20150203 TABLE_NO_KEY
+.. column_create Logs_20150203 timestamp COLUMN_SCALAR Time
+.. column_create Logs_20150203 message COLUMN_SCALAR Text
+.. table_create Logs_20150204 TABLE_NO_KEY
+.. column_create Logs_20150204 timestamp COLUMN_SCALAR Time
+.. column_create Logs_20150204 message COLUMN_SCALAR Text
+.. table_create Logs_20150205 TABLE_NO_KEY
+.. column_create Logs_20150205 timestamp COLUMN_SCALAR Time
+.. column_create Logs_20150205 message COLUMN_SCALAR Text
+
+.. groonga-command
+.. include:: ../../example/reference/commands/logical_count/setup_data.log
+.. load --table Logs_20150203
+.. [
+.. {"timestamp": "2015-02-03 23:59:58", "message": "Start"},
+.. {"timestamp": "2015-02-03 23:59:58", "message": "Shutdown"},
+.. {"timestamp": "2015-02-03 23:59:59", "message": "Start"},
+.. {"timestamp": "2015-02-03 23:59:59", "message": "Shutdown"}
+.. ]
+.. load --table Logs_20150204
+.. [
+.. {"timestamp": "2015-02-04 00:00:00", "message": "Start"},
+.. {"timestamp": "2015-02-04 00:00:00", "message": "Shutdown"},
+.. {"timestamp": "2015-02-04 00:00:01", "message": "Start"},
+.. {"timestamp": "2015-02-04 00:00:01", "message": "Shutdown"},
+.. {"timestamp": "2015-02-04 23:59:59", "message": "Start"},
+.. {"timestamp": "2015-02-04 23:59:59", "message": "Shutdown"}
+.. ]
+.. load --table Logs_20150205
+.. [
+.. {"timestamp": "2015-02-05 00:00:00", "message": "Start"},
+.. {"timestamp": "2015-02-05 00:00:00", "message": "Shutdown"},
+.. {"timestamp": "2015-02-05 00:00:01", "message": "Start"},
+.. {"timestamp": "2015-02-05 00:00:01", "message": "Shutdown"}
+.. ]
+
+There are three tables which are mapped each day from 2015 Feb 03 to 2015 Feb 05.
+
+* Logs_20150203
+* Logs_20150204
+* Logs_20150205
+
+Then, it loads data into each table which correspond to.
+
+Let's count logs which contains "Shutdown" in ``message`` column and the value of timestamp is "2015-02-04 00:00:00" or later.
+
+Here is the query to achieve above purpose.
+
+.. groonga-command
+.. include:: ../../example/reference/commands/logical_count/count_shutdown.log
+.. logical_count Logs timestamp --filter 'message == "Shutdown"' --min "2015-02-04 00:00:00" --min_border "include"
+
+There is a well known limitation about the number of records. By sharding feature, you can overcome such limitations because such a limitation is applied per table.
+
+.. note::
+
+   There is no convenient query such as ``PARTITIONING BY`` in SQL. Thus, you must create table by ``table_create`` for each tables which contains "_YYYYMMDD" postfix in table name.
+
+Parameters
+----------
+
+This section describes parameters of ``logical_count``.
+
+Required parameter
+^^^^^^^^^^^^^^^^^^
+
+There are required parameters, ``logical_table`` and ``shard_key``.
+
+``logical_table``
+"""""""""""""""""
+
+Specifies logical table name. It means table name without "_YYYYMMDD" postfix.
+If you use actual table such as "Logs_20150203", "Logs_20150203" and so on, logical table name is "Logs".
+
+``shard_key``
+"""""""""""""
+
+Specifies column name which is treated as shared key in each parted table.
+
+Optional parameters
+^^^^^^^^^^^^^^^^^^^
+
+There are optional parameters.
+
+``min``
+"""""""
+
+Specifies the min value of ``shard_key``
+
+``min_border``
+""""""""""""""
+
+Specifies whether the min value of borderline must be include or not.
+Specify ``include`` or ``exclude`` as the value of this parameter.
+
+``max``
+"""""""
+
+Specifies the max value of ``shard_key``.
+
+``max_border``
+""""""""""""""
+
+Specifies whether the max value of borderline must be include or not.
+Specify ``include`` or ``exclude`` as the value of this parameter.
+
+``filter``
+""""""""""
+
+
+Return value
+------------
+
+::
+
+  [HEADER, LOGICAL_COUNT]

data/vendor/local/share/doc/groonga/ja/html/_sources/reference/commands/logical_range_filter.txt

@@ -0,0 +1,112 @@
+.. -*- rst -*-
+
+.. highlightlang:: none
+
+.. groonga-command
+.. database: logical_range_filter
+
+``logical_range_filter``
+========================
+
+Summary
+-------
+
+.. note::
+
+   This command is an experimental feature.
+
+.. versionadded:: 5.0.0
+
+TODO: Write summary
+
+Syntax
+------
+
+The required parameters are ``logical_table`` and ``shard_key``::
+
+  logical_range_filter
+                logical_table
+                shard_key
+                [min]
+                [min_border]
+                [max]
+                [max_border]
+                [order]
+                [filter]
+                [offset]
+                [output_columns]
+
+Usage
+-----
+
+Register ``sharding`` plugin to use ``logical_range_filter`` command in advance.
+
+.. groonga-command
+.. register sharding
+
+Parameters
+----------
+
+This section describes parameters of ``logical_range_filter``.
+
+Required parameter
+^^^^^^^^^^^^^^^^^^
+
+There are required parameters, ``logical_table`` and ``shard_key``.
+
+``logical_table``
+"""""""""""""""""
+
+Specifies logical table name. It means table name without "_YYYYMMDD" postfix.
+If you use actual table such as "Logs_20150203", "Logs_20150203" and so on, logical table name is "Logs".
+
+``shard_key``
+"""""""""""""
+
+Specifies column name which is treated as shared key in each parted table.
+
+Optional parameters
+^^^^^^^^^^^^^^^^^^^
+
+There are optional parameters.
+
+``min``
+"""""""
+
+Specifies the min value of ``shard_key``
+
+``min_border``
+""""""""""""""
+
+Specifies whether the min value of borderline must be include or not.
+Specify ``include`` or ``exclude`` as the value of this parameter.
+
+``max``
+"""""""
+
+Specifies the max value of ``shard_key``.
+
+``max_border``
+""""""""""""""
+
+Specifies whether the max value of borderline must be include or not.
+Specify ``include`` or ``exclude`` as the value of this parameter.
+
+``order``
+""""""""""
+
+``filter``
+""""""""""
+
+``offset``
+""""""""""
+
+``output_columns``
+""""""""""""""""""
+
+Return value
+------------
+
+::
+
+  [HEADER, LOGICAL_FILTERED]

data/vendor/local/share/doc/groonga/ja/html/_sources/reference/commands/normalize.txt

@@ -8,10 +8,11 @@
 ``normalize``
 =============
 
-.. Caution::
+.. note::
 
-  ``normalize`` command is the experimental feature.
-  This command may be changed in the future.
+   This command is an experimental feature.
+
+   This command may be changed in the future.
 
 Summary
 -------
@@ -55,7 +56,7 @@ There are required parameters, ``normalizer`` and ``string``.
 ``normalizer``
 """"""""""""""
 
-It specifies the normalizer name. ``normalize`` command uses the
+Specifies the normalizer name. ``normalize`` command uses the
 normalizer that is named ``normalizer``.
 
 See :doc:`/reference/normalizers` about built-in normalizers.
@@ -72,7 +73,7 @@ MySQL compatible normalizer by registering `groonga-normalizer-mysql
 ``string``
 """"""""""
 
-It specifies any string which you want to normalize.
+Specifies any string which you want to normalize.
 
 If you want to include spaces in ``string``, you need to quote
 ``string`` by single quotation (``'``) or double quotation (``"``).
@@ -89,7 +90,7 @@ There are optional parameters.
 ``flags``
 """""""""
 
-It specifies a normalization customize options. You can specify
+Specifies a normalization customize options. You can specify
 multiple options separated by "``|``". For example,
 ``REMOVE_BLANK|WITH_TYPES``.