From 78313fe690d016c9473f06b78629d5951731b781 Mon Sep 17 00:00:00 2001 From: Natalia Ogoreltseva Date: Mon, 5 Apr 2021 17:56:51 +0300 Subject: [PATCH] fixes gh-1626 Varbinary supported in bitset indexes --- doc/reference/reference_lua/box_space/create_index.rst | 2 +- doc/release/2.7.1.rst | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/reference/reference_lua/box_space/create_index.rst b/doc/reference/reference_lua/box_space/create_index.rst index 9bddfa09b3..9720bbef43 100644 --- a/doc/reference/reference_lua/box_space/create_index.rst +++ b/doc/reference/reference_lua/box_space/create_index.rst @@ -202,7 +202,7 @@ and what index types are allowed. `. A varbinary byte sequence does not have a :ref:`collation ` because its contents are not UTF-8 characters - - memtx TREE, HASH or BITSET (since version 2.7) indexes; + - memtx TREE, HASH or BITSET (since version :doc:`2.7.1 `) indexes; vinyl TREE indexes - '\\65 \\66 \\67' diff --git a/doc/release/2.7.1.rst b/doc/release/2.7.1.rst index 4fa42d5d85..f6c20f2c3c 100644 --- a/doc/release/2.7.1.rst +++ b/doc/release/2.7.1.rst @@ -40,7 +40,7 @@ Core - Now it is allowed to define an index without extra braces when there is only one part: ``parts = {field1, type1, ...}`` (gh-2866). -- Bitset index now supports the varbinary type (gh-5392). +- :ref:`Bitset index ` now supports the varbinary type (gh-5392). - Index-related options now can’t be specified in their definition due to a more pedantic key-parts verification (gh-5473). - A warning is now logged when schema version is older than last