rroonga 7.0.2-x86-mingw32 → 7.1.1-x86-mingw32

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

@@ -1,16 +0,0 @@
-.. -*- rst -*-
-.. Groonga Project
-
-.. highlightlang:: none
-
-Operations
-==========
-
-Groonga has the multiple search operations. This section describes
-about search operations.
-
-.. toctree::
-   :maxdepth: 1
-   :glob:
-
-   operations/*

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

@@ -1,52 +0,0 @@
-.. -*- rst -*-
-
-.. highlightlang:: none
-
-Geolocation search
-==================
-
-Groonga supports geolocation search. It uses index for
-search. It means that you can search by geolocation fast
-like fulltext search.
-
-Supported features
-------------------
-
-Groonga supports only point as data type. Line, surface and
-so on aren't supported yet. Here is a feature list:
-
-#. Groonga can store a point to a column.
-#. Groonga can search records that have a point in the specified rectangle.
-#. Groonga can search records that have a point in the specified circle.
-#. Groonga can calculate distance between two points.
-#. Groonga can sort records by distance from the specified
-   point in ascending order.
-
-Here are use cases for Groonga's geolocation search:
-
-* You list McDonald's around a station.
-* You list KFC around the current location sort by distance
-  from the current location in ascending order with distance.
-
-Here are not use cases:
-
-* You search McDonald's in a city. (Groonga doesn't support
-  geolocation search by a shape except a rectangle and a
-  circle.)
-* You store a region instead of a point as a lake
-  record. (A column can't has geolocation data except a
-  point.)
-
-The following figures show about Groonga's geolocation
-search features.
-
-Here is a figure that only has records. A black point
-describes a record. The following figures shows how records
-are treated.
-
-.. image:: /images/geo-points.png
-   :alt: only records
-
-
-Coming soon...
-

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

@@ -1,76 +0,0 @@
-.. -*- rst -*-
-
-.. highlightlang:: none
-
-.. groonga-command
-.. database: operations_prefix_rk_search
-
-Prefix RK search
-================
-
-Summary
--------
-
-Groonga supports prefix RK search. RK means Romaji and Kana (reading).
-Prefix RK search can find registered text in katakana by query in
-romaji, hiragana or katakana. Found registered texts are started with
-query.
-
-Prefix RK search is useful for completing Japanese text. Because
-romaji is widely used to input Japanese on computer. See also
-`Japanese input methods on Wikipedia
-<https://en.wikipedia.org/wiki/Japanese_input_methods>`_.
-
-If users can search Japanese text in romaji, users doesn't need to
-convert romaji to hiragana, katakana or kanji by themselves. For
-example, if you register a reading for "日本" as "ニホン", users can
-find "日本" by "ni", "に" or "二".
-
-The feature is helpful because it reduces one or more operations of
-users.
-
-This feature is used in :doc:`/reference/suggest/completion`.
-
-You can use this feature in :ref:`select-filter` by
-:doc:`/reference/functions/prefix_rk_search`.
-
-Usage
------
-
-You need :ref:`table-pat-key` table for using prefix RK search.
-
-You need to put reading in katakana to ``TABLE_PAT_KEY`` as key:
-
-.. groonga-command
-.. include:: ../../example/reference/operations/prefix_rk_search/usage_register_kana.log
-.. table_create Readings TABLE_PAT_KEY ShortText --normalizer NormalizerAuto
-.. load --table Readings
-.. [
-.. {"_key": "ニホン"},
-.. {"_key": "ニッポン"},
-.. {"_key": "ローマジ"}
-.. ]
-
-You can finds ``ニホン`` and ``ニッポン`` by prefix RK search with
-``ni`` as query from the ``Readings`` table.
-
-You can finds ``ローマジ`` by prefix RK search with ``r`` as query
-from the ``Readings`` table.
-
-How to convert romaji to reading
---------------------------------
-
-Prefix RK search is based on JIS X 4063:2000 specification.
-
-The specification was obsoleted. See `ローマ字入力 on Japanese
-Wikipedia
-<https://ja.wikipedia.org/wiki/%E3%83%AD%E3%83%BC%E3%83%9E%E5%AD%97%E5%85%A5%E5%8A%9B>`_
-for JIS X 4063:2000.
-
-Normally, you can get converted results as expected.
-
-See also
---------
-
-  * :doc:`/reference/suggest/completion`
-  * :doc:`/reference/functions/prefix_rk_search`

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

@@ -1,164 +0,0 @@
-.. -*- rst -*-
-
-.. highlightlang:: none
-
-Output
-======
-
-Groonga supports the following output format types:
-
-  * `JSON <http://www.json.org/>`_
-  * `XML <http://www.w3.org/XML/>`_
-  * TSV (Tab Separated Values)
-  * `MessagePack <http://msgpack.org/>`_
-
-JSON is the default output format.
-
-Usage
------
-
-Groonga has the following query interfaces:
-
-  * command line
-  * HTTP
-
-They provides different ways to change output format type.
-
-Command line
-^^^^^^^^^^^^
-
-You can use command line query interface by ``groonga
-DB_PATH`` or ``groonga -c``. Those groonga commands shows
-``>`` prompt. In this query interface, you can specify
-output format type by ``output_type`` option.
-
-If you don't specify ``output_type`` option, you will get
-a result in JSON format::
-
-  > status
-  [[0,1327721628.10738,0.000131845474243164],{"alloc_count":142,"starttime":1327721626,"uptime":2,"version":"1.2.9-92-gb87d9f8","n_queries":0,"cache_hit_rate":0.0,"command_version":1,"default_command_version":1,"max_command_version":2}]
-
-You can specify ``json`` as ``output_type`` value to get a
-result in JSON format explicitly::
-
-  > status --output_type json
-  [[0,1327721639.08321,7.93933868408203e-05],{"alloc_count":144,"starttime":1327721626,"uptime":13,"version":"1.2.9-92-gb87d9f8","n_queries":0,"cache_hit_rate":0.0,"command_version":1,"default_command_version":1,"max_command_version":2}]
-
-You need to specify ``xml`` as ``output_type`` value to
-get a result in XML format::
-
-  > status --output_type xml
-  <?xml version="1.0" encoding="utf-8"?>
-  <RESULT CODE="0" UP="1327721649.61095" ELAPSED="0.000126361846923828">
-  <RESULT>
-  <TEXT>alloc_count</TEXT>
-  <INT>146</INT>
-  <TEXT>starttime</TEXT>
-  <INT>1327721626</INT>
-  <TEXT>uptime</TEXT>
-  <INT>23</INT>
-  <TEXT>version</TEXT>
-  <TEXT>1.2.9-92-gb87d9f8</TEXT>
-  <TEXT>n_queries</TEXT>
-  <INT>0</INT>
-  <TEXT>cache_hit_rate</TEXT>
-  <FLOAT>0.0</FLOAT>
-  <TEXT>command_version</TEXT>
-  <INT>1</INT>
-  <TEXT>default_command_version</TEXT>
-  <INT>1</INT>
-  <TEXT>max_command_version</TEXT>
-  <INT>2</INT></RESULT>
-  </RESULT>
-
-You need to specify ``tsv`` as ``output_type`` value to
-get a result in TSV format::
-
-  > status --output_type tsv
-  0	1327721664.82675	0.000113964080810547
-  "alloc_count"	146
-  "starttime"	1327721626
-  "uptime"	38
-  "version"	"1.2.9-92-gb87d9f8"
-  "n_queries"	0
-  "cache_hit_rate"	0.0
-  "command_version"	1
-  "default_command_version"	1
-  "max_command_version"	2
-  END
-
-
-You need to specify ``msgpack`` as ``output_type`` value to
-get a result in MessagePack format::
-
-  > status --output_type msgpack
-  (... omitted because MessagePack is binary data format. ...)
-
-HTTP
-^^^^
-
-You can use HTTP query interface by ``groonga --protocol
-http -s DB_PATH``. Groonga HTTP server starts on port 10041
-by default. In this query interface, you can specify
-output format type by extension.
-
-If you don't specify extension, you will get a result in
-JSON format::
-
-  % curl http://localhost:10041/d/status
-  [[0,1327809294.54311,0.00082087516784668],{"alloc_count":155,"starttime":1327809282,"uptime":12,"version":"1.2.9-92-gb87d9f8","n_queries":0,"cache_hit_rate":0.0,"command_version":1,"default_command_version":1,"max_command_version":2}]
-
-You can specify ``json`` as extension to get a result in
-JSON format explicitly::
-
-  % curl http://localhost:10041/d/status.json
-  [[0,1327809319.01929,9.5367431640625e-05],{"alloc_count":157,"starttime":1327809282,"uptime":37,"version":"1.2.9-92-gb87d9f8","n_queries":0,"cache_hit_rate":0.0,"command_version":1,"default_command_version":1,"max_command_version":2}]
-
-You need to specify ``xml`` as extension to get a result in
-XML format::
-
-  % curl http://localhost:10041/d/status.xml
-  <?xml version="1.0" encoding="utf-8"?>
-  <RESULT CODE="0" UP="1327809339.5782" ELAPSED="9.56058502197266e-05">
-  <RESULT>
-  <TEXT>alloc_count</TEXT>
-  <INT>159</INT>
-  <TEXT>starttime</TEXT>
-  <INT>1327809282</INT>
-  <TEXT>uptime</TEXT>
-  <INT>57</INT>
-  <TEXT>version</TEXT>
-  <TEXT>1.2.9-92-gb87d9f8</TEXT>
-  <TEXT>n_queries</TEXT>
-  <INT>0</INT>
-  <TEXT>cache_hit_rate</TEXT>
-  <FLOAT>0.0</FLOAT>
-  <TEXT>command_version</TEXT>
-  <INT>1</INT>
-  <TEXT>default_command_version</TEXT>
-  <INT>1</INT>
-  <TEXT>max_command_version</TEXT>
-  <INT>2</INT></RESULT>
-  </RESULT>
-
-You need to specify ``tsv`` as extension to get a result in
-TSV format::
-
-  % curl http://localhost:10041/d/status.tsv
-  0	1327809366.84187	8.44001770019531e-05
-  "alloc_count"	159
-  "starttime"	1327809282
-  "uptime"	84
-  "version"	"1.2.9-92-gb87d9f8"
-  "n_queries"	0
-  "cache_hit_rate"	0.0
-  "command_version"	1
-  "default_command_version"	1
-  "max_command_version"	2
-  END
-
-You need to specify ``msgpack`` as extension to get a result
-in MessagePack format::
-
-  % curl http://localhost:10041/d/status.msgpack
-  (... omitted because MessagePack is binary data format. ...)

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

@@ -1,12 +0,0 @@
-.. -*- rst -*-
-
-.. highlightlang:: none
-
-Query expanders
-===============
-
-.. toctree::
-   :maxdepth: 1
-   :glob:
-
-   query_expanders/*

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

@@ -1,153 +0,0 @@
-.. -*- 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``::
-
-  plugin_register query_expanders/tsv
-
-Usage
------
-
-You just add ``--query_expander QueryExpanderTSV`` parameter to
-``select`` command::
-
-  select --query "QUERY" --query_expander 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_expander QueryExpanderTSV
-
-The above command equals to the following command::
-
-  select --query "groonga OR Senna" --query_expander QueryExpanderTSV
-
-Here is another example of query expnasion that uses ``mroonga
-search`` as query::
-
-  select --query "mroonga search" --query_expander QueryExpanderTSV
-
-The above command equals to the following command::
-
-  select --query "(mroonga OR (groonga MySQL)) search" --query_expander 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_expander QueryExpanderTSV
-
-The above command equals to the following command::
-
-  select --query "groonga" --query_expander 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:`select-query-expansion`