Yasuhiro Horimoto 2019-03-04 11:28:13 +0900 (Mon, 04 Mar 2019) Revision: b77db7a8b48a6e95655327c51dca995773e211d9 https://github.com/groonga/groonga/commit/b77db7a8b48a6e95655327c51dca995773e211d9 Message: doc: improve an explanation about "GRN_TABLE_SELECT_ENOUGH_FILTERED_RATIO" Because applied conditions of this feature don't clear, we add details of it. Modified files: doc/locale/ja/LC_MESSAGES/news.po doc/source/news.rst Modified: doc/locale/ja/LC_MESSAGES/news.po (+28 -8) =================================================================== --- doc/locale/ja/LC_MESSAGES/news.po 2019-02-28 05:33:05 +0900 (65b6df5e6) +++ doc/locale/ja/LC_MESSAGES/news.po 2019-03-04 11:28:13 +0900 (c5d852a58) @@ -822,17 +822,37 @@ msgstr "" msgid "" "Enable sequential search for enough filtered case by default. If the current " "result is enough filtered, sequential search is faster than index search. If " -"the current result has only 1% records and less than 1000 records, " -"sequential search is used even when index search is available. You can " -"disable this feature by ``GRN_TABLE_SELECT_ENOUGH_FILTERED_RATIO=0.0`` " -"environment variable." +"the current result has only 1% records of all records in a table and less " +"than 1000 records, sequential search is used even when index search is " +"available." msgstr "" "充分に絞り込み済みの場合において、初期状態でシーケンシャルサーチを行うように" "しました。現在の結果が充分に少数である場合、シーケンシャルサーチはインデック" -"ス検索よりも高速です。現在の結果が元の結果の1%で1000件未満の場合、インデック" -"ス検索可能な場合であってもシーケンシャルサーチが使われます。この機能は環境変" -"数で ``GRN_TABLE_SELECT_ENOUGH_FILTERED_RATIO=0.0`` と設定する事で無効化でき" -"ます。" +"ス検索よりも高速です。現在の結果がテーブル内の全レコードの1%で1000件未満の場" +"合、インデックス検索可能な場合であってもシーケンシャルサーチが使われます。" + +msgid "" +"Cullently, this optimization is applied when search by ``==``, ``>``, ``<``, " +"``>=``, or ``<=``." +msgstr "" +"現在、この最適化は、 ``==`` と ``>`` と ``<`` と ``>=`` と ``<=`` を使った検" +"索時に適用されます。" + +msgid "" +"When a key of a table that has columns specified by the filter is " +"``ShortText``, you must set ``NormalizerAuto`` to normalizer of the table to " +"apply this optimization." +msgstr "" +"絞り込みに指定したカラムを持つテーブルのキーが ``ShortText`` の場合、この最適" +"化を適用するためには、そのテーブルのノーマライザーを ``NormalizerAuto`` にす" +"る必要があります。" + +msgid "" +"You can disable this feature by " +"``GRN_TABLE_SELECT_ENOUGH_FILTERED_RATIO=0.0`` environment variable." +msgstr "" +"この機能は環境変数で ``GRN_TABLE_SELECT_ENOUGH_FILTERED_RATIO=0.0`` と設定す" +"る事で無効化できます。" msgid "[load] improve error message. Table name is included." msgstr "[load] エラーメッセージにテーブル名を含めるようにしました。" Modified: doc/source/news.rst (+6 -1) =================================================================== --- doc/source/news.rst 2019-02-28 05:33:05 +0900 (d2dfb3515) +++ doc/source/news.rst 2019-03-04 11:28:13 +0900 (0c7b72a65) @@ -393,7 +393,12 @@ Improvements * Enable sequential search for enough filtered case by default. If the current result is enough filtered, sequential search is faster than index search. - If the current result has only 1% records and less than 1000 records, sequential search is used even when index search is available. + If the current result has only 1% records of all records in a table and less than 1000 records, sequential search is used even when index search is available. + + Cullently, this optimization is applied when search by ``==``, ``>``, ``<``, ``>=``, or ``<=``. + + When a key of a table that has columns specified by the filter is ``ShortText``, you must set ``NormalizerAuto`` to normalizer of the table to apply this optimization. + You can disable this feature by ``GRN_TABLE_SELECT_ENOUGH_FILTERED_RATIO=0.0`` environment variable. * [load] improve error message. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.osdn.me/mailman/archives/groonga-commit/attachments/20190304/a330637a/attachment-0001.html>
