From: Alexander Turenko <alexander.turenko@tarantool.org> To: Vladislav Shpilevoy <v.shpilevoy@tarantool.org> Cc: tarantool-patches@dev.tarantool.org Subject: Re: [Tarantool-patches] [PATCH v3 00/16] module api: extend for external key_def Lua module Date: Thu, 15 Oct 2020 06:09:00 +0300 [thread overview] Message-ID: <20201015030900.aonelxqk33gk6ae3@tkn_work_nb> (raw) In-Reply-To: <cdf03c47-bcaa-d390-a9b7-216badb828fd@tarantool.org> On Thu, Oct 15, 2020 at 01:41:57AM +0200, Vladislav Shpilevoy wrote: > Hi! Thanks for the patchset! > > Are we going to create a docbot request or a documentation ticket > for all these newly exported functions? I will create the issue manually. > > > Alexander Turenko (16): > > module api: get rid of typedef redefinitions > > module api: expose box region > > module api/lua: add luaL_iscdata() function > > lua: factor out tuple encoding from luaT_tuple_new > > lua: don't raise a Lua error from luaT_tuple_new() > > module api/lua: add luaT_tuple_encode() > > module api/lua: expose luaT_tuple_new() > > module api/lua: add API_EXPORT to tuple functions > > module api: add API_EXPORT to key_def functions > > module api: add box_key_def_new_v2() > > module api: add box_key_def_dump_parts() > > module api: expose box_key_def_validate_tuple() > > module api: expose box_key_def_merge() > > module api: expose box_key_def_extract_key() > > module api: add box_key_def_validate_key() > > module api: add box_key_def_validate_full_key() > > Still don't understand why do we need full key validation. > Anyway it won't help in anything. The only purpose I can > think of is kind of a guarantee, that if a key is full and > valid, it will return at most 1 tuple, but it is not so for > non-unique indexes - for them a full and not full keys are > the same. But whatever. But what if a caller knows that a particular key_def corresponds to some unique index and want to ensure that a key is not only valid, but also full? Or it knows that a particular key_def imposes a strict order on a particular tuple stream and want to ensure that compare against given key will impose the same strict ordering? It may be important for pagination.
next prev parent reply other threads:[~2020-10-15 3:08 UTC|newest] Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-12 23:23 Alexander Turenko 2020-10-12 23:23 ` [Tarantool-patches] [PATCH v3 01/16] module api: get rid of typedef redefinitions Alexander Turenko 2020-10-12 23:23 ` [Tarantool-patches] [PATCH v3 02/16] module api: expose box region Alexander Turenko 2020-10-14 23:41 ` Vladislav Shpilevoy 2020-10-15 13:17 ` Alexander Turenko 2020-10-12 23:23 ` [Tarantool-patches] [PATCH v3 03/16] module api/lua: add luaL_iscdata() function Alexander Turenko 2020-10-12 23:23 ` [Tarantool-patches] [PATCH v3 04/16] lua: factor out tuple encoding from luaT_tuple_new Alexander Turenko 2020-10-12 23:23 ` [Tarantool-patches] [PATCH v3 05/16] lua: don't raise a Lua error from luaT_tuple_new() Alexander Turenko 2020-10-14 23:41 ` Vladislav Shpilevoy 2020-10-15 13:17 ` Alexander Turenko 2020-10-12 23:23 ` [Tarantool-patches] [PATCH v3 06/16] module api/lua: add luaT_tuple_encode() Alexander Turenko 2020-10-12 23:23 ` [Tarantool-patches] [PATCH v3 07/16] module api/lua: expose luaT_tuple_new() Alexander Turenko 2020-10-12 23:23 ` [Tarantool-patches] [PATCH v3 08/16] module api/lua: add API_EXPORT to tuple functions Alexander Turenko 2020-10-14 23:41 ` Vladislav Shpilevoy 2020-10-15 2:35 ` Alexander Turenko 2020-10-12 23:23 ` [Tarantool-patches] [PATCH v3 09/16] module api: add API_EXPORT to key_def functions Alexander Turenko 2020-10-12 23:23 ` [Tarantool-patches] [PATCH v3 10/16] module api: add box_key_def_new_v2() Alexander Turenko 2020-10-12 23:23 ` [Tarantool-patches] [PATCH v3 11/16] module api: add box_key_def_dump_parts() Alexander Turenko 2020-10-12 23:23 ` [Tarantool-patches] [PATCH v3 12/16] module api: expose box_key_def_validate_tuple() Alexander Turenko 2020-10-12 23:23 ` [Tarantool-patches] [PATCH v3 13/16] module api: expose box_key_def_merge() Alexander Turenko 2020-10-14 23:41 ` Vladislav Shpilevoy 2020-10-12 23:23 ` [Tarantool-patches] [PATCH v3 14/16] module api: expose box_key_def_extract_key() Alexander Turenko 2020-10-14 23:41 ` Vladislav Shpilevoy 2020-10-15 2:39 ` Alexander Turenko 2020-10-12 23:23 ` [Tarantool-patches] [PATCH v3 15/16] module api: add box_key_def_validate_key() Alexander Turenko 2020-10-14 23:41 ` Vladislav Shpilevoy 2020-10-15 13:18 ` Alexander Turenko 2020-10-12 23:23 ` [Tarantool-patches] [PATCH v3 16/16] module api: add box_key_def_validate_full_key() Alexander Turenko 2020-10-14 23:41 ` [Tarantool-patches] [PATCH v3 00/16] module api: extend for external key_def Lua module Vladislav Shpilevoy 2020-10-15 3:09 ` Alexander Turenko [this message] 2020-10-15 13:19 ` Alexander Turenko 2020-10-16 6:05 ` Alexander Turenko 2020-10-15 20:12 ` Vladislav Shpilevoy
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20201015030900.aonelxqk33gk6ae3@tkn_work_nb \ --to=alexander.turenko@tarantool.org \ --cc=tarantool-patches@dev.tarantool.org \ --cc=v.shpilevoy@tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH v3 00/16] module api: extend for external key_def Lua module' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox