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

data/vendor/local/share/doc/groonga/en/html/_sources/tutorial/network.txt

@@ -1,64 +0,0 @@
-.. -*- rst -*-
-
-.. highlightlang:: none
-
-.. groonga-include : introduction.rst
-
-.. groonga-command
-.. database: tutorial
-
-Remote access
-=============
-
-You can use Groonga as a server which allows remote access. Groonga supports the original protocol (GQTP), the memcached binary protocol and HTTP.
-
-Hypertext transfer protocol (HTTP)
------------------------------------
-
-How to run an HTTP server
-^^^^^^^^^^^^^^^^^^^^^^^^^
-
-Groonga supports the hypertext transfer protocol (HTTP). The following form shows how to run Groonga as an HTTP server daemon.
-
-Form::
-
-  groonga [-p PORT_NUMBER] -d --protocol http DB_PATH
-
-The `--protocol` option and its argument specify the protocol of the server. "http" specifies to use HTTP. If the `-p` option is not specified, Groonga uses the default port number 10041.
-
-The following command runs an HTTP server that listens on the port number 80.
-
-Execution example::
-
-  % sudo groonga -p 80 -d --protocol http /tmp/groonga-databases/introduction.db
-  %
-
-.. note::
-   You must have root privileges if you listen on the port number 80 (well known port).
-   There is no such a limitation about the port number 1024 or over.
-
-How to send a command to an HTTP server
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-You can send a command to an HTTP server by sending a GET request to /d/COMMAND_NAME. Command parameters can be passed as parameters of the GET request. The format is "?NAME_1=VALUE_1&NAME_2=VALUE_2&...".
-
-The following example shows how to send commands to an HTTP server.
-
-.. groonga-command
-.. include:: ../example/tutorial/network-3.log
-.. .. http://HOST_NAME_OR_IP_ADDRESS[:PORT_NUMBER]/d/status
-.. .. Executed command:
-.. status
-.. .. http://HOST_NAME_OR_IP_ADDRESS[:PORT_NUMBER]/d/select?table=Site&query=title:@this
-.. .. Executed command:
-.. select --table Site --query title:@this
-
-Administration tool (HTTP)
---------------------------
-
-An HTTP server of Groonga provides a browser based administration tool that makes database management easy. After starting an HTTP server, you can use the administration tool by accessing http://HOST_NAME_OR_IP_ADDRESS[:PORT_NUMBER]/. Note that Javascript must be enabled for the tool to work properly.
-
-Security issues
----------------
-
-Groonga servers don't support user authentication. Everyone can view and modify databases hosted by Groonga servers. You are recommended to restrict IP addresses that can access Groonga servers. You can use iptables or similar for this purpose.

data/vendor/local/share/doc/groonga/en/html/_sources/tutorial/patricia_trie.txt

@@ -1,58 +0,0 @@
-.. -*- rst -*-
-
-.. highlightlang:: none
-
-.. groonga-command
-.. database: tutorial-patricia-trie
-
-Prefix search with patricia trie
-================================
-
-Groonga supports to create a table with patricia trie option.
-By specifying it, You can do prefix search.
-
-And more, you can do suffix search against primary key by specifying additional option.
-
-Prefix search by primary key
-----------------------------
-
-table_create command which uses TABLE_PAT_KEY for flags option supports prefix search by primary key.
-
-.. groonga-command
-.. include:: ../example/tutorial/patricia_trie_prefix_search.log
-..
-.. table_create --name PatPrefix --flags TABLE_PAT_KEY --key_type ShortText
-.. load --table PatPrefix
-.. [
-.. {"_key":"James"}
-.. {"_key":"Jason"}
-.. {"_key":"Jennifer"},
-.. {"_key":"Jeff"},
-.. {"_key":"John"},
-.. {"_key":"Joseph"},
-.. ]
-.. select --table PatPrefix --query _key:^Je
-
-Suffix search by primary key
-----------------------------
-
-table_create command which uses TABLE_PAT_KEY and KEY_WITH_SIS for flags option supports prefix search and suffix search by primary key.
-
-If you set KEY_WITH_SIS flag, suffix search records also are added when you add the data. So if you search simply, the automatically added records are hit in addition to the original records. In order to search only the original records, you need a plan.
-
-For example, in order to make this distinction between the original records and automatically added records, add the original column indicating that it is the original record, and add original column is ``true`` to the search condition. For attention, use ``--filter`` option because ``--query`` option is not specify ``Bool`` type value intuitively.
-
-.. groonga-command
-.. include:: ../example/tutorial/patricia_trie-2.log
-..
-.. table_create --name PatSuffix --flags TABLE_PAT_KEY|KEY_WITH_SIS --key_type ShortText
-.. column_create --table PatSuffix --name original --type Bool
-.. load --table PatSuffix
-.. [
-.. {"_key":"ひろゆき","original":true},
-.. {"_key":"まろゆき","original":true},
-.. {"_key":"ひろあき","original":true},
-.. {"_key":"ゆきひろ","original":true}
-.. ]
-.. select --table PatSuffix --query _key:$ゆき
-.. select --table PatSuffix --filter '_key @$ "ゆき" && original == true'

data/vendor/local/share/doc/groonga/en/html/_sources/tutorial/query_expansion.txt

@@ -1,69 +0,0 @@
-.. -*- rst -*-
-
-.. highlightlang:: none
-
-.. groonga-command
-.. database: tutorial-query-expansion
-
-Query expansion
-===============
-
-Groonga accepts ``query_expander`` parameter for :doc:`/reference/commands/select` command.
-It enables you to extend your query string.
-
-For example, if user searches "theatre" instead of "theater",
-query expansion enables to return search results of "theatre OR theater".
-This kind of way reduces search leakages. This is what really user wants.
-
-Preparation
------------
-
-To use query expansion, you need to create table which stores documents, synonym table which stores query string and replacement string.
-In synonym table, primary key represents original string, the column of ShortText represents modified string.
-
-.. TODO: 文字列型のベクターカラムでも可能であり、その場合は各要素をORでつなげたものに置換されるということを記述する。
-
-Let's create document table and synonym table.
-
-.. groonga-command
-.. include:: ../example/tutorial/query_expansion-1.log
-.. table_create Doc TABLE_PAT_KEY ShortText
-.. column_create Doc body COLUMN_SCALAR ShortText
-.. table_create Term TABLE_PAT_KEY ShortText --default_tokenizer TokenBigram --normalizer NormalizerAuto
-.. column_create Term Doc_body COLUMN_INDEX|WITH_POSITION Doc body
-.. table_create Synonym TABLE_PAT_KEY ShortText
-.. column_create Synonym body COLUMN_VECTOR ShortText
-.. load --table Doc
-.. [
-.. {"_key": "001", "body": "Play all night in this theater."},
-.. {"_key": "002", "body": "theatre is British spelling."},
-.. ]
-.. load --table Synonym
-.. [
-.. {"_key": "theater", "body": ["theater", "theatre"]},
-.. {"_key": "theatre", "body": ["theater", "theatre"]},
-.. ]
-
-In this case, it doesn't occur search leakage because it creates synonym table which accepts "theatre" and "theater" as query string.
-
-Search
-------
-
-Then, let's use prepared synonym table.
-First, use select command without ``query_expander`` parameter.
-
-.. groonga-command
-.. include:: ../example/tutorial/query_expansion-2.log
-.. select Doc --match_columns body --query "theater"
-.. select Doc --match_columns body --query "theatre"
-
-Above query returns the record which completely equal to query string.
-
-Then, use ``query_expander`` parameter against ``body`` column of ``Synonym`` table.
-
-.. groonga-command
-.. include:: ../example/tutorial/query_expansion-3.log
-.. select Doc --match_columns body --query "theater" --query_expander Synonym.body
-.. select Doc --match_columns body --query "theatre" --query_expander Synonym.body
-
-In which cases, query string is replaced to "(theater OR theatre)", thus synonym is considered for full text search.

data/vendor/local/share/doc/groonga/en/html/_sources/tutorial/search.txt

@@ -1,123 +0,0 @@
-.. -*- rst -*-
-
-.. highlightlang:: none
-
-.. groonga-include : data.rst
-
-.. groonga-command
-.. database: tutorial
-
-Various search conditions
-=========================
-
-Groonga supports to narrow down by using syntax like JavaScript, sort by the calculated value. Additionally, Groonga also supports to narrow down & sort search results by using location information (latitude & longitude).
-
-Narrow down & Full-text search by using syntax like JavaScript
---------------------------------------------------------------
-
-The ``filter`` parameter of ``select`` command accepts the search condition.
-There is one difference between ``filter`` parameter and ``query`` parameter, you need to specify the condition by syntax like JavaScript for ``filter`` parameter.
-
-.. groonga-command
-.. include:: ../example/tutorial/search-1.log
-.. select --table Site --filter "_id <= 1" --output_columns _id,_key
-
-See the detail of above query. Here is the condition which is specified as ``filter`` parameter::
-
-  _id <= 1
-
-In this case, this query returns the records which meets the condition that the value of ``_id`` is equal to or less than 1.
-
-Moreover, you can use ``&&`` for AND search, ``||`` for OR search.
-
-.. groonga-command
-.. include:: ../example/tutorial/search-2.log
-.. select --table Site --filter "_id >= 4 && _id <= 6" --output_columns _id,_key
-.. select --table Site --filter "_id <= 2 || _id >= 7" --output_columns _id,_key
-
-If you specify ``query`` parameter and ``filter`` parameter at the same time, you can get the records which meets both of the condition as a result.
-
-Sort by using ``scorer``
-------------------------
-
-``select`` command accepts ``scorer`` parameter which is used to process each record of full-text search results.
-
-This parameter accepts the conditions which is specified by syntax like JavaScript as same as ``filter`` parameter.
-
-.. groonga-command
-.. include:: ../example/tutorial/search-3.log
-.. select --table Site --filter "true" --scorer "_score = rand()" --output_columns _id,_key,_score --sortby _score
-.. select --table Site --filter "true" --scorer "_score = rand()" --output_columns _id,_key,_score --sortby _score
-
-'_score' is one of a pseudo column. The score of full-text search is assigned to it.
-See :doc:`/reference/columns/pseudo` about '_score' column.
-
-In the above query, the condition of ``scorer`` parameter is::
-
-  _score = rand()
-
-In this case, the score of full-text search is overwritten by the value of rand() function.
-
-The condition of ``sortby`` parameter is::
-
-  _score
-
-This means that sorting the search result by ascending order.
-
-As a result, the order of search result is randomized.
-
-Narrow down & sort by using location information
-------------------------------------------------
-
-Groonga supports to store location information (Longitude & Latitude) and not only narrow down but also sort by using it.
-
-Groonga supports two kind of column types to store location information. One is ``TokyoGeoPoint``, the other is ``WGS84GeoPoint``. ``TokyoGeoPoint`` is used for Japan geodetic system. ``WGS84GeoPoint`` is used for world geodetic system.
-
-Specify longitude and latitude as follows:
-
-* "[latitude in milliseconds]x[longitude in milliseconds]"（e.g.: "128452975x503157902"）
-* "[latitude in milliseconds],[longitude in milliseconds]"（e.g.: "128452975,503157902"）
-* "[latitude in degrees]x[longitude in degrees]"（e.g.: "35.6813819x139.7660839"）
-* "[latitude in degrees],[longitude in degrees]"（e.g.: "35.6813819,139.7660839"）
-
-Let's store two location information about station in Japan by WGS. One is Tokyo station, the other is Shinjyuku station. Both of them are station in Japan. The latitude of Tokyo station is 35 degrees 40 minutes 52.975 seconds, the longitude of Tokyo station is 139 degrees 45 minutes 57.902 seconds. The latitude of Shinjyuku station is  35 degrees 41 minutes  27.316 seconds, the longitude of Shinjyuku station is 139 degrees 42 minutes 0.929 seconds. Thus, location information in milliseconds are "128452975x503157902" and "128487316x502920929" respectively. location information in degrees are  "35.6813819x139.7660839" and "35.6909211x139.7002581" respectively.
-
-Let's register location information in milliseconds.
-
-.. groonga-command
-.. include:: ../example/tutorial/search-4.log
-.. column_create --table Site --name location --type WGS84GeoPoint
-.. load --table Site
-.. [
-..  {"_key":"http://example.org/","location":"128452975x503157902"}
-..  {"_key":"http://example.net/","location":"128487316x502920929"},
-.. ]
-.. select --table Site --query "_id:1 OR _id:2" --output_columns _key,location
-
-Then assign the value of geo distance which is calculated by :doc:`/reference/functions/geo_distance` function to ``scorer`` parameter.
-
-Let's show geo distance from Akihabara station in Japan. In world geodetic system, the latitude of Akihabara station is  35 degrees 41 minutes 55.259 seconds, the longitude of Akihabara station is 139 degrees 46 minutes 27.188 seconds. Specify "128515259x503187188" for geo_distance function.
-
-.. groonga-command
-.. include:: ../example/tutorial/search-5.log
-.. select --table Site --query "_id:1 OR _id:2" --output_columns _key,location,_score --scorer '_score = geo_distance(location, "128515259x503187188")'
-
-As you can see, the geo distance between Tokyo station and Akihabara station is 2054 meters, the geo distance between Akihabara station and Shinjyuku station is 6720 meters.
-
-The return value of geo_distance function is also used for sorting by specifying pseudo ``_score`` column to ``sortby`` parameter.
-
-.. groonga-command
-.. include:: ../example/tutorial/search-6.log
-.. select --table Site --query "_id:1 OR _id:2" --output_columns _key,location,_score --scorer '_score = geo_distance(location, "128515259x503187188")' --sortby -_score
-
-Groonga also supports to narrow down by "a certain point within specified meters".
-
-In such a case, use :doc:`/reference/functions/geo_in_circle` function in ``filter`` parameter.
-
-For example, search the records which exists within 5000 meters from Akihabara station.
-
-.. groonga-command
-.. include:: ../example/tutorial/search-7.log
-.. select --table Site --output_columns _key,location --filter 'geo_in_circle(location, "128515259x503187188", 5000)'
-
-There is :doc:`/reference/functions/geo_in_rectangle` function which is used to search a certain point within specified region.

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

@@ -1,70 +0,0 @@
-.. -*- rst -*-
-.. Groonga project
-
-.. highlightlang:: none
-
-Characteristics of Groonga
-==========================
-
-Groonga overview
-----------------
-
-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.
-
-The basic functions of Groonga are provided in a C library. Also, libraries for using Groonga in other languages, such as Ruby, are provided by related projects. In addition, groonga-based storage engines are provided for MySQL and PostgreSQL. These libraries and storage engines allow any application to use Groonga. See `usage examples <http://groonga.org/users/>`_.
-
-Full text search and Instant update
------------------------------------
-
-In widely used DBMSs, updates are immediately processed, for example, a newly registered record appears in the result of the next query. In contrast, some full text search engines do not support instant updates, because it is difficult to dynamically update inverted indexes, the underlying data structure.
-
-Groonga also uses inverted indexes but supports instant updates. In addition, Groonga allows you to search documents even when updating the document collection. Due to these superior characteristics, Groonga is very flexible as a full text search engine. Also, Groonga always shows good performance because it divides a large task, inverted index merging, into smaller tasks.
-
-Column store and aggregate query
---------------------------------
-
-People can collect more than enough data in the Internet era. However, it is difficult to extract informative knowledge from a large database, and such a task requires a many-sided analysis through trial and error. For example, search refinement by date, time and location may reveal hidden patterns. Aggregate queries are useful to perform this kind of tasks.
-
-An aggregate query groups search results by specified column values and then counts the number of records in each group. For example, an aggregate query in which a location column is specified counts the number of records per location. Making a graph from the result of an aggregate query against a date column is an easy way to visualize changes over time. Also, a combination of refinement by location and an aggregate query against a date column allows visualization of changes over time in specific location. Thus refinement and aggregation are important to perform data mining.
-
-A column-oriented architecture allows Groonga to efficiently process aggregate queries because a column-oriented database, which stores records by column, allows an aggregate query to access only a specified column. On the other hand, an aggregate query on a row-oriented database, which stores records by row, has to access neighbor columns, even though those columns are not required.
-
-Inverted index and tokenizer
-----------------------------
-
-An inverted index is a traditional data structure used for large-scale full text search. A search engine based on inverted index extracts index terms from a document when it is added. Then in retrieval, a query is divided into index terms to find documents containing those index terms. In this way, index terms play an important role in full text search and thus the way of extracting index terms is a key to a better search engine.
-
-A tokenizer is a module to extract index terms. A Japanese full text search engine commonly uses a word-based tokenizer (hereafter referred to as a word tokenizer) and/or a character-based n-gram tokenizer (hereafter referred to as an n-gram tokenizer). A word tokenizer-based search engine is superior in time, space and precision, which is the fraction of relevant documents in a search result. On the other hand, an n-gram tokenizer-based search engine is superior in recall, which is the fraction of retrieved documents in the perfect search result. The best choice depends on the application in practice.
-
-Groonga supports both word and n-gram tokenizers. The simplest built-in tokenizer uses spaces as word delimiters. Built-in n-gram tokenizers (n = 1, 2, 3) are also available by default. In addition, a yet another built-in word tokenizer is available if MeCab, a part-of-speech and morphological analyzer, is embedded. Note that a tokenizer is pluggable and you can develop your own tokenizer, such as a tokenizer based on another part-of-speech tagger or a named-entity recognizer.
-
-Sharable storage and read lock-free
------------------------------------
-
-Multi-core processors are mainstream today and the number of cores per processor is increasing. In order to exploit multiple cores, executing multiple queries in parallel or dividing a query into sub-queries for parallel processing is becoming more important.
-
-A database of Groonga can be shared with multiple threads/processes. Also, multiple threads/processes can execute read queries in parallel even when another thread/process is executing an update query because Groonga uses read lock-free data structures. This feature is suited to a real-time application that needs to update a database while executing read queries. In addition, Groonga allows you to build flexible systems. For example, a database can receive read queries through the built-in HTTP server of Groonga while accepting update queries through MySQL.
-
-Geo-location (latitude and longitude) search
---------------------------------------------
-
-Location services are getting more convenient because of mobile devices with GPS. For example, if you are going to have lunch or dinner at a nearby restaurant, a local search service for restaurants may be very useful, and for such services, fast geo-location search is becoming more important.
-
-Groonga provides inverted index-based fast geo-location search, which supports a query to find points in a rectangle or circle. Groonga gives high priority to points near the center of an area. Also, Groonga supports distance measurement and you can sort points by distance from any point.
-
-Groonga library
----------------
-
-The basic functions of Groonga are provided in a C library and any application can use Groonga as a full text search engine or a column-oriented database. Also, libraries for languages other than C/C++, such as Ruby, are provided in related projects. See `related projects <http://groonga.org/related-projects.html>`_ for details.
-
-Groonga server
---------------
-
-Groonga provides a built-in server command which supports HTTP, the memcached binary protocol and the Groonga Query Transfer Protocol (:doc:`/spec/gqtp`). Also, a Groonga server supports query caching, which significantly reduces response time for repeated read queries. Using this command, Groonga is available even on a server that does not allow you to install new libraries.
-
-Mroonga storage engine
-----------------------
-
-Groonga works not only as an independent column-oriented DBMS but also as storage engines of well-known DBMSs. For example, `Mroonga <http://mroonga.org/>`_ is a MySQL pluggable storage engine using Groonga. By using Mroonga, you can use Groonga for column-oriented storage and full text search. A combination of a built-in storage engine, MyISAM or InnoDB, and a Groonga-based full text search engine is also available. All the combinations have good and bad points and the best one depends on the application. See `related projects <http://groonga.org/related-projects.html>`_ for details.

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

@@ -1,19 +0,0 @@
-.. -*- rst -*-
-.. Groonga Project
-
-.. highlightlang:: none
-
-Client
-======
-
-Groonga supports the original protocol (:doc:`/spec/gqtp`), the memcached
-binary protocol and HTTP.
-
-As HTTP and memcached binary protocol is matured protocol, you can use
-existing client libraries.
-
-There are some client libraries which provides convenient API to connect
-to Groonga server in some program languages. See `Client libraries
-<http://groonga.org/related-projects.html#libraries>`_ for details.
-
-

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

@@ -1,49 +0,0 @@
-.. -*- rst -*-
-.. Groonga Project
-
-.. highlightlang:: none
-
-Community
-=========
-
-There are some places for sharing Groonga information.
-We welcome you to join our community.
-
-Mailing List
-------------
-
-There are mailing lists for discussion about Groonga.
-
-For English speakers
-  `groonga-talk@lists.sourceforge.net <http://lists.sourceforge.net/mailman/listinfo/groonga-talk>`_
-
-For Japanese speakers
-  `groonga-dev@lists.osdn.me <http://lists.osdn.me/mailman/listinfo/groonga-dev>`_
-
-Chat room
----------
-
-There are chat rooms for discussion about Groonga.
-
-For English speakers
-  `groonga/en chat room on Gitter <https://gitter.im/groonga/en>`_
-
-For Japanese speakers
-  `groonga/ja chat room on Gitter <https://gitter.im/groonga/ja>`_
-
-Twitter
--------
-
-`@groonga <https://twitter.com/groonga/>`_ tweets Groonga related
-information.
-
-Please follow the account to get the latest Groonga related
-information!
-
-Facebook
---------
-
-`Groonga page on Facebook <http://www.facebook.com/groonga>`_ shares
-Groonga related information.
-
-Please like the page to get the latest Groonga related information!