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

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

@@ -1,45 +0,0 @@
-.. -*- rst -*-
-
-.. highlightlang:: none
-
-How to avoid mmap Cannot allocate memory error
-==============================================
-
-Example
--------
-
-There is a case following mmap error in log file:
-
-  2013-06-04 08:19:34.835218|A|4e86e700|mmap(4194304,551,432017408)=Cannot allocate memory <13036498944>
-
-Note that <13036498944> means total size of mmap (almost 12GB) in this case.
-
-Solution
---------
-
-So you need to confirm following point of views.
-
-* Are there enough free memory?
-* Are maximum number of mappings exceeded?
-
-To check there are enough free memory, you can use vmstat command.
-
-To check whether maximum number of mappings are exceeded, you can investigate the value of vm.max_map_count.
-
-If this issue is fixed by modifying the value of vm.max_map_count, it's exactly the reason.
-
-As groonga allocates memory chunks each 256KB, you can estimate the size of database you can handle by following formula:
-
-  (database size) = vm.max_map_count * (memory chunks)
-
-If you want to handle over 16GB groonga database, you must specify at least 65536 as the value of vm.max_map_count:
-
-  database size (16GB) = vm.max_map_count (65536) * memory chunks (256KB)
-
-You can modify vm.max_map_count temporary by sudo sysctl -w vm.max_map_count=65536.
-
-Then save the configuration value to ``/etc/sysctl.conf`` or ``/etc/sysctl.d/*.conf``.
-
-See :doc:`/reference/tuning` documentation about tuning related parameters.
-
-

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

@@ -1,22 +0,0 @@
-.. -*- rst -*-
-.. Groonga Project
-
-.. highlightlang:: none
-
-Tutorial
-========
-
-.. toctree::
-   :maxdepth: 2
-
-   tutorial/introduction
-   tutorial/network
-   tutorial/data
-   tutorial/search
-   tutorial/drilldown
-   tutorial/index
-   tutorial/match_columns
-   tutorial/patricia_trie
-   tutorial/lexicon
-   tutorial/micro_blog
-   tutorial/query_expansion

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

@@ -1,173 +0,0 @@
-.. -*- rst -*-
-
-.. highlightlang:: none
-
-.. groonga-include : introduction.rst
-
-.. groonga-command
-.. database: tutorial
-
-Various data types
-==================
-
-Groonga is a full text search engine but also serves as a column-oriented data store. Groonga supports various data types, such as numeric types, string types, date and time type, longitude and latitude types, etc. This tutorial shows a list of data types and explains how to use them.
-
-Overview
---------
-
-The basic data types of Groonga are roughly divided into 5 groups --- boolean type, numeric types, string types, date/time type and longitude/latitude types. The numeric types are further divided according to whether integer or floating point number, signed or unsigned and the number of bits allocated to each integer. The string types are further divided according to the maximum length. The longitude/latitude types are further divided according to the geographic coordinate system. For more details, see :doc:`/reference/types`.
-
-In addition, Groonga supports reference types and vector types. Reference types are designed for accessing other tables. Vector types are designed for storing a variable number of values in one element.
-
-First, let's create a table for this tutorial.
-
-.. groonga-command
-.. include:: ../example/tutorial/data-1.log
-.. table_create --name ToyBox --flags TABLE_HASH_KEY --key_type ShortText
-
-Boolean type
-------------
-
-The boolean type is used to store true or false. To create a boolean type column, specify Bool to the `type` parameter of :doc:`/reference/commands/column_create` command. The default value of the boolean type is false.
-
-The following example creates a boolean type column and adds three records. Note that the third record has the default value because no value is specified.
-
-.. groonga-command
-.. include:: ../example/tutorial/data-2.log
-.. column_create --table ToyBox --name is_animal --type Bool
-.. load --table ToyBox
-.. [
-.. {"_key":"Monkey","is_animal":true}
-.. {"_key":"Flower","is_animal":false}
-.. {"_key":"Block"}
-.. ]
-.. select --table ToyBox --output_columns _key,is_animal
-
-Numeric types
--------------
-
-The numeric types are divided into integer types and a floating point number type. The integer types are further divided into the signed integer types and unsigned integer types. In addition, you can choose the number of bits allocated to each integer. For more details, see :doc:`/reference/types`. The default value of the numeric types is 0.
-
-The following example creates an Int8 column and a Float column, and then updates existing records. The :doc:`/reference/commands/load` command updates the weight column as expected. On the other hand, the price column values are different from the specified values because 15.9 is not an integer and 200 is too large. 15.9 is converted to 15 by removing the fractional part. 200 causes an overflow and the result becomes -56. Note that the result of an overflow/underflow is undefined.
-
-.. groonga-command
-.. include:: ../example/tutorial/data-3.log
-.. column_create --table ToyBox --name price --type Int8
-.. column_create --table ToyBox --name weight --type Float
-.. load --table ToyBox
-.. [
-.. {"_key":"Monkey","price":15.9}
-.. {"_key":"Flower","price":200,"weight":0.13}
-.. {"_key":"Block","weight":25.7}
-.. ]
-.. select --table ToyBox --output_columns _key,price,weight
-
-String types
-------------
-
-The string types are divided according to the maximum length. For more details, see :doc:`/reference/types`. The default value is the zero-length string.
-
-The following example creates a ``ShortText`` column and updates
-existing records. The third record (``"Block"`` key record) has the
-default value (zero-length string) because it's not updated.
-
-.. groonga-command
-.. include:: ../example/tutorial/data-4.log
-.. column_create --table ToyBox --name name --type ShortText
-.. load --table ToyBox
-.. [
-.. {"_key":"Monkey","name":"Grease"}
-.. {"_key":"Flower","name":"Rose"}
-.. ]
-.. select --table ToyBox --output_columns _key,name
-
-Date and time type
-------------------
-
-The date and time type of Groonga is Time. Actually, a Time column stores a date and time as the number of microseconds since the Epoch, 1970-01-01 00:00:00. A Time value can represent a date and time before the Epoch because the actual data type is a signed integer. Note that :doc:`/reference/commands/load` and :doc:`/reference/commands/select` commands use a decimal number to represent a data and time in seconds. The default value is 0.0, which means the Epoch.
-
-.. note::
-
-   Groonga internally holds the value of Epoch as pair of integer. The first integer represents the value of seconds, on the other hand, the second integer represents the value of micro seconds.
-   So, Groonga shows the value of Epoch as floating point. Integral part means the value of seconds, fraction part means the value of micro seconds.
-
-The following example creates a ``Time`` column and updates existing
-records. The first record (``"Monkey"`` key record) has the default
-value (``0.0``) because it's not updated.
-
-.. groonga-command
-.. include:: ../example/tutorial/data-5.log
-.. column_create --table ToyBox --name time --type Time
-.. load --table ToyBox
-.. [
-.. {"_key":"Flower","time":1234567890.1234569999}
-.. {"_key":"Block","time":-1234567890}
-.. ]
-.. select --table ToyBox --output_columns _key,time
-
-Longitude and latitude types
-----------------------------
-
-The longitude and latitude types are divided according to the geographic coordinate system. For more details, see :doc:`/reference/types`. To represent a longitude and latitude, Groonga uses a string formatted as follows:
-
-* "longitude x latitude" in milliseconds (e.g.: "128452975x503157902")
-* "longitude x latitude" in degrees (e.g.: "35.6813819x139.7660839")
-
-A number with/without a decimal point represents a longitude or latitude in milliseconds/degrees respectively. Note that a combination of a number with a decimal point and a number without a decimal point (e.g. 35.1x139) must not be used. A comma (',') is also available as a delimiter. The default value is "0x0".
-
-The following example creates a ``WGS84GeoPoint`` column and updates
-existing records. The second record (``"Flower"`` key record) has the
-default value (``"0x0"``) because it's not updated.
-
-.. groonga-command
-.. include:: ../example/tutorial/data-6.log
-.. column_create --table ToyBox --name location --type WGS84GeoPoint
-.. load --table ToyBox
-.. [
-.. {"_key":"Monkey","location":"128452975x503157902"}
-.. {"_key":"Block","location":"35.6813819x139.7660839"}
-.. ]
-.. select --table ToyBox --output_columns _key,location
-
-Reference types
----------------
-
-Groonga supports a reference column, which stores references to records in its associated table. In practice, a reference column stores the IDs of the referred records in the associated table and enables access to those records.
-
-You can specify a column in the associated table to the ``output_columns`` parameter of a :doc:`/reference/commands/select` command. The format is ``Src.Dest`` where Src is the name of the reference column and Dest is the name of the target column. If only the reference column is specified, it is handled as ``Src._key``. Note that if a reference does not point to a valid record, a :doc:`/reference/commands/select` command outputs the default value of the target column.
-
-The following example adds a reference column to the ``Site`` table
-that was created in :ref:`tutorial-introduction-create-table`. The new
-column, named ``link``, is designed for storing links among records in
-the ``Site`` table.
-
-.. groonga-command
-.. include:: ../example/tutorial/data-7.log
-.. column_create --table Site --name link --type Site
-.. load --table Site
-.. [
-.. {"_key":"http://example.org/","link":"http://example.net/"}
-.. ]
-.. select --table Site --output_columns _key,title,link._key,link.title --query title:@this
-
-The `type` parameter of the :doc:`/reference/commands/column_create` command specifies the table to be associated with the reference column. In this example, the reference column is associated with the own table. Then, the :doc:`/reference/commands/load` command registers a link from "http://example.org" to "http://example.net". Note that a reference column requires the primary key, not the ID, of the record to be referred to. After that, the link is confirmed by the :doc:`/reference/commands/select` command. In this case, the primary key and the title of the referred record are output because link._key and link.title are specified to the `output_columns` parameter.
-
-Vector types
-------------
-
-Groonga supports a vector column, in which each element can store a variable number of values. To create a vector column, specify the COLUMN_VECTOR flag to the `flags` parameter of a :doc:`/reference/commands/column_create` command. A vector column is useful to represent a many-to-many relationship.
-
-The previous example used a regular column, so each record could have at most one link. Obviously, the specification is insufficient because a site usually has more than one links. To solve this problem, the following example uses a vector column.
-
-.. FIXME: _idの配列ではダメなのかどうか。検証する。
-
-.. groonga-command
-.. include:: ../example/tutorial/data-8.log
-.. column_create --table Site --name links --flags COLUMN_VECTOR --type Site
-.. load --table Site
-.. [
-.. {"_key":"http://example.org/","links":["http://example.net/","http://example.org/","http://example.com/"]},
-.. ]
-.. select --table Site --output_columns _key,title,links._key,links.title --query title:@this
-
-The only difference at the first step is the `flags` parameter that specifies to create a vector column. The `type` parameter of the :doc:`/reference/commands/column_create` command is the same as in the previous example. Then, the :doc:`/reference/commands/load` command registers three links from "http://example.org/" to "http://example.net/", "http://example.org/" and "http://example.com/". After that, the links are confirmed by the :doc:`/reference/commands/select` command. In this case, the primary keys and the titles are output as arrays because links._key and links.title are specified to the `output_columns` parameter.

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

@@ -1,130 +0,0 @@
-.. -*- rst -*-
-.. Groonga Project
-
-.. highlightlang:: none
-
-.. groonga-include : search.rst
-
-.. groonga-command
-.. database: tutorial
-
-Drilldown
-=========
-
-You learned how to search and sort searched results in the previous sections.
-Now that you can search as you likes, but how do you summarize the number of records which has specific value in the column?
-
-As you know, there is a naive solution to execute query by every the value of column, then you can get the number of records as a result. It is a simple way, but it is not reasonable to many records.
-
-If you are familiar with SQL, you will doubt with "Is there a similar SQL functionality to ``GROUP BY`` in Groonga?".
-
-Of course, Groonga provides such a functionality. It's called as ``drilldown``.
-
-``drilldown`` enables you to get the number of records which belongs to specific the value of column at once.
-
-To illustrate this feature, imagine the case that classification by domain and grouping by country that domain belongs to.
-
-Here is the concrete examples how to use this feature.
-
-In this example, we add two columns to ``Site`` table. ``domain`` column is used for TLD (top level domain). ``country`` column is used for country name. The type of these columns are ``SiteDomain`` table which uses domain name as a primary key and ``SiteCountry`` table which uses country name as a primary key.
-
-.. groonga-command
-.. include:: ../example/tutorial/drilldown-1.log
-.. table_create --name SiteDomain --flags TABLE_HASH_KEY --key_type ShortText
-.. table_create --name SiteCountry --flags TABLE_HASH_KEY --key_type ShortText
-.. column_create --table Site --name domain --flags COLUMN_SCALAR --type SiteDomain
-.. column_create --table Site --name country --flags COLUMN_SCALAR --type SiteCountry
-.. load --table Site
-.. [
-.. {"_key":"http://example.org/","domain":".org","country":"japan"},
-.. {"_key":"http://example.net/","domain":".net","country":"brazil"},
-.. {"_key":"http://example.com/","domain":".com","country":"japan"},
-.. {"_key":"http://example.net/afr","domain":".net","country":"usa"},
-.. {"_key":"http://example.org/aba","domain":".org","country":"korea"},
-.. {"_key":"http://example.com/rab","domain":".com","country":"china"},
-.. {"_key":"http://example.net/atv","domain":".net","country":"china"},
-.. {"_key":"http://example.org/gat","domain":".org","country":"usa"},
-.. {"_key":"http://example.com/vdw","domain":".com","country":"japan"}
-.. ]
-
-Here is a example of drilldown with ``domain`` column. Three kind of values are used in ``domain`` column - ".org", ".net" and ".com".
-
-.. groonga-command
-.. include:: ../example/tutorial/drilldown-domain.log
-.. select --table Site --limit 0 --drilldown domain
-
-
-Here is a summary of above query.
-
-.. list-table:: Drilldown by ``domain`` column
-   :header-rows: 1
-
-   * - Group by
-     - The number of group records
-     - Group records means following records
-   * - .org
-     - 3
-     - * http://example.org/
-       * http://example.org/aba
-       * http://example.org/gat
-   * - .net
-     - 3
-     - * http://example.net/
-       * http://example.net/afr
-       * http://example.net/atv
-   * - .com
-     - 3
-     - * http://example.com/
-       * http://example.com/rab
-       * http://example.com/vdw
-
-
-The value of drilldown are returned as the value of ``_nsubrecs`` column. In this case, ``Site`` table is grouped by ".org", ".net", ".com" domain. ``_nsubrecs`` shows that each three domain has three records.
-
-If you execute drildown to the column which has table as a type, you can get the value of column which is stored in referenced table.
-``_nsubrecs`` pseudo column is added to the table which is used for drilldown. this pseudo column stores the number of records which is grouped by.
-
-Then, investigate referenced table in detail. As ``Site`` table use ``SiteDomain`` table as column type of ``domain``, you can use ``--drilldown_output_columns`` to know detail of referenced column.
-
-.. groonga-command
-.. include:: ../example/tutorial/drilldown-output-columns.log
-.. select --table Site --limit 0 --drilldown domain --drilldown_output_columns _id,_key,_nsubrecs
-
-Now, you can see detail of each grouped domain, drilldown by ``country`` column which has ".org" as column value.
-
-.. groonga-command
-.. include:: ../example/tutorial/drilldown-country.log
-.. select --table Site --limit 0 --filter "domain._id == 1" --drilldown country
-
-Drilldown with multiple column
-------------------------------
-
-Drilldown feature supports multiple column. Use comma separated multiple column names as ``drildown`` parameter.
-You can get the each result of drilldown at once.
-
-.. groonga-command
-.. include:: ../example/tutorial/drilldown-multiple-column.log
-.. select --table Site --limit 0 --drilldown domain,country
-
-
-Sorting drildown results
-------------------------
-
-Use ``--drilldown_sortby`` if you want to sort the result of drilldown. For example, specify ``_nsubrecs`` as ascending order.
-
-.. groonga-command
-.. include:: ../example/tutorial/drilldown-sortby.log
-.. select --table Site --limit 0 --drilldown country --drilldown_sortby _nsubrecs
-
-
-limits drildown results
-------------------------
-
-The number of drilldown results is limited to 10 as a default. Use ``drilldown_limit`` and ``drilldown_offset`` parameter to customize orilldown results.
-
-.. groonga-command
-.. include:: ../example/tutorial/drilldown-limit.log
-.. select --table Site --limit 0 --drilldown country --drilldown_sortby _nsubrecs --drilldown_limit 2 --drilldown_offset 2
-
-Note that drilldown to the column which stores string is slower than the columns which stores the other types.
-If you drilldown to string type of column, create the table that type of primary key is string, then create the column which refers that table.

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

@@ -1,123 +0,0 @@
-.. -*- rst -*-
-
-.. highlightlang:: none
-
-.. groonga-include : drilldown.rst
-
-.. groonga-command
-.. database: tutorial
-
-Tag search and reverse resolution of reference relationships
-============================================================
-
-As you know, Groonga supports to store array in column which refers other table.
-In fact, you can do tag search by using array data which refers other table.
-
-Tag search is very fast because Groonga use inverted index as data structure.
-
-Tag search
-----------
-
-Let's consider to create a search engine for an web site to share movies. Each movie may be associated with multiple keywords which represents the content of movie.
-
-Let's create tables for movie information, then search the movies.
-
-First, create the ``Video`` table which stores movie information. the ``Video`` table has two columns. the ``title`` column stores title of the movie. the ``tags`` column stores multiple tag information in reference Tag table.
-
-Next, create the ``Tag`` table which stores tag information. the ``Tag`` table has one column. The tag string is stored as primary key, then ``index_tags`` stores indexes for tags column of Video table.
-
-.. groonga-command
-.. include:: ../example/tutorial/index-1.log
-.. table_create --name Video --flags TABLE_HASH_KEY --key_type UInt32
-.. table_create --name Tag --flags TABLE_HASH_KEY --key_type ShortText
-.. column_create --table Video --name title --flags COLUMN_SCALAR --type ShortText
-.. column_create --table Video --name tags --flags COLUMN_VECTOR --type Tag
-.. column_create --table Tag --name index_tags --flags COLUMN_INDEX --type Video --source tags
-.. load --table Video
-.. [
-.. {"_key":1,"title":"Soccer 2010","tags":["Sports","Soccer"]},
-.. {"_key":2,"title":"Zenigata Kinjirou","tags":["Variety","Money"]},
-.. {"_key":3,"title":"groonga Demo","tags":["IT","Server","groonga"]},
-.. {"_key":4,"title":"Moero!! Ultra Baseball","tags":["Sports","Baseball"]},
-.. {"_key":5,"title":"Hex Gone!","tags":["Variety","Quiz"]},
-.. {"_key":6,"title":"Pikonyan 1","tags":["Animation","Pikonyan"]},
-.. {"_key":7,"title":"Draw 8 Month","tags":["Animation","Raccoon"]},
-.. {"_key":8,"title":"K.O.","tags":["Animation","Music"]}
-.. ]
-
-After creating indexed column, you can do full-text search very fast. The indexed column is also automatically updated when stored data is refreshed.
-
-List up the movies that specific keywords are given.
-
-.. groonga-command
-.. include:: ../example/tutorial/index-2.log
-.. select --table Video --query tags:@Variety --output_columns _key,title
-.. select --table Video --query tags:@Sports --output_columns _key,title
-.. select --table Video --query tags:@Animation --output_columns _key,title
-
-You can search by tags such as "Variety", "Sports" and "Animation".
-
-Reverse resolution of reference relationships
----------------------------------------------
-
-Groonga supports indexes for reverse resolution among tables. Tag search is one of concrete examples.
-
-For example, you can search friendships by reverse resolution in social networking site.
-
-Following example shows how to create ``User`` table which stores user information, ``username`` column which stores user name, ``friends`` column which stores list of user's friends in array, ``index_friends`` column as indexed column.
-
-.. groonga-command
-.. include:: ../example/tutorial/index-3.log
-.. table_create --name User --flags TABLE_HASH_KEY --key_type ShortText
-.. column_create --table User --name username --flags COLUMN_SCALAR --type ShortText
-.. column_create --table User --name friends --flags COLUMN_VECTOR --type User
-.. column_create --table User --name index_friends --flags COLUMN_INDEX --type User --source friends
-.. load --table User
-.. [
-.. {"_key":"ken","username":"健作","friends":["taro","jiro","tomo","moritapo"]}
-.. {"_key":"moritapo","username":"森田","friends":["ken","tomo"]}
-.. {"_key":"taro","username":"ぐるんが太郎","friends":["jiro","tomo"]}
-.. {"_key":"jiro","username":"ぐるんが次郎","friends":["taro","tomo"]}
-.. {"_key":"tomo","username":"トモちゃん","friends":["ken","hana"]}
-.. {"_key":"hana","username":"花子","friends":["ken","taro","jiro","moritapo","tomo"]}
-.. ]
-
-Let's show list of users who contains specified user in friend list.
-
-.. groonga-command
-.. include:: ../example/tutorial/index-4.log
-.. select --table User --query friends:@tomo --output_columns _key,username
-.. select --table User --query friends:@jiro --output_columns _key,username
-
-Then drilldown the count which shows user is listed as friend.
-
-.. groonga-command
-.. include:: ../example/tutorial/index-5.log
-.. select --table User --limit 0 --drilldown friends
-
-As you can see, it shows the results which follows reverse resolution of reference relationship.
-
-Geo location search with index
-------------------------------
-
-Groonga supports to add indexes to the column which stores geo location information.
-Groonga is very fast because it use such indexes against the column which contains geo location information to search enormous number of records.
-
-.. groonga-command
-.. include:: ../example/tutorial/index-6.log
-.. table_create --name GeoSite --flags TABLE_HASH_KEY --key_type ShortText
-.. column_create --table GeoSite --name location --type WGS84GeoPoint
-.. table_create --name GeoIndex --flags TABLE_PAT_KEY --key_type WGS84GeoPoint
-.. column_create --table GeoIndex --name index_point --type GeoSite --flags COLUMN_INDEX --source location
-.. load --table GeoSite
-.. [
-..  {"_key":"http://example.org/","location":"128452975x503157902"},
-..  {"_key":"http://example.net/","location":"128487316x502920929"}
-.. ]
-.. select --table GeoSite --filter 'geo_in_circle(location, "128515259x503187188", 5000)' --output_columns _key,location
-
-These indexes are also used when sorting the records with geo location search.
-
-.. groonga-command
-.. include:: ../example/tutorial/index-7.log
-.. select --table GeoSite --filter 'geo_in_circle(location, "128515259x503187188", 50000)' --output_columns _key,location,_score --sortby '-geo_distance(location, "128515259x503187188")' --scorer '_score = geo_distance(location, "128515259x503187188")'