rroonga 2.0.7-x86-mingw32 → 2.0.8-x86-mingw32

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

@@ -0,0 +1,20 @@
+.. -*- rst -*-
+
+.. highlightlang:: none
+
+Function
+========
+
+Function can be used in some commands. For example, you can use
+function in ``--filter``, ``--scorer`` and ``output_columns``
+options of :doc:`commands/select`.
+
+This section describes about function and built-in functions.
+
+TODO: Add documentations about function.
+
+.. toctree::
+   :maxdepth: 1
+   :glob:
+
+   functions/*

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

@@ -192,17 +192,11 @@ You can specify the value of ``approximate_type`` by one of the followings.
 
     There is a limitation about ``geo_distance``. ``geo_distance`` can not
     calculate the value of distance between two points across meridian,
-    euator or the date line.
+    equator or the date line if you use ``sphere`` or ``ellipsoid`` as
+    approximate type. There is not such a limitation for ``rectangle``.
     This is temporary limitation according to the implementation of groonga,
     but it will be fixed in the future release.
 
-.. note::
-
-    There is a limitation about ``geo_distance`` above notice.
-    But it relaxes the limitation if you use ``rectangle`` as approximate type.
-    You can calculate the correct distance if two point are placed at northern
-    hemisphere or southern hemisphere.
-
 ``rectangle``
 ...............
 
@@ -223,6 +217,29 @@ Here is a sample about calculating the value of distance with explicitly specifi
 
 .. include:: ../../example/reference/functions/geo_distance_distance_rectangle.log
 
+Here are samples about calculating the value of distance with explicitly specified point across meridian, equator, the date line.
+
+.. groonga-command
+.. include:: ../../example/reference/functions/geo_distance_distance_rectangle_across_meridian.log
+.. select Geo --output_columns distance --scorer 'distance = geo_distance("175904000x8464000", "145508000x-13291000", "rectangle")'
+
+This sample shows the value of distance across meridian.
+The return value of ``geo_distance("175904000x8464000", "145508000x-13291000", "rectangle")`` is the value of distance from Paris, Flance to Madrid, Spain.
+
+.. groonga-command
+.. include:: ../../example/reference/functions/geo_distance_distance_rectangle_across_equator.log
+.. select Geo --output_columns distance --scorer 'distance = geo_distance("146566000x-266422000", "-56880000x-172310000", "rectangle")'
+
+This sample shows the value of distance across equator.
+The return value of ``geo_distance("146566000x-266422000", "-56880000x-172310000", "rectangle")`` is the value of distance from New York, The United Status to Brasillia, Brasil.
+
+.. groonga-command
+.. include:: ../../example/reference/functions/geo_distance_distance_rectangle_across_the_date_line.log
+.. select Geo --output_columns distance --scorer 'distance = geo_distance("143660000x419009000", "135960000x-440760000", "rectangle")'
+
+This sample shows the value of distance across the date line.
+The return value of ``geo_distance("143660000x419009000", "135960000x-440760000", "rectangle")`` is the value of distance from Beijin, China to San Francisco, The United States.
+
 .. note::
 
     ``geo_distance`` uses square approximation as default. If you omit ``approximate_type``, ``geo_distance`` behaves like ``rectangle`` was specified.

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

@@ -0,0 +1,120 @@
+.. -*- rst -*-
+
+.. highlightlang:: none
+
+.. groonga-command
+.. database: functions_snippet_html
+
+snippet_html
+============
+
+.. caution::
+
+   This feature is experimental. API will be changed.
+
+Summary
+-------
+
+``snippet_html`` extracts snippets of target text around search
+keywords (``KWIC``. ``KeyWord In Context``). The snippets are prepared
+for embedding HTML. Special characters such as ``<`` and ``>`` are
+escapsed as ``&lt;`` and ``&gt;``. Keyword is surrounded with ``<span
+class="keyword">`` and ``</span>``. For example, a snippet of ``I am a
+groonga user. <3`` for keyword ``groonga`` is ``I am a <span
+class="keyword">groonga</span> user. &lt;3``.
+
+Syntax
+------
+
+``snippet_html`` has only one parameter::
+
+  snippet_html(column)
+
+``snippet_html`` has many parameters internally but they can't be
+specified for now. You will be able to custom those parameters soon.
+
+Usage
+-----
+
+Here are a schema definition and sample data to show usage.
+
+.. groonga-command
+.. include:: ../../example/reference/functions/snippet_html/usage_setup.log
+.. table_create Documents TABLE_NO_KEY
+.. column_create Documents content COLUMN_SCALAR Text
+.. table_create Terms TABLE_PAT_KEY|KEY_NORMALIZE ShortText --default_tokenizer TokenBigram
+.. column_create Terms documents_content_index COLUMN_INDEX|WITH_POSITION Documents content
+.. load --table Documents
+.. [
+.. ["content"],
+.. ["Groonga is a fast and accurate full text search engine based on inverted index. One of the characteristics of groonga is that a newly registered document instantly appears in search results. Also, groonga allows updates without read locks. These characteristics result in superior performance on real-time applications."],
+.. ["Groonga is also a column-oriented database management system (DBMS). Compared with well-known row-oriented systems, such as MySQL and PostgreSQL, column-oriented systems are more suited for aggregate queries. Due to this advantage, groonga can cover weakness of row-oriented systems."]
+.. ]
+
+``snippet_html`` can be used in only ``--output_columns`` in
+:doc:`/reference/commands/select`.
+
+You need to specify ``--command_version 2`` argument explicitly
+because function call in ``--output_columns`` is experimental feature
+in groonga 2.0.9. It will be enabled by default soon.
+
+You also need to specify ``--query`` and/or ``--filter``. Keywords are
+extracted from ``--query`` and ``--filter`` arguments.
+
+The following example uses ``--query "fast performance"``. In this
+case, ``fast`` and ``performance`` are used as keywords.
+
+.. groonga-command
+.. include:: ../../example/reference/functions/snippet_html/usage_basic.log
+.. select Documents --output_columns "snippet_html(content)" --command_version 2 --match_columns content --query "fast performance"
+
+``--query "fast performance"`` matches to only the first record's
+content. ``snippet_html(content)`` extracts two text parts that
+include the keywords ``fast`` or ``performance`` and surronds the
+keywords with ``<span class="keyword">`` and ``</span>``.
+
+The max number of text parts is 3. If there are 4 or more text parts
+that include the keywords, only the leading 3 parts are only used.
+
+The max size of a text part is 200byte. The unit is bytes not
+chracters. The size doesn't include inserted ``<span keyword="keyword">``
+and ``</span>``.
+
+Both the max number of text parts and the max size of a text part
+aren't customizable.
+
+You can specify string literal instead of column.
+
+.. groonga-command
+.. include:: ../../example/reference/functions/snippet_html/usage_string_literal.log
+.. select Documents --output_columns 'snippet_html("Groonga is very fast fulltext search engine.")' --command_version 2 --match_columns content --query "fast performance"
+
+Return value
+------------
+
+``snippet_html`` returns an array of string. An element of array is a
+snippet::
+
+  [SNIPPET1, SNIPPET2, SNIPPET3]
+
+A snippet includes one or more keywords. The max byte size of a
+snippet except ``<span keyword="keyword">`` and ``</span>`` is
+200byte. The unit isn't the number of chracters.
+
+The array size is larger than or equal to 0 and less than or equal
+to 3. The max size 3 will be customizable soon.
+
+TODO
+----
+
+* Make the max number of text parts customizable.
+* Make the max size of a text part customizable.
+* Make keywords customizable.
+* Make tag that surrounds a keyword customizable.
+* Make normalization customizable.
+* Support options by object literal.
+
+See also
+--------
+
+* :doc:`/reference/commands/select`

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

@@ -9,7 +9,7 @@ Indexing
 ========
 
 Groonga supports both online index construction and offline
-index construction since 1.3.1.
+index construction since 2.0.0.
 
 Online index construction
 -------------------------
@@ -25,6 +25,8 @@ tweets, news, blog posts and so on will value
 freshness. Online index construction can make fresh
 documents searchable and keep searchable while indexing.
 
+.. _offline-index-construction:
+
 Offline index construction
 --------------------------
 

data/vendor/local/share/doc/groonga/{source/reference/functions.txt → ja/html/_sources/reference/query_expanders.txt}

@@ -2,11 +2,11 @@
 
 .. highlightlang:: none
 
-組み込み関数一覧
-================
+Query expanders
+===============
 
 .. toctree::
    :maxdepth: 1
    :glob:
 
-   functions/*
+   query_expanders/*

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

@@ -0,0 +1,153 @@
+.. -*- rst -*-
+
+.. highlightlang:: none
+
+QueryExpanderTSV
+================
+
+Summary
+-------
+
+``QueryExpanderTSV`` is a query expander plugin that reads synonyms
+from TSV (Tab Separated Values) file. This plugin provides poor
+feature than the embedded query expansion feature. For example, it
+doesn't support word normalization. But it may be easy to use because
+you can manage your synonyms by TSV file. You can edit your synonyms
+by spreadsheet application such as Excel. With the embedded query
+expansion feature, you manage your synonyms by groonga's table.
+
+Install
+-------
+
+You need to register ``query_expanders/tsv`` as a plugin before you
+use ``QueryExpanderTSV``::
+
+  register query_expanders/tsv
+
+Usage
+-----
+
+You just add ``--query_expansion QueryExpanderTSV`` parameter to
+``select`` command::
+
+  select --query "QUERY" --query_expansion QueryExpanderTSV
+
+If ``QUERY`` has registered synonyms, they are expanded. For example,
+there are the following synonyms.
+
++----------------------------+------------------------+----------------------+
+|            word            |       synonym 1        |      synonym 2       |
++============================+========================+======================+
+|          groonga           |        groonga         |        Senna         |
++----------------------------+------------------------+----------------------+
+|          mroonga           |        mroonga         |    groonga MySQL     |
++----------------------------+------------------------+----------------------+
+
+The table means that ``synonym 1`` and ``synonym 2`` are synonyms of
+``word``. For example, ``groonga`` and ``Senna`` are synonyms of
+``groonga``. And ``mroonga`` and ``groonga MySQL`` are synonyms of
+``mroonga``.
+
+Here is an example of query expnasion that uses ``groonga`` as query::
+
+  select --query "groonga" --query_expansion QueryExpanderTSV
+
+The above command equals to the following command::
+
+  select --query "groonga OR Senna" --query_expansion QueryExpanderTSV
+
+Here is another example of query expnasion that uses ``mroonga
+search`` as query::
+
+  select --query "mroonga search" --query_expansion QueryExpanderTSV
+
+The above command equals to the following command::
+
+  select --query "(mroonga OR (groonga MySQL)) search" --query_expansion QueryExpanderTSV
+
+It is important that registered words (``groonga`` and ``mroonga``)
+are only expanded to synonyms and not registered words (``search``)
+are not expanded. Query expansion isn't occurred
+recursively. ``groonga`` is appeared in ``(mroonga OR (groonga
+MySQL))`` as query expansion result but it isn't expanded.
+
+Normally, you need to include ``word`` itself into synonyms. For
+example, ``groonga`` and ``mroonga`` are included in synonyms of
+themselves. If you want to ignore ``word`` itself, you don't include
+``word`` itself into synonyms. For example, if you want to use query
+expansion as spelling correction, you should use the following
+synonyms.
+
++----------------------------+------------------------+
+|            word            |        synonym         |
++============================+========================+
+|           gronga           |        groonga         |
++----------------------------+------------------------+
+
+``gronga`` in ``word`` has a typo. A ``o`` is missing. ``groonga`` in
+``synonym`` is the correct word.
+
+Here is an example of using query expnasion as spelling correction::
+
+  select --query "gronga" --query_expansion QueryExpanderTSV
+
+The above command equals to the following command::
+
+  select --query "groonga" --query_expansion QueryExpanderTSV
+
+The former command has a typo in ``--query`` value but the latter
+command doesn't have any typos.
+
+TSV File
+--------
+
+Synonyms are defined in TSV format file. This section describes about
+it.
+
+Location
+^^^^^^^^
+
+The file name should be ``synonyms.tsv`` and it is located at
+configuration directory. For example, ``/etc/groonga/synonyms.tsv`` is
+a TSV file location. The location is decided at build time.
+
+You can change the location by environment variable
+``GRN_QUERY_EXPANDER_TSV_SYNONYMS_FILE`` at run time::
+
+  % env GRN_QUERY_EXPANDER_TSV_SYNONYMS_FILE=/tmp/synonyms.tsv groonga
+
+With the above command, ``/tmp/synonyms.tsv`` file is used.
+
+Format
+^^^^^^
+
+You can define zero or more synonyms in a TSV file. You define a
+``word`` and ``synonyms`` pair by a line. ``word`` is expanded to
+``synonyms`` in ``--query`` value. ``Synonyms`` are combined by
+``OR``. For example, ``groonga`` and ``Senna`` synonyms are expanded
+as ``groonga OR Senna``.
+
+The first column is ``word`` and the rest columns are ``synonyms`` of
+the ``word``. Here is a sample line for ``word`` is ``groonga`` and
+``synonyms`` are ``groonga`` and ``Senna``. ``(TAB)`` means a tab
+character (``U+0009``)::
+
+  groonga(TAB)groonga(TAB)Senna
+
+Comment line is supported. Lines that start with ``#`` are ignored.
+Here is an example for comment line. ``groonga`` line is ignored as
+comment line::
+
+  #groonga(TAB)groonga(TAB)Senna
+  mroonga(TAB)mroonga(TAB)groonga MySQL
+
+Limitation
+----------
+
+You need to restart groonga to reload your synonyms. TSV file is
+loaded only at the plugin load time.
+
+See also
+--------
+
+  * :ref:`query-expansion`

data/vendor/local/share/doc/groonga/ja/html/_sources/server/http/comparison.txt

@@ -27,7 +27,7 @@ There are many differences between :doc:`groonga` and
 +----------------------------+------------------------+----------------------+
 |      Gzip compression      | x                      | o                    |
 +----------------------------+------------------------+----------------------+
-|            POST            | x                      | x (comming soon)     |
+|            POST            | x                      | o                    |
 +----------------------------+------------------------+----------------------+
 |           HTTPS            | x                      | o                    |
 +----------------------------+------------------------+----------------------+
@@ -270,7 +270,17 @@ processed by groonga. You don't need to consider about other modules.
 POST
 ----
 
-TODO
+You can load your data by POST JSON data. You need follow the
+following rules to use loading by POST.
+
+* `Content-Type` header value must be `application/json`.
+* JSON data is sent as body.
+* Table name is specified by query parameter such as ``table=NAME``.
+
+Here is an example curl command line that loads two users `alice` and
+`bob` to `Users` table::
+
+  % curl --data-binary '[{"_key": "alice"}, {"_key": "bob"}]' -H "Content-Type: application/json" "http://localhost:10041/d/load?table=Users"
 
 HTTPS
 -----

data/vendor/local/share/doc/groonga/ja/html/_sources/spec/gqtp.txt

@@ -0,0 +1,214 @@
+.. -*- rst -*-
+
+.. highlightlang:: none
+
+GQTP
+====
+
+GQTP is the acronym of Groonga Query Transfer Protocol. GQTP is the
+original protocol for groonga.
+
+Protocol
+--------
+
+GQTP is stateful client server model protocol. The following sequence
+is one processing unit:
+
+* Client sends a request
+* Server receives the request
+* Server processes the request
+* Server sends a response
+* Client receives the response
+
+You can do zero or more processing units in a session.
+
+Both request and response consist of GQTP header and body. GQTP header
+is fixed size data. Body is variable size data and its size is stored
+in GQTP header. The content of body isn't defined in GQTP.
+
+.. _gqtp-header-spec:
+
+GQTP header
+^^^^^^^^^^^
+
+GQTP header consists of the following unsigned integer values:
+
++----------------+-------+----------------------------+
+|      Name      |  Size |        Description         |
++================+=======+============================+
+|  ``protocol``  | 1byte | Protocol type.             |
++----------------+-------+----------------------------+
+| ``query_type`` | 1byte | Content type of body.      |
++----------------+-------+----------------------------+
+| ``key_length`` | 2byte | Not used.                  |
++----------------+-------+----------------------------+
+|   ``level``    | 1byte | Not used.                  |
++----------------+-------+----------------------------+
+|   ``flags``    | 1byte | Flags.                     |
++----------------+-------+----------------------------+
+|   ``status``   | 2byte | Return code.               |
++----------------+-------+----------------------------+
+|    ``size``    | 4byte | Body size.                 |
++----------------+-------+----------------------------+
+|   ``opaque``   | 4byte | Not used.                  |
++----------------+-------+----------------------------+
+|    ``cas``     | 8byte | Not used.                  |
++----------------+-------+----------------------------+
+
+All header values are encoded by network byte order.
+
+The following sections describes available values of each header value.
+
+The total size of GQTP header is 24byte.
+
+``protocol``
+""""""""""""
+
+The value is always ``0xc7`` in both request and response GQTP header.
+
+``query_type``
+""""""""""""""
+
+The value is one of the following values:
+
++-------------+--------+----------------------------+
+|    Name     | Value  |        Description         |
++=============+========+============================+
+|  ``NONE``   |   0    | Free format.               |
++-------------+--------+----------------------------+
+|   ``TSV``   |   1    | Tab Separated Values.      |
++-------------+--------+----------------------------+
+|  ``JSON``   |   2    | JSON.                      |
++-------------+--------+----------------------------+
+|   ``XML``   |   3    | XML.                       |
++-------------+--------+----------------------------+
+| ``MSGPACK`` |   4    | MessagePack.               |
++-------------+--------+----------------------------+
+
+This is not used in request GQTP header.
+
+This is used in response GQTP header. Body is formatted as specified
+type.
+
+``flags``
+"""""""""
+
+The value is bitwise OR of the following values:
+
++-----------+--------+----------------------------+
+|   Name    | Value  |        Description         |
++===========+========+============================+
+| ``MORE``  |  0x01  | There are more data.       |
++-----------+--------+----------------------------+
+| ``TAIL``  |  0x02  | There are no more data.    |
++-----------+--------+----------------------------+
+| ``HEAD``  |  0x04  | Not used.                  |
++-----------+--------+----------------------------+
+| ``QUIET`` |  0x08  | Be quiet.                  |
++-----------+--------+----------------------------+
+| ``QUIT``  |  0x10  | Quit.                      |
++-----------+--------+----------------------------+
+
+You must specify ``MORE`` or ``TAIL`` flag.
+
+If you use ``MORE`` flag, you should also use ``QUIET`` flag. Because
+you don't need to show a response for your partial request.
+
+Use ``QUIT`` flag to quit this session.
+
+``status``
+""""""""""
+
+Here are available values. The new statuses will be added in the
+future.
+
+* 0: ``SUCCESS``
+* 1: ``END_OF_DATA``
+* 65535: ``UNKNOWN_ERROR``
+* 65534: ``OPERATION_NOT_PERMITTED``
+* 65533: ``NO_SUCH_FILE_OR_DIRECTORY``
+* 65532: ``NO_SUCH_PROCESS``
+* 65531: ``INTERRUPTED_FUNCTION_CALL``
+* 65530: ``INPUT_OUTPUT_ERROR``
+* 65529: ``NO_SUCH_DEVICE_OR_ADDRESS``
+* 65528: ``ARG_LIST_TOO_LONG``
+* 65527: ``EXEC_FORMAT_ERROR``
+* 65526: ``BAD_FILE_DESCRIPTOR``
+* 65525: ``NO_CHILD_PROCESSES``
+* 65524: ``RESOURCE_TEMPORARILY_UNAVAILABLE``
+* 65523: ``NOT_ENOUGH_SPACE``
+* 65522: ``PERMISSION_DENIED``
+* 65521: ``BAD_ADDRESS``
+* 65520: ``RESOURCE_BUSY``
+* 65519: ``FILE_EXISTS``
+* 65518: ``IMPROPER_LINK``
+* 65517: ``NO_SUCH_DEVICE``
+* 65516: ``NOT_A_DIRECTORY``
+* 65515: ``IS_A_DIRECTORY``
+* 65514: ``INVALID_ARGUMENT``
+* 65513: ``TOO_MANY_OPEN_FILES_IN_SYSTEM``
+* 65512: ``TOO_MANY_OPEN_FILES``
+* 65511: ``INAPPROPRIATE_I_O_CONTROL_OPERATION``
+* 65510: ``FILE_TOO_LARGE``
+* 65509: ``NO_SPACE_LEFT_ON_DEVICE``
+* 65508: ``INVALID_SEEK``
+* 65507: ``READ_ONLY_FILE_SYSTEM``
+* 65506: ``TOO_MANY_LINKS``
+* 65505: ``BROKEN_PIPE``
+* 65504: ``DOMAIN_ERROR``
+* 65503: ``RESULT_TOO_LARGE``
+* 65502: ``RESOURCE_DEADLOCK_AVOIDED``
+* 65501: ``NO_MEMORY_AVAILABLE``
+* 65500: ``FILENAME_TOO_LONG``
+* 65499: ``NO_LOCKS_AVAILABLE``
+* 65498: ``FUNCTION_NOT_IMPLEMENTED``
+* 65497: ``DIRECTORY_NOT_EMPTY``
+* 65496: ``ILLEGAL_BYTE_SEQUENCE``
+* 65495: ``SOCKET_NOT_INITIALIZED``
+* 65494: ``OPERATION_WOULD_BLOCK``
+* 65493: ``ADDRESS_IS_NOT_AVAILABLE``
+* 65492: ``NETWORK_IS_DOWN``
+* 65491: ``NO_BUFFER``
+* 65490: ``SOCKET_IS_ALREADY_CONNECTED``
+* 65489: ``SOCKET_IS_NOT_CONNECTED``
+* 65488: ``SOCKET_IS_ALREADY_SHUTDOWNED``
+* 65487: ``OPERATION_TIMEOUT``
+* 65486: ``CONNECTION_REFUSED``
+* 65485: ``RANGE_ERROR``
+* 65484: ``TOKENIZER_ERROR``
+* 65483: ``FILE_CORRUPT``
+* 65482: ``INVALID_FORMAT``
+* 65481: ``OBJECT_CORRUPT``
+* 65480: ``TOO_MANY_SYMBOLIC_LINKS``
+* 65479: ``NOT_SOCKET``
+* 65478: ``OPERATION_NOT_SUPPORTED``
+* 65477: ``ADDRESS_IS_IN_USE``
+* 65476: ``ZLIB_ERROR``
+* 65475: ``LZO_ERROR``
+* 65474: ``STACK_OVER_FLOW``
+* 65473: ``SYNTAX_ERROR``
+* 65472: ``RETRY_MAX``
+* 65471: ``INCOMPATIBLE_FILE_FORMAT``
+* 65470: ``UPDATE_NOT_ALLOWED``
+* 65469: ``TOO_SMALL_OFFSET``
+* 65468: ``TOO_LARGE_OFFSET``
+* 65467: ``TOO_SMALL_LIMIT``
+* 65466: ``CAS_ERROR``
+* 65465: ``UNSUPPORTED_COMMAND_VERSION``
+
+``size``
+""""""""
+
+The size of body. The maximum body size is 4GiB because ``size`` is
+4byte unsigned integer. If you want to send 4GiB or more larger data,
+use ``MORE`` flag.
+
+Example
+-------
+
+TODO
+
+See also
+--------
+
+TODO