rroonga 1.3.1-x86-mingw32 → 2.0.0-x86-mingw32

data/vendor/local/share/license/msgpack/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

data/vendor/local/share/man/ja/man1/groonga.1

@@ -1,4 +1,4 @@
-.TH "GROONGA" "1" "2012 年 01 月 29 日" "1.2.9" "groonga"
+.TH "GROONGA" "1" "2012 年 02 月 28 日" "2.0.0" "groonga"
 .SH NAME
 groonga \- groongaのドキュメント
 .
@@ -6658,6 +6658,114 @@ rand(10)
 3
 .ft P
 .fi
+.SS インデックス構築
+.sp
+groongaは1.3.1から動的なインデックス構築方法と静的なインデックス構築方法を両方サポートしています。
+.SS 動的なインデックス構築方法
+.sp
+動的なインデックス構築方法では、登録された文書はインデックス構築中にすぐに検索できるようになります。しかし、静的なインデックス構築方法に比べてコストがかかります。
+.sp
+動的なインデックス構築方法は鮮度が重要な検索システムに適しています。例えば、つぶやきやニュースやブログ記事などを検索するシステムは鮮度が重要になるでしょう。動的なインデックス構築方法はできたばかりの文書を検索できるようにし、インデックス構築中も検索できます。
+.SS 静的なインデックス構築方法
+.sp
+静的なインデックス構築方法では、動的なインデックス構築方法よりもインデックス構築にかかるコストが小さくなります。インデックス構築時間は短くなるでしょう。インデックスは小さくなるでしょう。インデックス構築に必要なリソースは少なくなるでしょう。しかし、登録中の文書は登録しようとしている全ての文書のインデックス構築が終わるまで検索できません。
+.sp
+静的なインデックス構築方法は消費リソースが少ないことが重要な検索システムに適しています。鮮度が重要でないシステムであれば静的なインデックス構築方法が適しているでしょう。例えば、リファレンスマニュアルを検索するシステムは鮮度を重視しません。これは、リファレンスマニュアルはリリース時にだけ更新されるだけだからです。
+.SS 使い方
+.sp
+groongaはデフォルトで動的なインデックス構築方法を使います。文書を登録するとすぐに検索できるようになります。
+.sp
+すでにデータが格納されているカラムにインデックスを追加した場合は静的なインデックス構築方法を使います。
+.sp
+スキーマを定義します。
+.sp
+実行例:
+.sp
+.nf
+.ft C
+> table_create Tweets TABLE_NO_KEY
+[[0,1330339027.61804,0.000236272811889648],true]
+> column_create Tweets content COLUMN_SCALAR ShortText
+[[0,1330339027.81905,0.000560760498046875],true]
+> table_create Lexicon TABLE_HASH_KEY|KEY_NORMALIZE ShortText \-\-default_tokenizer TokenBigram
+[[0,1330339028.02028,0.000248432159423828],true]
+.ft P
+.fi
+.sp
+データを登録します:
+.sp
+実行例:
+.sp
+.nf
+.ft C
+> load \-\-table Tweets
+> [
+> {"content":"Hello!"},
+> {"content":"I just start it!"},
+> {"content":"I\(aqm sleepy... Have a nice day... Good night..."}
+> ]
+[[0,1330339028.22155,1.00183534622192],3]
+.ft P
+.fi
+.sp
+インデックスなしで検索します。これは何もヒットしません:
+.sp
+実行例:
+.sp
+.nf
+.ft C
+> select Tweets \-\-match_columns content \-\-query \(aqgood nice\(aq
+[[0,1330339029.42452,0.000802278518676758],[[[0],[["_id","UInt32"],["content","ShortText"]]]]]
+.ft P
+.fi
+.sp
+\fBTweets.content\fP 用のインデックスを作成します。すでに \fBTweets.content\fP に登録されているデータは静的なインデックス構築方法でインデックスを構築します:
+.sp
+実行例:
+.sp
+.nf
+.ft C
+> column_create Lexicon tweet COLUMN_INDEX|WITH_POSITION Tweets content
+[[0,1330339029.62682,0.00742125511169434],true]
+.ft P
+.fi
+.sp
+インデックスありで検索します。1件ヒットします:
+.sp
+実行例:
+.sp
+.nf
+.ft C
+> select Tweets \-\-match_columns content \-\-query \(aqgood nice\(aq
+[[0,1330339029.83545,0.000765085220336914],[[[1],[["_id","UInt32"],["content","ShortText"]],[3,"I\(aqm sleepy... Have a nice day... Good night..."]]]]
+.ft P
+.fi
+.sp
+もう一度データを登録します。このデータ用のインデックスは動的なインデックス構築方法で構築します。
+.sp
+実行例:
+.sp
+.nf
+.ft C
+> load \-\-table Tweets
+> [
+> {"content":"Good morning! Nice day."},
+> {"content":"Let\(aqs go shopping."}
+> ]
+[[0,1330339030.03821,0.801372528076172],2]
+.ft P
+.fi
+.sp
+検索すると新しく登録されたレコードもヒットします:
+.sp
+実行例:
+.sp
+.nf
+.ft C
+> select Tweets \-\-match_columns content \-\-query \(aqgood nice\(aq
+[[0,1330339031.04064,0.000650644302368164],[[[2],[["_id","UInt32"],["content","ShortText"]],[3,"I\(aqm sleepy... Have a nice day... Good night..."],[4,"Good morning! Nice day."]]]]
+.ft P
+.fi
 .SS Log
 .sp
 Groonga has two log files. They are process log and query
@@ -7054,11 +7162,11 @@ TokenMeCabトークナイザーの場合はわかち書き後のキーワード
 例えば、「スープカレー」というキーワードで検索した場合、「スープカレー」（"スープ"と"カレー"の2単語扱い）や「スープカレーライス」（"スープ"と"カレーライス"の2単語扱い）、「スープカレーバー」（1単語扱い）にもヒットします。
 .SS 検索の使い分け
 .sp
-groongaは基本的に完全一致検索のみを行います。完全一致検索でのヒット件数が所定の閾値を超えない場合に限り、非わかち書き検索を行い、それでもヒット件数が閾値を超えない場合は部分一致検索を行います。(閾値は1がデフォルト値となっています)
+groongaは基本的に完全一致検索のみを行います。完全一致検索でのヒット件数が所定の閾値以下の場合に限り、非わかち書き検索を行い、それでもヒット件数が閾値以下の場合は部分一致検索を行います。（閾値のデフォルト値は0です。）
 .sp
-ただし、すでに検索結果セットが存在する場合はたとえヒット件数が閾値に満たなくても完全一致検索のみを行います。
+ただし、すでに検索結果セットが存在する場合はたとえヒット件数が閾値以下でも完全一致検索のみを行います。
 .sp
-例えば、以下のようなクエリの場合は、それぞれの検索でヒット件数が閾値に満たない場合は完全一致検索、非わかち書き検索、部分一致検索を順に行います。:
+例えば、以下のようなクエリの場合は、それぞれの検索でヒット件数が閾値以下の場合は完全一致検索、非わかち書き検索、部分一致検索を順に行います。:
 .sp
 .nf
 .ft C
@@ -7066,7 +7174,7 @@ select Shops \-\-match_column description \-\-query スープカレー
 .ft P
 .fi
 .sp
-しかし、以下のように全文検索を行う前に検索結果セットが存在する場合は完全一致検索のみを行います。（point > 3で閾値の件数以上ヒットしている場合）:
+しかし、以下のように全文検索を行う前に検索結果セットが存在する場合は完全一致検索のみを行います。（point > 3で閾値の件数よりヒットしている場合）:
 .sp
 .nf
 .ft C

data/vendor/local/share/man/man1/groonga.1

@@ -1,4 +1,4 @@
-.TH "GROONGA" "1" "January 29, 2012" "1.2.9" "groonga"
+.TH "GROONGA" "1" "February 28, 2012" "2.0.0" "groonga"
 .SH NAME
 groonga \- groonga documentation
 .
@@ -5637,8 +5637,8 @@ complete|correct|suggest
 .UNINDENT
 .TP
 .B \fBtable\fP
-It specifies table name that has \fBitem_${DATA_SET_NAME}\(ga format.
-For example, \(ga\(gaitem_query\fP is a table name if you created
+It specifies table name that has \fBitem_${DATA_SET_NAME}\fP format.
+For example, \fBitem_query\fP is a table name if you created
 dataset by the following command:
 .sp
 .nf
@@ -6819,6 +6819,137 @@ rand(10)
 3
 .ft P
 .fi
+.SS Indexing
+.sp
+Groonga supports both online index construction and offline
+index construction since 1.3.1.
+.SS Online index construction
+.sp
+In online index construction, registered documents can be
+searchable quickly while indexing. But indexing requires
+more cost rather than indexing by offline index
+construction.
+.sp
+Online index construction is suitable for a search system
+that values freshness. For example, a search system for
+tweets, news, blog posts and so on will value
+freshness. Online index construction can make fresh
+documents searchable and keep searchable while indexing.
+.SS Offline index construction
+.sp
+In offline index construction, indexing cost is less than
+indexing cost by online index construction. Indexing time
+will be shorter. Index will be smaller. Resources required
+for indexing will be smaller. But a registering document
+cannot be searchable until all registered documents are
+indexed.
+.sp
+Offline index construction is suitable for a search system
+that values less required resources. If a search system
+doesn\(aqt value freshness, offline index construction will be
+suitable. For example, a reference manual search system
+doesn\(aqt value freshness because a reference manual will be
+updated only at a release.
+.SS How to use
+.sp
+Groonga uses online index construction by default. We
+register a document, we can search it quickly.
+.sp
+Groonga uses offline index construction by adding an index
+to a column that already has data.
+.sp
+We define a schema:
+.sp
+Execution example:
+.sp
+.nf
+.ft C
+> table_create Tweets TABLE_NO_KEY
+[[0,1330339027.61804,0.000236272811889648],true]
+> column_create Tweets content COLUMN_SCALAR ShortText
+[[0,1330339027.81905,0.000560760498046875],true]
+> table_create Lexicon TABLE_HASH_KEY|KEY_NORMALIZE ShortText \-\-default_tokenizer TokenBigram
+[[0,1330339028.02028,0.000248432159423828],true]
+.ft P
+.fi
+.sp
+We register data:
+.sp
+Execution example:
+.sp
+.nf
+.ft C
+> load \-\-table Tweets
+> [
+> {"content":"Hello!"},
+> {"content":"I just start it!"},
+> {"content":"I\(aqm sleepy... Have a nice day... Good night..."}
+> ]
+[[0,1330339028.22155,1.00183534622192],3]
+.ft P
+.fi
+.sp
+We search without index. We get no result:
+.sp
+Execution example:
+.sp
+.nf
+.ft C
+> select Tweets \-\-match_columns content \-\-query \(aqgood nice\(aq
+[[0,1330339029.42452,0.000802278518676758],[[[0],[["_id","UInt32"],["content","ShortText"]]]]]
+.ft P
+.fi
+.sp
+We create index for \fBTweets.content\fP. Already registered
+data in \fBTweets.content\fP are indexed by offline index
+construction:
+.sp
+Execution example:
+.sp
+.nf
+.ft C
+> column_create Lexicon tweet COLUMN_INDEX|WITH_POSITION Tweets content
+[[0,1330339029.62682,0.00742125511169434],true]
+.ft P
+.fi
+.sp
+We search with index. We get a matched record:
+.sp
+Execution example:
+.sp
+.nf
+.ft C
+> select Tweets \-\-match_columns content \-\-query \(aqgood nice\(aq
+[[0,1330339029.83545,0.000765085220336914],[[[1],[["_id","UInt32"],["content","ShortText"]],[3,"I\(aqm sleepy... Have a nice day... Good night..."]]]]
+.ft P
+.fi
+.sp
+We register data again. They are indexed by online index
+construction:
+.sp
+Execution example:
+.sp
+.nf
+.ft C
+> load \-\-table Tweets
+> [
+> {"content":"Good morning! Nice day."},
+> {"content":"Let\(aqs go shopping."}
+> ]
+[[0,1330339030.03821,0.801372528076172],2]
+.ft P
+.fi
+.sp
+We can also get newly registered records by searching:
+.sp
+Execution example:
+.sp
+.nf
+.ft C
+> select Tweets \-\-match_columns content \-\-query \(aqgood nice\(aq
+[[0,1330339031.04064,0.000650644302368164],[[[2],[["_id","UInt32"],["content","ShortText"]],[3,"I\(aqm sleepy... Have a nice day... Good night..."],[4,"Good morning! Nice day."]]]]
+.ft P
+.fi
 .SS Log
 .sp
 Groonga has two log files. They are process log and query
@@ -7215,11 +7346,11 @@ TokenMeCabトークナイザーの場合はわかち書き後のキーワード
 例えば、「スープカレー」というキーワードで検索した場合、「スープカレー」（"スープ"と"カレー"の2単語扱い）や「スープカレーライス」（"スープ"と"カレーライス"の2単語扱い）、「スープカレーバー」（1単語扱い）にもヒットします。
 .SS 検索の使い分け
 .sp
-groongaは基本的に完全一致検索のみを行います。完全一致検索でのヒット件数が所定の閾値を超えない場合に限り、非わかち書き検索を行い、それでもヒット件数が閾値を超えない場合は部分一致検索を行います。(閾値は1がデフォルト値となっています)
+groongaは基本的に完全一致検索のみを行います。完全一致検索でのヒット件数が所定の閾値以下の場合に限り、非わかち書き検索を行い、それでもヒット件数が閾値以下の場合は部分一致検索を行います。（閾値のデフォルト値は0です。）
 .sp
-ただし、すでに検索結果セットが存在する場合はたとえヒット件数が閾値に満たなくても完全一致検索のみを行います。
+ただし、すでに検索結果セットが存在する場合はたとえヒット件数が閾値以下でも完全一致検索のみを行います。
 .sp
-例えば、以下のようなクエリの場合は、それぞれの検索でヒット件数が閾値に満たない場合は完全一致検索、非わかち書き検索、部分一致検索を順に行います。:
+例えば、以下のようなクエリの場合は、それぞれの検索でヒット件数が閾値以下の場合は完全一致検索、非わかち書き検索、部分一致検索を順に行います。:
 .sp
 .nf
 .ft C
@@ -7227,7 +7358,7 @@ select Shops \-\-match_column description \-\-query スープカレー
 .ft P
 .fi
 .sp
-しかし、以下のように全文検索を行う前に検索結果セットが存在する場合は完全一致検索のみを行います。（point > 3で閾値の件数以上ヒットしている場合）:
+しかし、以下のように全文検索を行う前に検索結果セットが存在する場合は完全一致検索のみを行います。（point > 3で閾値の件数よりヒットしている場合）:
 .sp
 .nf
 .ft C
@@ -7460,10 +7591,10 @@ This section describes the details.
 .UNINDENT
 .SS How to report a bug
 .sp
-We have two issue tracking systems,
-\fI\%Redmine\fP and \fI\%GitHub issue tracker\fP. Redmine is for
-Japanese and GitHub issue tracker is for English. You can
-use both of them to report a bug.
+We have two issue tracking systems, \fI\%Redmine\fP and
+\fI\%GitHub issue tracker\fP.
+Redmine is for Japanese and GitHub issue tracker is for
+English. You can use both of them to report a bug.
 .SS groonga開発者向け情報
 .SS groonga 通信アーキテクチャ
 .SS gqtpでのアーキテクチャ