rroonga 5.0.3-x86-mingw32 → 5.0.4-x86-mingw32

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

@@ -130,7 +130,7 @@ Dump records only::
   ["Groonga","Introduction to Groonga"],
   ["Mroonga","Introduction to Mroonga"]
   ]
-  
+
 Dump schema only::
 
   > dump --dump_records no --dump_plugins no --dump_indexes no
@@ -141,7 +141,7 @@ Dump schema only::
   column_create Bookmarks title COLUMN_SCALAR ShortText
   
   table_create Lexicon TABLE_PAT_KEY ShortText
-  
+
 Parameters
 ----------
 
@@ -153,11 +153,13 @@ Optional parameters
 ``tables``
 """"""""""
 
-  出力対象のテーブルを「,」（カンマ）区切りで指定します。存在しないテーブルを指定した場合は無視されます。
+出力対象のテーブルを「,」（カンマ）区切りで指定します。存在しないテーブルを指定した場合は無視されます。
 
 ``dump_plugins``
 """"""""""""""""
 
+.. versionadded:: 5.0.3
+
 You can customize the output whether it contains registered plugins or not.
 To exclude registered plugins from the output, specify ``no``.
 
@@ -166,6 +168,8 @@ The default value is ``yes``.
 ``dump_schema``
 """""""""""""""
 
+.. versionadded:: 5.0.3
+
 You can customize the output whether it contains database schema or not.
 To exclude database schema from the output, specify ``no``.
 
@@ -174,6 +178,8 @@ The default value is ``yes``.
 ``dump_records``
 """"""""""""""""
 
+.. versionadded:: 5.0.3
+
 You can customize the output whether it contains records or not.
 To exclude records from the output, specify ``no``.
 
@@ -182,6 +188,8 @@ The default value is ``yes``.
 ``dump_indexes``
 """"""""""""""""
 
+.. versionadded:: 5.0.3
+
 You can customize the output whether it contains indexes or not.
 To exclude indexes from the output, specify ``no``.
 

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

@@ -0,0 +1,60 @@
+.. -*- rst -*-
+
+.. highlightlang:: none
+
+.. groonga-command
+.. database: io_flush
+
+``io_flush``
+============
+
+Summary
+-------
+
+.. note::
+
+   This command is an experimental feature.
+
+.. versionadded:: 5.0.5
+
+TODO
+
+Syntax
+------
+
+``io_flush`` command has two parameters. ::
+
+  io_flush [target_name]
+           [recursive=yes]
+
+Usage
+-----
+
+TODO
+
+Parameters
+----------
+
+This section describes parameters of ``io_flush``.
+
+Optional parameters
+^^^^^^^^^^^^^^^^^^^
+
+There are optional parameters.
+
+``target_name``
+"""""""""""""""
+
+TODO
+
+``recursive``
+"""""""""""""
+
+TODO
+
+Return value
+------------
+
+::
+
+  [HEADER, true]

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

@@ -0,0 +1,100 @@
+.. -*- rst -*-
+
+.. highlightlang:: none
+
+.. groonga-command
+.. database: logical_select
+
+``logical_select``
+========================
+
+Summary
+-------
+
+.. note::
+
+   This command is an experimental feature.
+
+.. versionadded:: 5.0.5
+
+TODO
+
+Syntax
+------
+
+``logical_select`` command has seven parameters.
+
+The required parameters are ``logical_table`` and ``shard_key``::
+
+  logical_select logical_table
+                 shard_key
+                 [min]
+                 [min_border]
+                 [max]
+                 [max_border]
+                 [filter]
+
+Usage
+-----
+
+TODO
+
+Parameters
+----------
+
+This section describes parameters of ``logical_select``.
+
+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
+------------
+
+TODO: add more description for RESULTS
+
+::
+
+  [HEADER, RESULTS]

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

@@ -0,0 +1,94 @@
+.. -*- rst -*-
+
+.. highlightlang:: none
+
+.. groonga-command
+.. database: logical_table_remove
+
+``logical_table_remove``
+========================
+
+Summary
+-------
+
+.. note::
+
+   This command is an experimental feature.
+
+.. versionadded:: 5.0.5
+
+TODO
+
+Syntax
+------
+
+``logical_table_remove`` command has six parameters.
+
+The required parameters are ``logical_table`` and ``shard_key``::
+
+  logical_table_remove logical_table
+                       shard_key
+                       [min]
+                       [min_border]
+                       [max]
+                       [max_border]
+
+Usage
+-----
+
+TODO
+
+Parameters
+----------
+
+This section describes parameters of ``logical_table_remove``.
+
+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.
+
+Return value
+------------
+
+::
+
+  [HEADER, true]

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

@@ -119,8 +119,8 @@ Daemon mode
 ^^^^^^^^^^^
 
 In daemon mode, ``groonga`` executable file runs as a daemon. Daemon
-is similar to server but it runs in the background. See 
-:ref:`_groonga-executable-file-server-mode` about server.
+is similar to server but it runs in the background. See
+:ref:`groonga-executable-file-server-mode` about server.
 
 Here is the syntax to run Groonga daemon with temporary database::
 

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

@@ -125,7 +125,7 @@ Additional normalizers
 
 There are additional normalizers:
 
-  * `groonga-normalizer-mysql <https://github.com/groonga/groonga-normalizer-mysql>_`
+  * `groonga-normalizer-mysql <https://github.com/groonga/groonga-normalizer-mysql>`_
 
 See also
 --------

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

@@ -8,13 +8,12 @@ Tuning
 Summary
 -------
 
-There are some tuning parameters for improving Groonga performance or
-handling a large database.
+There are some tuning parameters for handling a large database.
 
 Parameters
 ----------
 
-This section describes parameters.
+This section describes tuning parameters.
 
 .. _tuning-max-n-open-files:
 
@@ -23,15 +22,15 @@ The max number of open files per process
 
 This parameter is for handling a large database.
 
-Groonga creates one or more files per table and colum. If your
-database has many tables and columns, groonga process needs to open
+Groonga creates one or more files per table and column. If your
+database has many tables and columns, Groonga process needs to open
 many files.
 
 System limits the max number of open files per process. So you need to
 relax the limitation.
 
 Here is an expression that compute how many files are opened by
-groonga::
+Groonga::
 
   3 (for DB) +
     N tables +
@@ -64,16 +63,19 @@ Memory usage
 This parameter is for handling a large database.
 
 Groonga maps database files onto memory and accesses to them. Groonga
-doesn't maps unnecessary files onto memory until they are nneded.
+doesn't maps unnecessary files onto memory. Groonga maps files when
+they are needed.
 
 If you access to all data in database, all database files are mapped
-onto memory.  If total size of your database files is 6GiB, your
-groonga process uses 6GiB memory.
+onto memory. If total size of your database files is 6GiB, your
+Groonga process uses 6GiB memory.
 
-Normally, your all database files aren't mapped onto memry. But is may
+Normally, your all database files aren't mapped onto memory. But it may
 be occurred. It is an example case that you dump your database.
 
-You must have memory and swap that is larger than database.
+Normally, you must have memory and swap that is larger than
+database. Linux has tuning parameter to work with less memory and swap
+than database size.
 
 .. _tuning-linux:
 
@@ -84,8 +86,8 @@ This section describes how to configure parameters on Linux.
 
 .. _tuning-linux-nofile:
 
-nofile
-^^^^^^
+``nofile``
+^^^^^^^^^^
 
 You can relax the :ref:`tuning-max-n-open-files` parameter by creating
 a configuration file ``/etc/security/limits.d/groonga.conf`` that has
@@ -94,27 +96,26 @@ the following content::
   ${USER} soft nofile ${MAX_VALUE}
   ${USER} hard nofile ${MAX_VALUE}
 
-If you run ``groonga`` process by ``groonga`` user and your groonga
+If you run Groonga process by ``groonga`` user and your Groonga
 process needs to open less than 10000 files, use the following
 configuration::
 
   groonga soft nofile 10000
   groonga hard nofile 10000
 
-The configuration is applied after your groonga service is restarted
-or re-login as your groonga user.
+The configuration is applied after your Groonga service is restarted
+or re-login as your ``groonga`` user.
 
 .. _tuning-linux-overcommit-memory:
 
-vm.overcommit_memory
-^^^^^^^^^^^^^^^^^^^^
+``vm.overcommit_memory``
+^^^^^^^^^^^^^^^^^^^^^^^^
 
 This is :ref:`tuning-memory-usage` related parameter. You can handle a
 database that is larger than your memory and swap by setting
-``vm.overcommit_memory`` kernel parameter to 1. 1 means that Groonga
-can always map database files onto memory. It is no problem until
-groonga touch mapped database files that their size is larger than
-memory and swap. Groonga recommends the configuration.
+``vm.overcommit_memory`` kernel parameter to ``1``. ``1`` means that
+Groonga can always map database files onto memory. Groonga recommends
+the configuration.
 
 See `Linux kernel documentation about overcommit
 <https://www.kernel.org/doc/Documentation/vm/overcommit-accounting>`_
@@ -133,16 +134,17 @@ following command::
 
 .. _tuning-linux-max-map-count:
 
-vm.max_map_count
-^^^^^^^^^^^^^^^^
+``vm.max_map_count``
+^^^^^^^^^^^^^^^^^^^^
 
 This is :ref:`tuning-memory-usage` related parameter. You can handle a
 16GiB or more larger size database by increasing ``vm.max_map_count``
 kernel parameter. The parameter limits the max number of memory maps.
 
-The default value of the kernel parameter may be 65530 or 65536.
-Groonga maps 256KiB memory chunk at one time. If a database is larger
-than 16GiB, groonga reaches the limitation. (``256KiB * 65536 = 16GiB``)
+The default value of the kernel parameter may be ``65530`` or
+``65536``.  Groonga maps 256KiB memory chunk at one time. If a
+database is larger than 16GiB, Groonga reaches the
+limitation. (``256KiB * 65536 = 16GiB``)
 
 You needs to increase the value of the kernel parameter to handle
 16GiB or more larger size database. For example, you can handle almost
@@ -152,7 +154,7 @@ configuration by putting a configuration file
 
   vm.max_map_count = 131072
 
-Note that your real confiugration file will be the following because
+Note that your real configuration file will be the following because
 you already have ``vm.overcommit_memory`` configuration::
 
   vm.overcommit_memory = 1
@@ -170,7 +172,7 @@ This section describes how to configure parameters on FreeBSD.
 
 .. _tuning-freebsd-maxfilesperproc:
 
-kern.maxfileperproc
-^^^^^^^^^^^^^^^^^^^
+``kern.maxfileperproc``
+^^^^^^^^^^^^^^^^^^^^^^^
 
 TODO