rroonga 7.0.2-x64-mingw32 → 7.1.1-x64-mingw32

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

@@ -1,65 +0,0 @@
-.. -*- rst -*-
-
-.. highlightlang:: none
-
-``log_put``
-===========
-
-Summary
--------
-
-log_put - ログ出力
-
-groonga組込コマンドの一つであるlog_putについて説明します。組込コマンドは、groonga実行ファイルの引数、標準入力、またはソケット経由でgroongaサーバにリクエストを送信することによって実行します。
-
-log_putは、ログにmessageを出力します。
-
-Syntax
-------
-::
-
- log_put level message
-
-Usage
------
-::
-
- log_put ERROR ****MESSAGE****
- [true]
-
-Parameters
-----------
-
-``level``
-
-  設定するログ出力レベルの値を以下のいずれかで指定します。
-
-     EMERG
-     ALERT
-     CRIT
-     error
-     warning
-     notice
-     info
-     debug
-
-``message``
-
-  出力する文字列を指定します。
-
-Return value
-------------
-
-::
-
- [成功かどうかのフラグ]
-
-``成功かどうかのフラグ``
-
-  エラーが生じなかった場合にはtrue、エラーが生じた場合にはfalseを返す。
-
-See also
---------
-
-:doc:`log_level`
-:doc:`log_reopen`

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

@@ -1,62 +0,0 @@
-.. -*- rst -*-
-
-.. highlightlang:: none
-
-``log_reopen``
-==============
-
-Summary
--------
-
-log_reopen - ログファイルの再読み込み
-
-Groonga組込コマンドの一つであるlog_reopenについて説明します。組込コマンドは、groonga実行ファイルの引数、標準入力、またはソケット経由でgroongaサーバにリクエストを送信することによって実行します。
-
-log_reopenは、ログファイルを再読み込みします。
-
-現在、デフォルトのログ関数を用いている場合のみに対応しています。
-
-Syntax
-------
-::
-
- log_reopen
-
-Usage
------
-::
-
- log_reopen
-
- [true]
-
-log_reopenを用いたログのローテーション
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-1. ログファイルをmvなどで移動する。
-   ログはmvで移動された先のファイルに書き込まれる。
-2. log_reopenコマンドを実行する。
-3. 既存のログファイル名と同じファイル名で、新たなログファイルが作成される。
-   今後のログは新たなログファイルに書き込まれる。
-
-Parameters
-----------
-
-ありません。
-
-Return value
-------------
-
-::
-
- [成功かどうかのフラグ]
-
-``成功かどうかのフラグ``
-
-  エラーが生じなかった場合にはtrue、エラーが生じた場合にはfalseを返す。
-
-See also
---------
-
-:doc:`log_level`
-:doc:`log_put`

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

@@ -1,171 +0,0 @@
-.. -*- rst -*-
-
-.. highlightlang:: none
-
-.. groonga-command
-.. database: logical_count
-
-``logical_count``
-=================
-
-Summary
--------
-
-.. 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
-------
-
-This command takes many 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
-.. plugin_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 parameters
-^^^^^^^^^^^^^^^^^^^
-
-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
-
-::
-
-  [HEADER, LOGICAL_COUNT]

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

@@ -1,134 +0,0 @@
-.. -*- rst -*-
-
-.. highlightlang:: none
-
-.. groonga-command
-.. database: commands_logical_parameters
-
-``logical_parameters``
-======================
-
-Summary
--------
-
-.. versionadded:: 5.0.6
-
-``logical_parameters`` is a command for test. Normally, you don't need
-to use this command.
-
-``logical_parameters`` provides the following two features:
-
-  * It returns the current parameters for ``logical_*`` commands.
-  * It sets new parameters for ``logical_*`` commands.
-
-Here is a list of parameters:
-
-  * :ref:`logical-parameters-range-index`
-
-.. note::
-
-   The parameters are independent in each thread. (To be exact, each
-   :c:type:`grn_ctx`.) If you want to control the parameters
-   perfectly, you should reduce the max number of threads to ``1`` by
-   :doc:`/reference/commands/thread_limit` while you're using the
-   parameters.
-
-Syntax
-------
-
-This command takes only one optional parameter::
-
-  logical_parameters [range_index=null]
-
-Usage
------
-
-You need to register ``sharding`` plugin to use this command:
-
-.. groonga-command
-.. include:: ../../example/reference/commands/logical_parameters/usage_register.log
-.. plugin_register sharding
-
-You can get the all current parameter values by calling without
-parameters:
-
-.. groonga-command
-.. include:: ../../example/reference/commands/logical_parameters/usage_get.log
-.. logical_parameters
-
-You can set new values by calling with parameters:
-
-.. groonga-command
-.. include:: ../../example/reference/commands/logical_parameters/usage_set.log
-.. logical_parameters --range_index never
-
-``logical_parameters`` returns the parameter values before new values
-are set when you set new values.
-
-Parameters
-----------
-
-This section describes parameters.
-
-Required parameters
-^^^^^^^^^^^^^^^^^^^
-
-There is no required parameter.
-
-Optional parameters
-^^^^^^^^^^^^^^^^^^^
-
-There is one optional parameter.
-
-.. _logical-parameters-range-index:
-
-``range_index``
-"""""""""""""""
-
-Specifies how to use range index in :doc:`logical_range_filter` by
-keyword.
-
-Here are available keywords:
-
-  * ``auto`` (default)
-  * ``always``
-  * ``never``
-
-If ``auto`` is specified, range index is used only when it'll be
-efficient. This is the default value.
-
-.. groonga-command
-.. include:: ../../example/reference/commands/logical_parameters/range_index_auto.log
-.. logical_parameters --range_index auto
-
-If ``always`` is specified, range index is always used. It'll be
-useful for testing a case that range index is used.
-
-.. groonga-command
-.. include:: ../../example/reference/commands/logical_parameters/range_index_always.log
-.. logical_parameters --range_index always
-
-If ``never`` is specified, range index is never used. It'll be useful
-for testing a case that range index isn't used.
-
-.. groonga-command
-.. include:: ../../example/reference/commands/logical_parameters/range_index_never.log
-.. logical_parameters --range_index never
-
-Return value
-------------
-
-The command returns the current parameters for ``logical_*`` command::
-
-  [
-    HEADER,
-    {"range_index": HOW_TO_USE_RANGE_INDEX}
-  ]
-
-``HOW_TO_USE_RANGE_INDEX`` value is one of the followings:
-
-  * ``"auto"``
-  * ``"always"``
-  * ``"never"``
-
-See :doc:`/reference/command/output_format` for ``HEADER``.

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

@@ -1,195 +0,0 @@
-.. -*- rst -*-
-
-.. highlightlang:: none
-
-.. groonga-command
-.. database: logical_range_filter
-
-``logical_range_filter``
-========================
-
-Summary
--------
-
-.. versionadded:: 5.0.0
-
-TODO: Write summary
-
-Syntax
-------
-
-This command takes many parameters.
-
-The required parameters are ``logical_table`` and ``shard_key``::
-
-  logical_range_filter
-    logical_table
-    shard_key
-    [min=null]
-    [min_border=null]
-    [max=null]
-    [max_border=null]
-    [order=ascending]
-    [filter=null]
-    [offset=0]
-    [limit=10]
-    [output_columns=_key,*]
-    [use_range_index=null]
-
-There are some parameters that can be only used as named
-parameters. You can't use these parameters as ordered parameters. You
-must specify parameter name.
-
-Here are parameters that can be only used as named parameters:
-
-  * ``cache=no``
-
-Usage
------
-
-Register ``sharding`` plugin to use ``logical_range_filter`` command in advance.
-
-.. groonga-command
-.. plugin_register sharding
-
-TODO: Add examples
-
-Parameters
-----------
-
-This section describes parameters of ``logical_range_filter``.
-
-Required parameters
-^^^^^^^^^^^^^^^^^^^
-
-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".
-
-TODO: Add examples
-
-``shard_key``
-"""""""""""""
-
-Specifies column name which is treated as shared key in each parted table.
-
-TODO: Add examples
-
-Optional parameters
-^^^^^^^^^^^^^^^^^^^
-
-There are optional parameters.
-
-``min``
-"""""""
-
-Specifies the min value of ``shard_key``
-
-TODO: Add examples
-
-``min_border``
-""""""""""""""
-
-Specifies whether the min value of borderline must be include or not.
-Specify ``include`` or ``exclude`` as the value of this parameter.
-
-TODO: Add examples
-
-``max``
-"""""""
-
-Specifies the max value of ``shard_key``.
-
-TODO: Add examples
-
-``max_border``
-""""""""""""""
-
-Specifies whether the max value of borderline must be include or not.
-Specify ``include`` or ``exclude`` as the value of this parameter.
-
-TODO: Add examples
-
-``order``
-""""""""""
-
-TODO
-
-``filter``
-""""""""""
-
-TODO
-
-``offset``
-""""""""""
-
-TODO
-
-``limit``
-"""""""""
-
-TODO
-
-``output_columns``
-""""""""""""""""""
-
-TODO
-
-``use_range_index``
-"""""""""""""""""""
-
-Specifies whether range_index is used or not.
-Note that it's a parameter for test. It should not be used for production.
-
-TODO: Add examples
-
-Cache related parameter
-^^^^^^^^^^^^^^^^^^^^^^^
-
-.. _logical-range-filter-cache:
-
-``cache``
-"""""""""
-
-Specifies whether caching the result of this query or not.
-
-If the result of this query is cached, the next same query returns
-response quickly by using the cache.
-
-It doesn't control whether existing cached result is used or not.
-
-Here are available values:
-
-.. list-table::
-   :header-rows: 1
-
-   * - Value
-     - Description
-   * - ``no``
-     - Don't cache the output of this query.
-   * - ``yes``
-     - Cache the output of this query.
-       It's the default value.
-
-TODO: Add examples
-
-.. Here is an example to disable caching the result of this query:
-
-.. .. groonga-command
-.. .. include:: ../../example/reference/commands/logical_range_filter/cache_no.log
-.. .. logical_range_filter ... --cache no
-
-The default value is ``yes``.
-
-Return value
-------------
-
-TODO
-
-::
-
-  [HEADER, LOGICAL_FILTERED]