YUKI Hiroshi
null+****@clear*****
Tue Mar 25 11:48:30 JST 2014
YUKI Hiroshi 2014-03-25 11:48:30 +0900 (Tue, 25 Mar 2014) New Revision: c1577889d4e60f16ff39b5535428173f8962bde9 https://github.com/droonga/droonga.org/commit/c1577889d4e60f16ff39b5535428173f8962bde9 Message: Revert "Fix path to get cache statistics" Because other changes are unexpectedly committed. This reverts commit 9a0e67ee55d4f3bb38bd6d11fd3c2c1dadf7325b. Modified files: _po/ja/reference/catalog/version2/index.po _po/ja/reference/commands/search/index.po ja/reference/catalog/version2/index.md ja/tutorial/plugin-development/adapter/index.md ja/tutorial/plugin-development/handler/index.md news/_posts/2014-03-29-release.md Modified: _po/ja/reference/catalog/version2/index.po (+61 -31) =================================================================== --- _po/ja/reference/catalog/version2/index.po 2014-03-25 11:46:23 +0900 (824b9e2) +++ _po/ja/reference/catalog/version2/index.po 2014-03-25 11:48:30 +0900 (58609f1) @@ -127,7 +127,7 @@ msgstr "" ": 以下のキーと値のペアを持つオブジェクト。" msgid "#### Parameters" -msgstr "" +msgstr "#### パラメータ" msgid "##### `version` {#parameter-version}" msgstr "" @@ -228,7 +228,7 @@ msgstr "" ": 可。`dataset`と`volume`の定義でオーバライドできます。" msgid "#### Example" -msgstr "" +msgstr "#### 例" msgid "A version 2 catalog effective after `2013-09-01T00:00:00Z`, with no datasets:" msgstr "" @@ -355,11 +355,15 @@ msgid "" "Abstract\n" ": Specifies which data structure is used for managing keys of the table." msgstr "" +"概要\n" +": テーブルのキーを管理するためのデータ構造を指定する。" msgid "" "Value\n" ": Any of the following values." msgstr "" +"値\n" +": 以下のうち何れかの値。" msgid "" "* \"Array\": for tables which have no keys.\n" @@ -367,11 +371,17 @@ msgid "" "* \"PatriciaTrie\": for patricia trie tables.\n" "* \"DoubleArrayTrie\": for double array trie tables." msgstr "" +"* \"Array\": キーの無いテーブル\n" +"* \"Hash\": ハッシュテーブル\n" +"* \"PatriciaTrie\": パトリシアトライテーブル\n" +"* \"DoubleArrayTrie\": ダブル配列トライテーブル" msgid "" "Default value\n" ": \"Hash\"" msgstr "" +"デフォルト値\n" +": \"Hash\"" msgid "##### `keyType` {#parameter-keyType}" msgstr "" @@ -381,11 +391,13 @@ msgid "" ": Data type of the key of the table. Mustn't be assigned when the `type` is \"A" "rray\"." msgstr "" +"概要\n" +": テーブルにおけるキーのデータ型。`type`が\"Array\"の場合は指定してはいけません。" msgid "" "Value\n" ": Any of the following data types." -msgstr "" +msgstr ": 以下のデータ型のうちの何れか。" msgid "" "* \"Integer\" : 64bit signed integer.\n" @@ -396,6 +408,13 @@ msgid "" "* \"WGS84GeoPoint\" : [WGS84](http://en.wikipedia.org/wiki/World_Geodetic_System" ") based geometric point value." msgstr "" +"* \"Integer\" : 64bit 符号付き整数。\n" +"* \"Float\" : 64bit 浮動小数点数。\n" +"* \"Time\" : マイクロ秒精度の時刻。\n" +"* \"ShortText\" : 4095バイトまでの文字列。\n" +"* \"TokyoGeoPoint\" : 旧日本測地系による経緯度。\n" +"* \"WGS84GeoPoint\" : [WGS84](http://en.wikipedia.org/wiki/World_Geodetic_System" +") による経緯度。" msgid "" "Default value\n" @@ -465,13 +484,13 @@ msgid "" msgstr "" msgid "#### Examples" -msgstr "" +msgstr "#### 例" msgid "##### Example 1: Hash table" -msgstr "" +msgstr "##### 例1: Hashテーブル" msgid "A `Hash` table whose key is `ShortText` type, with no columns:" -msgstr "" +msgstr "`ShortText`型のキーを持つ`Hash`テーブルで、カラムは無いもの:" msgid "" "~~~\n" @@ -485,12 +504,12 @@ msgid "" msgstr "" msgid "##### Example 2: PatriciaTrie table" -msgstr "" +msgstr "##### 例2: PatriciaTrieテーブル" msgid "" "A `PatriciaTrie` table with `TokenBigram` tokenizer and `NormalizerAuto` norma" "lizer, with no columns:" -msgstr "" +msgstr "`TokenBigram`トークナイザと`NormalizerAuto`ノーマライザを利用する`PatriciaTrie`テーブル" msgid "" "~~~\n" @@ -566,8 +585,8 @@ msgid "" ") based geometric point value." msgstr "" -msgid "##### `indexOptions` {#parameter-indexOptions}" -msgstr "### indexOption 定義 {#indexOption}" +msgid "##### `vectorOptions` {#parameter-vectorOptions}" +msgstr "" msgid "" "Abstract\n" @@ -586,12 +605,8 @@ msgid "" ": `{}` (Void object)." msgstr "" -msgid "" -"Abstract\n" -": Specifies the optional properties of an \"Index\" column." +msgid "##### `indexOptions` {#parameter-indexOptions}" msgstr "" -"概要\n" -": データベースインスタンスの場所を指定します。" msgid "" "Value\n" @@ -599,10 +614,10 @@ msgid "" msgstr "" msgid "##### Example 1: Scalar column" -msgstr "" +msgstr "##### 例1: スカラー型カラム" msgid "A scaler column to store `ShortText` values:" -msgstr "" +msgstr "`ShortText`を格納するスカラー型のカラム:" msgid "" "~~~\n" @@ -635,7 +650,7 @@ msgid "##### Example 3: Index column" msgstr "##### 例2: インデクスカラム" msgid "A column to index `address` column on `Store` table:" -msgstr "" +msgstr "`Store`テーブルの`address`カラムをインデクスするカラム:" msgid "" "~~~\n" @@ -654,6 +669,9 @@ msgstr "" msgid "### vectorOptions definition {#vectorOptions}" msgstr "### indexOption 定義 {#indexOption}" +msgid "##### `weight` {#parameter-vectorOptions-weight}" +msgstr "" + msgid "" "Abstract\n" ": Specifies whether the vector column stores the weight data or not. Weight da" @@ -684,6 +702,9 @@ msgstr "" msgid "### indexOptions definition {#indexOptions}" msgstr "### indexOption 定義 {#indexOption}" +msgid "##### `section` {#parameter-indexOptions-section}" +msgstr "" + msgid "" "Abstract\n" ": Specifies whether the index column stores the section data or not. Section d" @@ -691,12 +712,18 @@ msgid "" "e appears." msgstr "" +msgid "##### `weight` {#parameter-indexOptions-weight}" +msgstr "" + msgid "" "Abstract\n" ": Specifies whether the index column stores the weight data or not. Weight dat" "a is used for indicating the importance of the value in the sources." msgstr "" +msgid "##### `position` {#parameter-indexOptions-position}" +msgstr "" + msgid "" "Abstract\n" ": Specifies whether the index column stores the position data or not. Position" @@ -704,6 +731,9 @@ msgid "" "es. It is indispensable for fast and accurate phrase-search." msgstr "" +msgid "##### `sources` {#parameter-indexOptions-sources}" +msgstr "" + msgid "" "Abstract\n" ": Makes the column an inverted index of the referencing table's columns." @@ -751,7 +781,7 @@ msgstr "" "外のパラメータを指定してはいけません。そうでない場合は、`dimension`と`slicer`と`slices`が必須で、他は指定してはいけません。" msgid "#### Types of Slicers {#types-of-slicers}" -msgstr "" +msgstr "#### スライサーの種類" msgid "" "In order to define a volume which consists of a collection of `slices`,\n" @@ -884,10 +914,10 @@ msgstr "" ": [`slice` 定義](#slice)の配列。" msgid "##### Example 1: Single instance" -msgstr "" +msgstr "##### 例1: 単一のインスタンス" msgid "A volume at \"localhost:24224/volume.000\":" -msgstr "" +msgstr "\"localhost:24224/volume.000\"にあるボリューム:" msgid "" "~~~\n" @@ -898,13 +928,13 @@ msgid "" msgstr "" msgid "##### Example 2: Slices" -msgstr "" +msgstr "##### Example 2: 複数のスライス" msgid "" "A volume that consists of three slices, records are to be distributed accordin" "g to `hash`,\n" "which is ratio-scaled slicer function, of `_key`." -msgstr "" +msgstr "3つのスライスから構成され、`_key`に対してratio-scaledなスライサー関数`hash`を適用してレコードを分散させるボリューム" msgid "" "~~~\n" @@ -1011,10 +1041,10 @@ msgid ": An object which is a [`volume` definition](#volume)" msgstr ": [`volume` 定義](#volume)オブジェクト" msgid "##### Example 1: Ratio-scaled" -msgstr "" +msgstr "\"##### 例1: Ratio-scaled" msgid "Slice for a ratio-scaled slicer, with the weight `1`:" -msgstr "" +msgstr "ratio-scaledなスライサーのためのスライス、重みは`1`" msgid "" "~~~\n" @@ -1027,10 +1057,10 @@ msgid "" msgstr "" msgid "##### Example 2: Nominal-scaled" -msgstr "" +msgstr "##### 例2: Nominal-scaled" msgid "Slice for a nominal-scaled slicer, with the label `\"1\"`:" -msgstr "" +msgstr "nominal-scaledなスライサーのためのスライス、ラベルは `\"1\"`" msgid "" "~~~\n" @@ -1043,10 +1073,10 @@ msgid "" msgstr "" msgid "##### Example 3: Ordinal-scaled" -msgstr "" +msgstr "##### 例3: Ordinal-scaled" msgid "Slice for a ordinal-scaled slicer, with the boundary `100`:" -msgstr "" +msgstr "ordinal-scaledなスライサーに対するスライス、境界値は`100`:" msgid "" "~~~\n" @@ -1059,10 +1089,10 @@ msgid "" msgstr "" msgid "## Realworld example" -msgstr "" +msgstr "## 実際の例" msgid "See the catalog of [basic tutorial]." -msgstr "" +msgstr "[基本的な使い方のチュートリアル][basic tutorial]に登場するカタログを参照してください。" msgid " [basic tutorial]: ../../../tutorial/basic" msgstr "" Modified: _po/ja/reference/commands/search/index.po (+12 -12) =================================================================== --- _po/ja/reference/commands/search/index.po 2014-03-25 11:46:23 +0900 (11d05da) +++ _po/ja/reference/commands/search/index.po 2014-03-25 11:48:30 +0900 (d3ee79d) @@ -1969,18 +1969,6 @@ msgstr "" " }" msgid "" -"`type`\n" -": A string meaning the value type of the column.\n" -" The type is indicated as one of [Groonga's primitive data formats](http://gr" -"oonga.org/docs/reference/types.html), or a name of an existing table for refer" -"ring columns." -msgstr "" -"`type`\n" -": カラムの値の型を示す文字列です。\n" -" 値は[Groonga のプリミティブなデータ型](http://groonga.org/ja/docs/reference/types.html)の名前" -"か、もしくはテーブル名です。" - -msgid "" "This format is designed to reduce traffic with small responses, instead of use" "ful rich data format.\n" "Recommended for cases when the response can include too much records, or the s" @@ -2018,6 +2006,18 @@ msgstr "" "。" msgid "" +"`type`\n" +": A string meaning the value type of the column.\n" +" The type is indicated as one of [Groonga's primitive data formats](http://gr" +"oonga.org/docs/reference/types.html), or a name of an existing table for refer" +"ring columns." +msgstr "" +"`type`\n" +": カラムの値の型を示す文字列です。\n" +" 値は[Groonga のプリミティブなデータ型](http://groonga.org/ja/docs/reference/types.html)の名前" +"か、もしくはテーブル名です。" + +msgid "" "`vector`\n" ": A boolean value meaning it is a [vector column](http://groonga.org/docs/tuto" "rial/data.html#vector-types) or not.\n" Modified: ja/reference/catalog/version2/index.md (+57 -59) =================================================================== --- ja/reference/catalog/version2/index.md 2014-03-25 11:46:23 +0900 (89ec1d1) +++ ja/reference/catalog/version2/index.md 2014-03-25 11:48:30 +0900 (46329a8) @@ -95,7 +95,7 @@ layout: ja 値 : 以下のキーと値のペアを持つオブジェクト。 -#### Parameters +#### パラメータ ##### `version` {#parameter-version} @@ -153,7 +153,7 @@ layout: ja : 可。`dataset`と`volume`の定義でオーバライドできます。 -#### Example +#### 例 A version 2 catalog effective after `2013-09-01T00:00:00Z`, with no datasets: @@ -171,7 +171,7 @@ A version 2 catalog effective after `2013-09-01T00:00:00Z`, with no datasets: 値 : 以下のキーと値のペアを持つオブジェクト。 -#### Parameters +#### パラメータ ##### `plugins` {#parameter-plugins} @@ -229,7 +229,7 @@ A version 2 catalog effective after `2013-09-01T00:00:00Z`, with no datasets: 継承可能性 : 不可。 -#### Example +#### 例 データベースインスタンスに1つにつき4ワーカーを持ち、プラグイン`groonga`、`crud`、`search`を使用するデータセット: @@ -249,22 +249,22 @@ A version 2 catalog effective after `2013-09-01T00:00:00Z`, with no datasets: 値 : 以下のキーと値のペアを持つオブジェクト。 -#### Parameters +#### パラメータ ##### `type` {#parameter-table-type} -Abstract -: Specifies which data structure is used for managing keys of the table. +概要 +: テーブルのキーを管理するためのデータ構造を指定する。 -Value -: Any of the following values. +値 +: 以下のうち何れかの値。 -* "Array": for tables which have no keys. -* "Hash": for hash tables. -* "PatriciaTrie": for patricia trie tables. -* "DoubleArrayTrie": for double array trie tables. +* "Array": キーの無いテーブル +* "Hash": ハッシュテーブル +* "PatriciaTrie": パトリシアトライテーブル +* "DoubleArrayTrie": ダブル配列トライテーブル -Default value +デフォルト値 : "Hash" 継承可能性 @@ -272,18 +272,17 @@ Default value ##### `keyType` {#parameter-keyType} -Abstract -: Data type of the key of the table. Mustn't be assigned when the `type` is "Array". +概要 +: テーブルにおけるキーのデータ型。`type`が"Array"の場合は指定してはいけません。 -Value -: Any of the following data types. +: 以下のデータ型のうちの何れか。 -* "Integer" : 64bit signed integer. -* "Float" : 64bit floating-point number. -* "Time" : Time value with microseconds resolution. -* "ShortText" : Text value up to 4095 bytes length. -* "TokyoGeoPoint" : Tokyo Datum based geometric point value. -* "WGS84GeoPoint" : [WGS84](http://en.wikipedia.org/wiki/World_Geodetic_System) based geometric point value. +* "Integer" : 64bit 符号付き整数。 +* "Float" : 64bit 浮動小数点数。 +* "Time" : マイクロ秒精度の時刻。 +* "ShortText" : 4095バイトまでの文字列。 +* "TokyoGeoPoint" : 旧日本測地系による経緯度。 +* "WGS84GeoPoint" : [WGS84](http://en.wikipedia.org/wiki/World_Geodetic_System) による経緯度。 Default value : None. Mandatory for tables with keys. @@ -349,11 +348,11 @@ Value 継承可能性 : 不可。 -#### Examples +#### 例 -##### Example 1: Hash table +##### 例1: Hashテーブル -A `Hash` table whose key is `ShortText` type, with no columns: +`ShortText`型のキーを持つ`Hash`テーブルで、カラムは無いもの: ~~~ { @@ -364,9 +363,9 @@ A `Hash` table whose key is `ShortText` type, with no columns: } ~~~ -##### Example 2: PatriciaTrie table +##### 例2: PatriciaTrieテーブル -A `PatriciaTrie` table with `TokenBigram` tokenizer and `NormalizerAuto` normalizer, with no columns: +`TokenBigram`トークナイザと`NormalizerAuto`ノーマライザを利用する`PatriciaTrie`テーブル ~~~ { @@ -385,7 +384,7 @@ A `PatriciaTrie` table with `TokenBigram` tokenizer and `NormalizerAuto` normali : An object with the following key/value pairs. -#### Parameters +#### パラメータ ##### `type` {#parameter-column-type} @@ -442,10 +441,10 @@ Default value 継承可能性 : 不可。 -### indexOption 定義 {#indexOption} +##### `indexOptions` {#parameter-indexOptions} -概要 -: データベースインスタンスの場所を指定します。 +Abstract +: Specifies the optional properties of an "Index" column. Value : An object which is an [`indexOptions` definition](#indexOptions) @@ -456,11 +455,11 @@ Default value 継承可能性 : 不可。 -#### Examples +#### 例 -##### Example 1: Scalar column +##### 例1: スカラー型カラム -A scaler column to store `ShortText` values: +`ShortText`を格納するスカラー型のカラム: ~~~ { @@ -485,7 +484,7 @@ A vector column to store `ShortText` values with weight: ##### 例2: インデクスカラム -A column to index `address` column on `Store` table: +`Store`テーブルの`address`カラムをインデクスするカラム: ~~~ { @@ -504,7 +503,7 @@ A column to index `address` column on `Store` table: 値 : 以下のキーと値のペアを持つオブジェクト。 -#### Parameters +#### パラメータ ##### `weight` {#parameter-vectorOptions-weight} @@ -520,7 +519,7 @@ Default value 継承可能性 : 不可。 -#### Example +#### 例 Store the weight data. @@ -535,7 +534,7 @@ Store the weight data. 値 : 以下のキーと値のペアを持つオブジェクト。 -#### Parameters +#### パラメータ ##### `section` {#parameter-indexOptions-section} @@ -593,7 +592,7 @@ Value 継承可能性 : 不可。 -#### Example +#### 例 Store the section data, the weight data and the position data. Index `name` and `address` on the referencing table. @@ -618,7 +617,7 @@ Index `name` and `address` on the referencing table. 値 : 以下のキーと値のペアを持つオブジェクト。 -#### Types of Slicers {#types-of-slicers} +#### スライサーの種類 In order to define a volume which consists of a collection of `slices`, the way how slice recodes into slices must be decided. @@ -646,7 +645,7 @@ element of `{High, Middle, Low}`. the values denotes categories,which have no order, e.g. country, zip code, color. -#### Parameters +#### パラメータ ##### `address` {#parameter-address} @@ -709,11 +708,11 @@ e.g. country, zip code, color. 継承可能性 : 不可。 -#### Examples +#### 例 -##### Example 1: Single instance +##### 例1: 単一のインスタンス -A volume at "localhost:24224/volume.000": +"localhost:24224/volume.000"にあるボリューム: ~~~ { @@ -721,10 +720,9 @@ A volume at "localhost:24224/volume.000": } ~~~ -##### Example 2: Slices +##### Example 2: 複数のスライス -A volume that consists of three slices, records are to be distributed according to `hash`, -which is ratio-scaled slicer function, of `_key`. +3つのスライスから構成され、`_key`に対してratio-scaledなスライサー関数`hash`を適用してレコードを分散させるボリューム ~~~ { @@ -751,7 +749,7 @@ which is ratio-scaled slicer function, of `_key`. 値 : 以下のキーと値のペアを持つオブジェクト。 -#### Parameters +#### パラメータ ##### `weight` {#parameter-slice-weight} @@ -810,11 +808,11 @@ Value 継承可能性 : 不可。 -#### Examples +#### 例 -##### Example 1: Ratio-scaled +"##### 例1: Ratio-scaled -Slice for a ratio-scaled slicer, with the weight `1`: +ratio-scaledなスライサーのためのスライス、重みは`1` ~~~ { @@ -824,9 +822,9 @@ Slice for a ratio-scaled slicer, with the weight `1`: } ~~~ -##### Example 2: Nominal-scaled +##### 例2: Nominal-scaled -Slice for a nominal-scaled slicer, with the label `"1"`: +nominal-scaledなスライサーのためのスライス、ラベルは `"1"` ~~~ { @@ -836,9 +834,9 @@ Slice for a nominal-scaled slicer, with the label `"1"`: } ~~~ -##### Example 3: Ordinal-scaled +##### 例3: Ordinal-scaled -Slice for a ordinal-scaled slicer, with the boundary `100`: +ordinal-scaledなスライサーに対するスライス、境界値は`100`: ~~~ { @@ -848,8 +846,8 @@ Slice for a ordinal-scaled slicer, with the boundary `100`: } ~~~ -## Realworld example +## 実際の例 -See the catalog of [basic tutorial]. +[基本的な使い方のチュートリアル][basic tutorial]に登場するカタログを参照してください。 [basic tutorial]: ../../../tutorial/basic Modified: ja/tutorial/plugin-development/adapter/index.md (+21 -23) =================================================================== --- ja/tutorial/plugin-development/adapter/index.md 2014-03-25 11:46:23 +0900 (18cb63b) +++ ja/tutorial/plugin-development/adapter/index.md 2014-03-25 11:48:30 +0900 (10003e4) @@ -1,5 +1,5 @@ --- -title: "プラグイン：リクエストとレスポンスをAdaptして、既存のコマンドに基づいた新たなコマンドを作成する" +title: "プラグイン: リクエストとレスポンスを加工し、既存のコマンドに基づいた新しいコマンドを作成する" layout: ja --- @@ -17,25 +17,23 @@ layout: ja ## チュートリアルのゴール -Droongaプラグインを自分で開発するための手順を身につける事が、このチュートリアルの目標です。 +Learning steps to develop a Droonga plugin by yourself. -このページの内容は、Droongaプラグインによる「adaption」に焦点を当てています。 -最後には、練習のための小さなプラグインとして、既存の`search`コマンドを利用して`storeSearch`というコマンドを作成します。 +This page focuses on the "adaption" by Droonga plugins. +At the last, we create a new command `storeSearch` based on the existing `search` command, with a small practical plugin. ## 前提条件 -* [基本のチュートリアル][basic tutorial]を完了しておいて下さい。 +* [基本的な使い方のチュートリアル][basic tutorial] を完了している必要があります。 -## 入力メッセージに対するAdaption +## 入力メッセージの加工 -最初に、adaption phaseで動作する`sample-logger`という名前の単純なロギング用プラグインの作成を通じて基本を学びましょう。 +まず`sample-logger`という簡単なロガープラグインを使って、adaption phaseに作用するプラグインを作りながら、基礎を学びましょう。 -We sometime need to modify incoming requests from outside to Droonga Engine. -We can use a plugin for this purpose. -Let's see how to create a plugin for the adaption phase, in this section. +外部のシステムからDroonga Engineにやってくるリクエストを加工する必要がある場合があります。このようなときに、プラグインを利用できます。このセクションでは、どのようにしてadaption phaseのプラグインをつくるのかをみていきます。 -### Directory Structure +### ディレクトリの構造 Assume that we are going to add a new plugin to the system built in the [basic tutorial][]. In that tutorial, Groonga engine was placed under `engine` directory. @@ -59,7 +57,7 @@ engine ~~~ -### Create a plugin +### プラグインの作成 You must put codes for a plugin into a file which has the name *same to the plugin itself*. Because the plugin now you creating is `sample-logger`, put codes into a file `sample-logger.rb` in the `droonga/plugins` directory. @@ -91,7 +89,7 @@ This plugin does nothing except registering itself to the Droonga Engine. An adapter class must be defined as a subclass of the `Droonga::Adapter`, under the namespace of the plugin module. -### Activate the plugin with `catalog.json` +### `catalog.json`でプラグインを有効化する You need to update `catalog.json` to activate your plugin. Insert the name of the plugin `"sample-logger"` to the `"plugins"` list under the dataset, like: @@ -109,7 +107,7 @@ catalog.json: Note: you must place `"sample-logger"` before `"search"`, because the `sample-logger` plugin depends on the `search`. Droonga Engine applies plugins at the adaption phase in the order defined in the `catalog.json`, so you must resolve plugin dependencies by your hand (for now). -### Run and test +### 実行と動作を確認する Let's get Droonga started. Note that you need to specify `./lib` directory in `RUBYLIB` environment variable in order to make ruby possible to find your plugin. @@ -188,7 +186,7 @@ Elapsed time: 0.021544 This is the search result. -### Do something in the plugin: take logs +### プラグインを動作させる: ログをとる The plugin we have created do nothing so far. Let's get the plugin to do some interesting. @@ -266,7 +264,7 @@ You will see something like below fluentd's log in `fluentd.log`: This shows the message is received by our `SampleLoggerPlugin::Adapter` and then passed to Droonga. Here we can modify the message before the actual data processing. -### Modify messages with the plugin +### プラグインでメッセージを加工する Suppose that we want to restrict the number of records returned in the response, say `1`. What we need to do is set `limit` to be `1` for every request. @@ -330,13 +328,13 @@ You will see something like below fluentd's log in `fluentd.log`: ~~~ -## Adaption for outgoing messages +## 出力メッセージの加工 In case we need to modify outgoing messages from Droonga Engine, for example, search results, then we can do it simply by another method. In this section, we are going to define a method to adapt outgoing messages. -### Add a method to adapt outgoing messages +### 出力のメッセージを加工するメソッドを追加する Let's take logs of results of `search` command. Define the `adapt_output` method to process outgoing messages. @@ -364,7 +362,7 @@ lib/droonga/plugins/sample-logger.rb: The method `adapt_output` is called only for outgoing messages triggered by incoming messages processed by the plugin itself. See the [reference manual for plugin developers](../../../reference/plugin/adapter/) for more details. -### Run +### 実行する Let's restart fluentd: @@ -411,7 +409,7 @@ The fluentd's log should be like as follows: This shows that the result of `search` is passed to the `adapt_output` method (and logged), then outputted. -### Modify results in the adaption phase +### 結果をadaption phaseで加工する Let's modify the result. For example, add `completedAt` attribute that shows the time completed the request. @@ -476,7 +474,7 @@ The results in `fluentd.log` will be like this: ~~~ -## Adaption for both incoming and outgoing messages +## 入出力メッセージの加工 We have learned the basics of plugins for the adaption phase so far. Let's try to build more practical plugin. @@ -484,7 +482,7 @@ Let's try to build more practical plugin. You may feel the Droonga's `search` command is too flexible for your purpose. Here, we're going to add our own `storeSearch` command to wrap the `search` command in order to provide an application-specific and simple interface, with a new plugin named `store-search`. -### Accepting of simple requests +### シンプルなリクエストを受け取る First, create the `store-search` plugin. Remember, you must put codes into a file which has the name same to the plugin now you are creating. @@ -623,7 +621,7 @@ Now we can perform store search with simple requests. Note: look at the `"type"` of the response message. Now it became `"storeSearch.result"`, from `"search.result"`. Because it is triggered from the incoming message with the type `"storeSearch"`, the outgoing message has the type `"(incoming command).result"` automatically. In other words, you don't have to change the type of the outgoing messages, like `input_message.type = "search"` in the method `adapt_input`. -### Returning of simple responses +### シンプルなレスポンスを返す Second, let's return results in more simple way: just an array of the names of stores. Modified: ja/tutorial/plugin-development/handler/index.md (+5 -5) =================================================================== --- ja/tutorial/plugin-development/handler/index.md 2014-03-25 11:46:23 +0900 (e785e0c) +++ ja/tutorial/plugin-development/handler/index.md 2014-03-25 11:48:30 +0900 (2a3f10d) @@ -212,7 +212,7 @@ The `Collectors::Sum` is one of built-in collectors. It merges results returned from handler instances for each partition to one result. -### Activate the plugin with `catalog.json` +### `catalog.json`でプラグインを有効化する Update catalog.json to activate this plugin. Add `"count-records"` to `"plugins"`. @@ -226,7 +226,7 @@ Add `"count-records"` to `"plugins"`. (snip) ~~~ -### Run and test +### 実行と動作を確認する Let's get Droonga started. Note that you need to specify ./lib directory in RUBYLIB environment variable in order to make ruby possible to find your plugin. @@ -369,7 +369,7 @@ If the request is successfully processed, the `body` becomes `true`. Otherwise ` The `body` is just one boolean value, because we don't have to receive multiple results from partitions. -### Directory Structure +### ディレクトリの構造 Now let's create the `delete-stores` plugin, as the file `delete-stores.rb`. The directory tree will be: @@ -470,7 +470,7 @@ The handler finds and deletes existing records which have the given keyword in i And, the `Collectors::And` is bound to the step by the configuration `step.collector`. It is is also one of built-in collectors, and merges boolean values returned from handler instances for each partition and replica, to one boolean value. -### Activate the plugin with `catalog.json` +### `catalog.json`でプラグインを有効化する Update catalog.json to activate this plugin. Add `"delete-stores"` to `"plugins"`. @@ -484,7 +484,7 @@ Add `"delete-stores"` to `"plugins"`. (snip) ~~~ -### Run and test +### 実行と動作を確認する Restart the Droonga Engine and send the request. Modified: news/_posts/2014-03-29-release.md (+1 -1) =================================================================== --- news/_posts/2014-03-29-release.md 2014-03-25 11:46:23 +0900 (a240fd6) +++ news/_posts/2014-03-29-release.md 2014-03-25 11:48:30 +0900 (e82d9c6) @@ -33,7 +33,7 @@ The release has the following improvements: * The bundled HTTP server application becomes more useful. * It supports `--port`, `--droonga-engine-host-name`, `--droonga-engine-port`, `--default-dataset`, `--enable-logging` command line options. * A middleware for response caches is available now. - You can see the statistics via `/cache/statistics`. + You can see the statistics via `/cache/`. * Query parameters `attributes` and `group_by` are available for a REST `search` command (via `/tables/:tableName`). And, related projects are also released: -------------- next part -------------- HTML����������������������������...ダウンロード
