[Groonga-commit] groonga/groonga at 739f9b0 [master] doc: add description about exception case for sort_keys

Back to archive index

Kentaro Hayashi null+****@clear*****
Fri Oct 6 19:28:11 JST 2017


Kentaro Hayashi	2017-10-06 19:28:11 +0900 (Fri, 06 Oct 2017)

  New Revision: 739f9b012d9caa7709666261c6fd57f59b9b7d1a
  https://github.com/groonga/groonga/commit/739f9b012d9caa7709666261c6fd57f59b9b7d1a

  Message:
    doc: add description about exception case for sort_keys

  Modified files:
    doc/source/reference/commands/logical_select.rst

  Modified: doc/source/reference/commands/logical_select.rst (+13 -1)
===================================================================
--- doc/source/reference/commands/logical_select.rst    2017-10-06 13:44:48 +0900 (8ec23e17d)
+++ doc/source/reference/commands/logical_select.rst    2017-10-06 19:28:11 +0900 (f400dc6a3)
@@ -139,7 +139,10 @@ But there are some differences from :doc:`select`:
   * ``logical_table`` and ``shard_key`` parameters are required
     instead of ``table`` parameter.
   * ``sort_keys`` isn't supported when multiple shards are used. (Only
-    one shard is used, they are supported.)
+    one shard is used, they are supported. There is one exception
+    about ``sort_keys`` for multiple shards. When ``shard_keys`` and
+    ``sort_keys`` are same, they are supported. See
+    :ref:`logical-select-sort-keys` about details)
   * ``_value.${KEY_NAME}`` in ``drilldowns[${LABEL}].sort_keys``
     doesn't work with multiple shards. It works with one
     shard. ``_key`` in ``drilldowns[${LABEL}].sort_keys`` work with
@@ -545,6 +548,15 @@ Corresponds to :ref:`select-sort-keys` in :doc:`select`. See
 search target shards is one. If the number of search target shards is
 larger than one, ``sort_keys`` doesn't work.
 
+.. note::
+
+   There is one exception for multiple shards. When the same value is
+   specified for ``shard_key`` and ``sort_keys``, they are supported.
+   ``logical_select`` processes target shards one by one by ascending
+   order. Thus, in this process, magnitude correlation about the value
+   of ``shard_key`` is kept among them. This is because ``sort_keys``
+   is supported when ``shard_key`` and ``sort_keys`` is same.
+
 Here is an example that uses only one shard:
 
 .. groonga-command
-------------- next part --------------
HTML����������������������������...
URL: https://lists.osdn.me/mailman/archives/groonga-commit/attachments/20171006/8eefa565/attachment-0001.htm 



More information about the Groonga-commit mailing list
Back to archive index