rroonga 6.0.2-x64-mingw32 → 6.0.4-x64-mingw32

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

@@ -89,9 +89,9 @@ Install required packages to build Groonga::
 
 Download source::
 
-  % wget http://packages.groonga.org/source/groonga/groonga-6.0.2.tar.gz
-  % tar xvzf groonga-6.0.2.tar.gz
-  % cd groonga-6.0.2
+  % wget http://packages.groonga.org/source/groonga/groonga-6.0.4.tar.gz
+  % tar xvzf groonga-6.0.4.tar.gz
+  % cd groonga-6.0.4
 
 Configure (see :ref:`source-configure` about ``configure`` options)::
 

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

@@ -80,9 +80,9 @@ Install required packages to build Groonga::
 
 Download source::
 
-  % wget http://packages.groonga.org/source/groonga/groonga-6.0.2.tar.gz
-  % tar xvzf groonga-6.0.2.tar.gz
-  % cd groonga-6.0.2
+  % wget http://packages.groonga.org/source/groonga/groonga-6.0.4.tar.gz
+  % tar xvzf groonga-6.0.4.tar.gz
+  % cd groonga-6.0.4
 
 Configure (see :ref:`source-configure` about ``configure`` options)::
 

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

@@ -49,9 +49,9 @@ Install `Xcode <https://developer.apple.com/xcode/>`_.
 
 Download source::
 
-  % curl -O http://packages.groonga.org/source/groonga/groonga-6.0.2.tar.gz
-  % tar xvzf groonga-6.0.2.tar.gz
-  % cd groonga-6.0.2
+  % curl -O http://packages.groonga.org/source/groonga/groonga-6.0.4.tar.gz
+  % tar xvzf groonga-6.0.4.tar.gz
+  % cd groonga-6.0.4
 
 Configure (see :ref:`source-configure` about ``configure`` options)::
 

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

@@ -74,9 +74,9 @@ Build from source
 Groonga uses GNU build system. So the following is the simplest build
 steps::
 
-  % wget http://packages.groonga.org/source/groonga/groonga-6.0.2.tar.gz
-  % tar xvzf groonga-6.0.2.tar.gz
-  % cd groonga-6.0.2
+  % wget http://packages.groonga.org/source/groonga/groonga-6.0.4.tar.gz
+  % tar xvzf groonga-6.0.4.tar.gz
+  % cd groonga-6.0.4
   % ./configure
   % make
   % sudo make install

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

@@ -17,9 +17,9 @@ Install required packages to build Groonga::
 
 Download source::
 
-  % wget http://packages.groonga.org/source/groonga/groonga-6.0.2.tar.gz
-  % gtar xvzf groonga-6.0.2.tar.gz
-  % cd groonga-6.0.2
+  % wget http://packages.groonga.org/source/groonga/groonga-6.0.4.tar.gz
+  % gtar xvzf groonga-6.0.4.tar.gz
+  % cd groonga-6.0.4
 
 Configure with ``CFLAGS="-m64" CXXFLAGS="-m64"`` variables. They are
 needed for building 64-bit version. To build 32-bit version, just

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

@@ -83,9 +83,9 @@ Install required packages to build Groonga::
 
 Download source::
 
-  % wget http://packages.groonga.org/source/groonga/groonga-6.0.2.tar.gz
-  % tar xvzf groonga-6.0.2.tar.gz
-  % cd groonga-6.0.2
+  % wget http://packages.groonga.org/source/groonga/groonga-6.0.4.tar.gz
+  % tar xvzf groonga-6.0.4.tar.gz
+  % cd groonga-6.0.4
 
 Configure (see :ref:`source-configure` about ``configure`` options)::
 

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

@@ -21,14 +21,14 @@ Installer
 For 32-bit environment, download x86 executable binary from
 packages.groonga.org:
 
-  * http://packages.groonga.org/windows/groonga/groonga-6.0.2-x86.exe
+  * http://packages.groonga.org/windows/groonga/groonga-6.0.4-x86.exe
 
 Then run it.
 
 For 64-bit environment, download x64 executable binary from
 packages.goronga.org:
 
-  * http://packages.groonga.org/windows/groonga/groonga-6.0.2-x64.exe
+  * http://packages.groonga.org/windows/groonga/groonga-6.0.4-x64.exe
 
 Then run it.
 
@@ -41,14 +41,14 @@ zip
 For 32-bit environment, download x86 zip archive from
 packages.groonga.org:
 
-  * http://packages.groonga.org/windows/groonga/groonga-6.0.2-x86.zip
+  * http://packages.groonga.org/windows/groonga/groonga-6.0.4-x86.zip
 
 Then extract it.
 
 For 64-bit environment, download x64 zip archive from
 packages.groonga.org:
 
-  * http://packages.groonga.org/windows/groonga/groonga-6.0.2-x64.zip
+  * http://packages.groonga.org/windows/groonga/groonga-6.0.4-x64.zip
 
 Then extract it.
 
@@ -66,27 +66,27 @@ Windows. Here are required tools:
 
 Download zipped source from packages.groonga.org:
 
-  * http://packages.groonga.org/source/groonga/groonga-6.0.2.zip
+  * http://packages.groonga.org/source/groonga/groonga-6.0.4.zip
 
 Then extract it.
 
 Move to the Groonga's source folder::
 
-  > cd c:\Users\%USERNAME%\Downloads\groonga-6.0.2
+  > cd c:\Users\%USERNAME%\Downloads\groonga-6.0.4
 
 Configure by ``cmake``. The following commnad line is for 64-bit
 version. To build 32-bit version, use ``-G "Visual Studio 12 2013"``
 parameter instead::
 
-  groonga-6.0.2> cmake . -G "Visual Studio 12 2013 Win64" -DCMAKE_INSTALL_PREFIX=C:\Groonga
+  groonga-6.0.4> cmake . -G "Visual Studio 12 2013 Win64" -DCMAKE_INSTALL_PREFIX=C:\Groonga
 
 Build::
 
-  groonga-6.0.2> cmake --build . --config Release
+  groonga-6.0.4> cmake --build . --config Release
 
 Install::
 
-  groonga-6.0.2> cmake --build . --config Release --target Install
+  groonga-6.0.4> cmake --build . --config Release --target Install
 
 After the above steps, :doc:`/reference/executables/groonga` is found at
 ``c:\Groonga\bin\groonga.exe``.

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

@@ -7,6 +7,135 @@
 News
 ====
 
+.. _release-6-0-4:
+
+Release 6.0.4 - 2016-06-06
+--------------------------
+
+It's a bug fix release of 6.0.3. It's recommend that Groonga 6.0.3
+users upgrade to 6.0.4. This release fixes some search related
+problem.
+
+Fixes
+^^^^^
+
+* [:doc:`/reference/commands/select`] Fixed a bug that ``--drilldown``
+  against a temporary column created by ``--columns`` refers freed
+  memory.
+
+* Fixed a bug that search with large index may refer invalid data. It
+  takes a long time to return search result.
+  [GitHub#548][groonga-dev,04028][Reported by Atsushi Shinoda]
+
+Thanks
+^^^^^^
+
+* Atsushi Shinoda
+
+.. _release-6-0-3:
+
+Release 6.0.3 - 2016-05-29
+--------------------------
+
+Improvements
+^^^^^^^^^^^^
+
+* [experimental] Added ``GRN_II_OVERLAP_TOKEN_SKIP_ENABLE`` and
+  ``GRN_NGRAM_TOKENIZER_REMOVE_BLANK_DISABLE`` environment variables
+  to improve performance of N-gram tokenizer.  [GitHub#533][Patch by
+  Naoya Murakami]
+
+* [:doc:`/reference/commands/table_create`] Stopped to ignore
+  nonexistent default tokenizer, normalizer or token filters. In the
+  previous versions, Groonga ignored a typo in
+  ``--default_tokenizer``, ``--normalizer`` or ``--token_filters``
+  parameter silently. It caused a delay in finding problems.
+
+* [:doc:`/reference/commands/select`] output_columns v1: Supported
+  expression such as ``snippet_html(...)`` in output_columns.
+
+* [:doc:`/reference/commands/select`] Removed a limitation about the
+  number of labeled drilldowns. In the previous versions, the number
+  of max labeled drilldowns is limited to 10.
+
+* [:doc:`/reference/functions/number_classify`] Added a number
+  plugin. Use ``number_classify`` function to classify by value.
+
+* Added a time plugin. Use ``time_classify_second``,
+  ``time_classify_minute``, ``time_classify_hour``,
+  ``time_classify_day``, ``time_classify_week``,
+  ``time_classify_month``, ``time_classify_year`` function to classify
+  by value.
+
+* [:doc:`/reference/commands/select`] Supported dynamic column
+  creation which is used in ``output_columns``, ``drilldown`` or
+  ``sortby`` [GitHub#539,#541,#542,#544,#545][Patch by Naoya Murakami]::
+
+    select \
+      --columns[LABEL].stage filtered \
+      --columns[LABEL].type ShortText \
+      --columns[LABEL].flags COLUMN_SCALAR \
+      --columns[LABEL].value 'script syntax expression' \
+      ...
+
+* [experimental][:doc:`/reference/commands/select`] Improved
+  performance for range/equal search and enough filtered case. Set
+  ``GRN_TABLE_SELECT_ENOUGH_FILTERED_RATIO`` environment variable to
+  enable this feature.
+
+* [:doc:`/reference/commands/select`] Supported index used search for
+  filtered tables.
+
+* Supported to detect changed database isn't closed. This feature is
+  useful to check database corruption when Groonga is crashed
+  unexpectedly.
+
+* [:doc:`/reference/executables/grndb`] Supported detecting database
+  wasn't closed successfully case.
+
+* Added ``--drilldown_filter``.
+
+* Supported ``filter`` in labeled drilldown.
+
+* Improved performance for using [:doc:`/reference/functions/between`]
+  without index. By between() optimization, there is a case that range
+  search is 100x faster than the previous version of between().
+
+* [:doc:`/reference/functions/record_number`] Supported window function.
+
+* [experimental][:doc:`/reference/commands/select`] Supported ``--slices``.
+
+* [:doc:`/reference/commands/select`] Deprecated ``--sortby`` and
+  ``--drilldown_sortby``. Use ``--sort_keys`` and
+  ``-drilldown_sort_keys`` instead.
+
+* [:doc:`/reference/commands/select`] Deprecated ``--drilldown[...]``.
+  Use ``--drilldowns[...]`` instead.
+
+* Added [:doc:`/reference/command/command_version`] 3. It uses object
+  literal based envelope.
+
+* [groonga-httpd] Updated bundled nginx version to 1.11.0.
+
+Fixes
+^^^^^
+
+* [:doc:`/reference/commands/select`] output_columns v2: Fixed a bug
+  that ``*`` isn't expand to columns correctly.
+
+* Fixed a bug that 1usec information is lost for time value.
+
+* Fixed a crash bug when a mruby plugin is initialized with multiple
+  threads.
+
+* Fixed a bug that static indexing crashes if a posting list is very long.
+  This bug may occur against enormous size of database. [GitHub#546]
+
+Thanks
+^^^^^^
+
+* Naoya Murakami
+
 .. _release-6-0-2:
 
 Release 6.0.2 - 2016-04-29

data/vendor/local/share/doc/groonga/ja/html/_sources/reference/commands/select.txt

@@ -47,16 +47,21 @@ optional::
          [adjuster=null]
          [drilldown_calc_types=NONE]
          [drilldown_calc_target=null]
+         [sort_keys=null]
+         [drilldown_sort_keys=null]
 
 ``select`` has the following named parameters for advanced drilldown:
 
-  * ``drilldown[${LABEL}].keys=null``
-  * ``drilldown[${LABEL}].sortby=null``
-  * ``drilldown[${LABEL}].output_columns="_key, _nsubrecs"``
-  * ``drilldown[${LABEL}].offset=0``
-  * ``drilldown[${LABEL}].limit=10``
-  * ``drilldown[${LABEL}].calc_types=NONE``
-  * ``drilldown[${LABEL}].calc_target=null``
+  * ``drilldowns[${LABEL}].keys=null``
+  * ``drilldowns[${LABEL}].sortby=null``
+  * ``drilldowns[${LABEL}].output_columns="_key, _nsubrecs"``
+  * ``drilldowns[${LABEL}].offset=0``
+  * ``drilldowns[${LABEL}].limit=10``
+  * ``drilldowns[${LABEL}].calc_types=NONE``
+  * ``drilldowns[${LABEL}].calc_target=null``
+
+.. deprecated:: 6.0.3
+  ``drilldown[...]`` syntax is deprecated, Use ``drilldowns[...]`` instead.
 
 You can use one or more alphabets, digits, ``_`` and ``.`` for
 ``${LABEL}``. For example, ``parent.sub1`` is a valid ``${LABEL}``.
@@ -65,15 +70,15 @@ Parameters that have the same ``${LABEL}`` are grouped.
 
 For example, the following parameters specify one drilldown:
 
-  * ``--drilldown[label].keys column``
-  * ``--drilldown[label].sortby -_nsubrecs``
+  * ``--drilldowns[label].keys column``
+  * ``--drilldowns[label].sortby -_nsubrecs``
 
 The following parameters specify two drilldowns:
 
-  * ``--drilldown[label1].keys column1``
-  * ``--drilldown[label1].sortby -_nsubrecs``
-  * ``--drilldown[label2].keys column2``
-  * ``--drilldown[label2].sortby _key``
+  * ``--drilldowns[label1].keys column1``
+  * ``--drilldowns[label1].sortby -_nsubrecs``
+  * ``--drilldowns[label2].keys column2``
+  * ``--drilldowns[label2].sortby _key``
 
 Usage
 -----
@@ -557,7 +562,8 @@ more searches aren't executed. And no records are matched.
 ``query_expansion``
 """""""""""""""""""
 
-Deprecated. Use :ref:`select-query-expander` instead.
+.. deprecated:: 3.0.2
+   Use :ref:`select-query-expander` instead.
 
 .. _select-query-flags:
 
@@ -789,14 +795,22 @@ values except ``_score`` are outputted.
 ``sortby``
 """"""""""
 
+.. deprecated:: 6.0.3
+   Use :ref:`select-sort-keys` instead.
+
+.. _select-sort-keys:
+
+``sort_keys``
+"""""""""""""
+
 Specifies sort keys separated by ``,``. Each sort key is column
 name.
 
-Here is a simple ``sortby`` usage example.
+Here is a simple ``sort_keys`` usage example.
 
 .. groonga-command
-.. include:: ../../example/reference/commands/select/sortby_simple.log
-.. select Entries --sortby 'n_likes, _id'
+.. include:: ../../example/reference/commands/select/sort_keys_simple.log
+.. select Entries --sort_keys 'n_likes, _id'
 
 The ``select`` command sorts by ``n_likes`` column value in ascending
 order. For records that has the same ``n_likes`` are sorted by ``_id``
@@ -805,21 +819,21 @@ are the case.
 
 If you want to sort in descending order, add ``-`` before column name.
 
-Here is a descending order ``sortby`` usage example.
+Here is a descending order ``sort_keys`` usage example.
 
 .. groonga-command
-.. include:: ../../example/reference/commands/select/sortby_descending.log
-.. select Entries --sortby '-n_likes, _id'
+.. include:: ../../example/reference/commands/select/sort_keys_descending.log
+.. select Entries --sort_keys '-n_likes, _id'
 
 The ``select`` command sorts by ``n_likes`` column value in descending
 order. But ascending order is used for sorting by ``_id``.
 
-You can use ``_score`` pseudo column in ``sortby`` if you use
+You can use ``_score`` pseudo column in ``sort_keys`` if you use
 ``query`` or ``filter`` parameter.
 
 .. groonga-command
-.. include:: ../../example/reference/commands/select/sortby_score_with_query.log
-.. select Entries --match_columns content --query fast --sortby -_score --output_columns '_key, _score'
+.. include:: ../../example/reference/commands/select/sort_keys_score_with_query.log
+.. select Entries --match_columns content --query fast --sort_keys -_score --output_columns '_key, _score'
 
 The ``select`` command sorts matched records by hit score in
 descending order and outputs record key and hit score.
@@ -975,6 +989,14 @@ The ``select`` command outputs the following information:
 ``drilldown_sortby``
 """"""""""""""""""""
 
+.. deprecated:: 6.0.3
+   Use :ref:`select-drilldown-sort-keys` instead.
+
+.. _select-drilldown-sort-keys:
+
+``drilldown_sort_keys``
+"""""""""""""""""""""""
+
 Specifies sort keys for drilldown outputs separated by ``,``. Each
 sort key is column name.
 
@@ -1363,13 +1385,13 @@ configuration for all drilldowns. For example,
 You can use a configuration for each drilldown by the following
 parameters:
 
-  * ``drilldown[${LABEL}].keys``
-  * ``drilldown[${LABEL}].sortby``
-  * ``drilldown[${LABEL}].output_columns``
-  * ``drilldown[${LABEL}].offset``
-  * ``drilldown[${LABEL}].limit``
-  * ``drilldown[${LABEL}].calc_types``
-  * ``drilldown[${LABEL}].calc_target``
+  * ``drilldowns[${LABEL}].keys``
+  * ``drilldowns[${LABEL}].sortby``
+  * ``drilldowns[${LABEL}].output_columns``
+  * ``drilldowns[${LABEL}].offset``
+  * ``drilldowns[${LABEL}].limit``
+  * ``drilldowns[${LABEL}].calc_types``
+  * ``drilldowns[${LABEL}].calc_target``
 
 ``${LABEL}`` is a variable. You can use the following characters for
 ``${LABEL}``:
@@ -1389,14 +1411,14 @@ parameters are used for one drilldown.
 
 For example, there are 2 groups for the following parameters:
 
-  * ``--drilldown[label1].keys _key``
-  * ``--drilldown[label1].output_columns _nsubrecs``
-  * ``--drilldown[label2].keys tag``
-  * ``--drilldown[label2].output_columns _key,_nsubrecs``
+  * ``--drilldowns[label1].keys _key``
+  * ``--drilldowns[label1].output_columns _nsubrecs``
+  * ``--drilldowns[label2].keys tag``
+  * ``--drilldowns[label2].output_columns _key,_nsubrecs``
 
-``drilldown[label1].keys`` and ``drilldown[label1].output_columns``
-are grouped. ``drilldown[label2].keys`` and
-``drilldown[label2].output_columns`` are also grouped.
+``drilldowns[label1].keys`` and ``drilldowns[label1].output_columns``
+are grouped. ``drilldowns[label2].keys`` and
+``drilldowns[label2].output_columns`` are also grouped.
 
 In ``label1`` group, ``_key`` is used for group key and ``_nsubrecs``
 is used for output columns.
@@ -1407,28 +1429,28 @@ In ``label2`` group, ``tag`` is used for group key and
 See document for corresponding ``drilldown_XXX`` parameter to know how
 to use it for the following parameters:
 
-  * ``drilldown[${LABEL}].sortby``: :ref:`select-drilldown-sortby`
-  * ``drilldown[${LABEL}].offset``: :ref:`select-drilldown-offset`
-  * ``drilldown[${LABEL}].limit``: :ref:`select-drilldown-limit`
-  * ``drilldown[${LABEL}].calc_types``: :ref:`select-drilldown-calc-types`
-  * ``drilldown[${LABEL}].calc_target``: :ref:`select-drilldown-calc-target`
+  * ``drilldowns[${LABEL}].sortby``: :ref:`select-drilldown-sortby`
+  * ``drilldowns[${LABEL}].offset``: :ref:`select-drilldown-offset`
+  * ``drilldowns[${LABEL}].limit``: :ref:`select-drilldown-limit`
+  * ``drilldowns[${LABEL}].calc_types``: :ref:`select-drilldown-calc-types`
+  * ``drilldowns[${LABEL}].calc_target``: :ref:`select-drilldown-calc-target`
 
 The following parameters are needed more description:
 
-  * ``drilldown[${LABEL}].keys``
-  * ``drilldown[${LABEL}].output_columns``
+  * ``drilldowns[${LABEL}].keys``
+  * ``drilldowns[${LABEL}].output_columns``
 
 Output format is different a bit. It's also needed more description.
 
 .. _select-drilldown-label-keys:
 
-``drilldown[${LABEL}].keys``
-""""""""""""""""""""""""""""
+``drilldowns[${LABEL}].keys``
+"""""""""""""""""""""""""""""
 
 :ref:`select-drilldown` can specify multiple keys for multiple
 drilldowns. But it can't specify multiple keys for one drilldown.
 
-``drilldown[${LABEL}].keys`` can't specify multiple keys for multiple
+``drilldowns[${LABEL}].keys`` can't specify multiple keys for multiple
 drilldowns. But it can specify multiple keys for one drilldown.
 
 You can specify multiple keys separated by "``,``".
@@ -1441,8 +1463,8 @@ column values:
 .. select Entries \
 ..   --limit -1 \
 ..   --output_column tag,n_likes \
-..   --drilldown[tag.n_likes].keys tag,n_likes \
-..   --drilldown[tag.n_likes].output_columns _value.tag,_value.n_likes,_nsubrecs
+..   --drilldowns[tag.n_likes].keys tag,n_likes \
+..   --drilldowns[tag.n_likes].output_columns _value.tag,_value.n_likes,_nsubrecs
 
 ``tag.n_likes`` is used as the label for the drilldown parameters
 group. You can refer grouped keys by ``_value.${KEY_NAME}`` syntax in
@@ -1451,22 +1473,22 @@ column name to be used by group key. ``tag`` and ``n_likes`` are
 ``${KEY_NAME}`` in this case.
 
 Note that you can't use ``_value.${KEY_NAME}`` syntax when you just
-specify one key as ``drilldown[${LABEL}].keys`` like ``--drilldown[tag].keys
+specify one key as ``drilldowns[${LABEL}].keys`` like ``--drilldowns[tag].keys
 tag``. You should use ``_key`` for the case. It's the same rule in
 :ref:`select-drilldown-output-columns`.
 
 .. _select-drilldown-label-output-columns:
 
-``drilldown[${LABEL}].output_columns``
-""""""""""""""""""""""""""""""""""""""
+``drilldowns[${LABEL}].output_columns``
+"""""""""""""""""""""""""""""""""""""""
 
 It's almost same as :ref:`select-drilldown-output-columns`. The
 difference between :ref:`select-drilldown-output-columns` and
-``drilldown[${LABEL}].output_columns`` is how to refer group keys.
+``drilldowns[${LABEL}].output_columns`` is how to refer group keys.
 
 :ref:`select-drilldown-output-columns` uses ``_key``
 :doc:`/reference/columns/pseudo` to refer group
-key. ``drilldown[${LABEL}].output_columns`` also uses ``_key``
+key. ``drilldowns[${LABEL}].output_columns`` also uses ``_key``
 :doc:`/reference/columns/pseudo` to refer group key when you specify
 only one group key by :ref:`select-drilldown-label-keys`.
 
@@ -1478,12 +1500,12 @@ Here is an example to refer single group key by ``_key``
 .. select Entries \
 ..   --limit 0 \
 ..   --output_column _id \
-..   --drilldown[tag.n_likes].keys tag \
-..   --drilldown[tag.n_likes].output_columns _key
+..   --drilldowns[tag.n_likes].keys tag \
+..   --drilldowns[tag.n_likes].output_columns _key
 
 But you can't refer each group key by ``_key``
 :doc:`/reference/columns/pseudo` in
-``drilldown[${LABEL}].output_columns``. You need to use
+``drilldowns[${LABEL}].output_columns``. You need to use
 ``_value.${KEY_NAME}`` syntax. ``${KEY_NAME}`` is a column name that is
 used for group key in :ref:`select-drilldown-label-keys`.
 
@@ -1495,8 +1517,8 @@ Here is an example to refer each group key in multiple group keys by
 .. select Entries \
 ..   --limit 0 \
 ..   --output_column _id \
-..   --drilldown[tag.n_likes].keys tag,n_likes \
-..   --drilldown[tag.n_likes].output_columns _value.tag,_value.n_likes
+..   --drilldowns[tag.n_likes].keys tag,n_likes \
+..   --drilldowns[tag.n_likes].output_columns _value.tag,_value.n_likes
 
 .. tip:: Why ``_value.${KEY_NAME}`` syntax?
 
@@ -1504,7 +1526,7 @@ Here is an example to refer each group key in multiple group keys by
 
    ``_key`` is a vector value. The vector value is consists of all
    group keys. You can see byte sequence of the vector value by
-   referring ``_key`` in ``drilldown[${LABEL}].output_columns``.
+   referring ``_key`` in ``drilldowns[${LABEL}].output_columns``.
 
    There is one grouped record in ``_value`` to refer each grouped
    values when you specify multiple group keys to
@@ -1518,8 +1540,8 @@ Here is an example to refer each group key in multiple group keys by
 
 .. _select-drilldown-label-output-format:
 
-Output format for ``drilldown[${LABEL}]`` style
-"""""""""""""""""""""""""""""""""""""""""""""""
+Output format for ``drilldowns[${LABEL}]`` style
+""""""""""""""""""""""""""""""""""""""""""""""""
 
 There is a difference in output format between :ref:`select-drilldown`
 and :ref:`select-drilldown-label-keys`. :ref:`select-drilldown` uses
@@ -1710,7 +1732,7 @@ If ``select`` fails, error details are in ``HEADER``.
 See :doc:`/reference/command/output_format` for ``HEADER``.
 
 There are zero or more ``DRILLDOWN_RESULT``. If no ``drilldown`` and
-``drilldown[${LABEL}].keys`` are specified, they are omitted like the
+``drilldowns[${LABEL}].keys`` are specified, they are omitted like the
 following::
 
   [
@@ -1733,7 +1755,7 @@ column1, column2"``, multiple ``DRILLDOWN_RESULT`` exist::
     ]
   ]
 
-If ``drilldown[${LABEL}].keys`` is used, only one ``DRILLDOWN_RESULT``
+If ``drilldowns[${LABEL}].keys`` is used, only one ``DRILLDOWN_RESULT``
 exist::
 
   [
@@ -1745,7 +1767,7 @@ exist::
   ]
 
 ``DRILLDOWN_RESULT`` format is different between ``drilldown`` and
-``drilldown[${LABEL}].keys``. It's described later.
+``drilldowns[${LABEL}].keys``. It's described later.
 
 ``SEARCH_RESULT`` is the following format::
 
@@ -1844,7 +1866,7 @@ Here is an example ``RECORDS``::
   ]
 
 ``DRILLDOWN_RESULT`` format is different between ``drilldown`` and
-``drilldown[${LABEL}].keys``.
+``drilldowns[${LABEL}].keys``.
 
 ``drilldown`` uses the same format as ``SEARCH_RESULT``::
 
@@ -1857,8 +1879,8 @@ Here is an example ``RECORDS``::
 And ``drilldown`` generates one or more ``DRILLDOWN_RESULT`` when
 :ref:`select-drilldown` has one ore more keys.
 
-``drilldown[${LABEL}].keys`` uses the following format. Multiple
-``drilldown[${LABEL}].keys`` are mapped to one object (key-value
+``drilldowns[${LABEL}].keys`` uses the following format. Multiple
+``drilldowns[${LABEL}].keys`` are mapped to one object (key-value
 pairs)::
 
   {
@@ -1880,7 +1902,7 @@ pairs)::
     ]
   }
 
-Each ``drilldown[${LABEL}].keys`` corresponds to the following::
+Each ``drilldowns[${LABEL}].keys`` corresponds to the following::
 
   "LABEL": [
     [N_HITS],
@@ -1897,7 +1919,7 @@ The following value part is the same format as ``SEARCH_RESULT``::
   ]
 
 See also :ref:`select-drilldown-label-output-format` for
-``drilldown[${LABEL}]`` style drilldown output format.
+``drilldowns[${LABEL}]`` style drilldown output format.
 
 
 See also