From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Subject: Re: [tarantool-patches] Re: [PATCH v1 1/1] rfc: describe a Tarantool JSON indexes References: <7192ba6c28bf9cd637f7e1e5263bbf9771cc6f44.1532603654.git.kshcherbatov@tarantool.org> <20180727151013.goyfa4uuf7nl7nou@esperanza> From: Kirill Shcherbatov Message-ID: <00b50f7e-55ba-8aae-61f9-1f7b95e72cb8@tarantool.org> Date: Mon, 30 Jul 2018 17:09:30 +0300 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit To: tarantool-patches@freelists.org, Vladislav Shpilevoy , Vladimir Davydov List-ID: > 2. As I remember from verbal discussion, we've decided to do not store > offsets for intermediate nodes. It is too expensive. You actually purpose > to store an offset for each tuple field, even non-indexed. In such a case > the field_map would become bigger than the tuple payload. Field_map is > very expensive storage and should not store non-needed offsets. So you should > not have an offset on [name], on [birthday]. Only on [first] and [last]. > Please, pay attention that we don't allocate offset_slot for intermediate node. This is the only cache for tuple_new operation. offset_slot only for leafs. Without this feature there is no difference with hash.