From: Kirill Shcherbatov <kshcherbatov@tarantool.org> To: tarantool-patches@freelists.org, Vladimir Davydov <vdavydov.dev@gmail.com> Cc: Alexandr Lyapunov <aleks@tarantool.org> Subject: Re: [tarantool-patches] Re: [PATCH v3 7/7] memtx: introduce tuple compare hint Date: Tue, 26 Feb 2019 15:10:07 +0300 [thread overview] Message-ID: <4c97b16c-19ee-402f-f692-96dbc1cd94f6@tarantool.org> (raw) In-Reply-To: <20190225174437.yagywystuzbl7skp@esperanza> > See a few minor comments inline. Apart from them the patch is fine by > me, but as Kostja justifiably noted, may be it's worth enabling hints > for all data types, including floating point numbers. Then we wouldn't > need the memtx tree parametrization introduced by the previous patches. > OTOH we will probably need it anyway for multikey indexes. We really need memtx tree parametrization at least because multikey index tree has own MEMTX_TREE_COMPARE/MEMTX_TREE_COMPARE_KEY functions (that use multikey_idx). Show kshch/gh-1257-multikey-index branch for more details. >> +template<bool is_nullable> >> +static uint64_t >> +key_hint_uint(const char *key, struct key_def *key_def) >> +{ >> + (void)key_def; >> + assert(key_part_is_nullable(key_def->parts) == is_nullable); >> + assert(key_def->parts->type == FIELD_TYPE_UNSIGNED || >> + key_def->parts->type == FIELD_TYPE_INTEGER); > > FIELD_TYPE_INTEGER? How can that be? I've reused it below. But ok, let's just inline it. > Should be buf[8]? Yep.
prev parent reply other threads:[~2019-02-26 12:10 UTC|newest] Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-02-22 15:42 [PATCH v3 0/7] box: introduce hint option for memtx tree index Kirill Shcherbatov 2019-02-22 15:42 ` [PATCH v3 1/7] memtx: introduce universal iterator_pool Kirill Shcherbatov 2019-02-22 18:37 ` [tarantool-patches] " Konstantin Osipov 2019-02-23 12:03 ` Kirill Shcherbatov 2019-02-25 16:14 ` Vladimir Davydov 2019-02-25 16:39 ` [tarantool-patches] " Kirill Shcherbatov 2019-02-25 17:14 ` Vladimir Davydov 2019-02-24 6:56 ` [tarantool-patches] " Vladimir Davydov 2019-02-24 17:15 ` Konstantin Osipov 2019-02-24 18:22 ` Vladimir Davydov 2019-02-25 16:46 ` [tarantool-patches] " Konstantin Osipov 2019-02-25 17:15 ` Vladimir Davydov 2019-02-22 15:42 ` [PATCH v3 2/7] lib: fix undef _api_name in bps_tree header Kirill Shcherbatov 2019-02-22 18:37 ` [tarantool-patches] " Konstantin Osipov 2019-02-25 15:32 ` Vladimir Davydov 2019-02-22 15:42 ` [PATCH v3 3/7] lib: introduce BPS_TREE_IDENTICAL custom comparator Kirill Shcherbatov 2019-02-25 15:33 ` Vladimir Davydov 2019-02-22 15:42 ` [PATCH v3 4/7] memtx: hide index implementation details from header Kirill Shcherbatov 2019-02-22 18:40 ` [tarantool-patches] " Konstantin Osipov 2019-02-25 15:33 ` Vladimir Davydov 2019-02-22 15:42 ` [PATCH v3 5/7] memtx: rework memtx_tree to store arbitrary nodes Kirill Shcherbatov 2019-02-25 16:57 ` Vladimir Davydov 2019-02-26 12:10 ` [tarantool-patches] " Kirill Shcherbatov 2019-02-22 15:42 ` [PATCH v3 6/7] memtx: rename memtx_tree.c to memtx_tree_impl.h Kirill Shcherbatov 2019-02-22 15:42 ` [PATCH v3 7/7] memtx: introduce tuple compare hint Kirill Shcherbatov 2019-02-25 17:44 ` Vladimir Davydov 2019-02-26 12:10 ` Kirill Shcherbatov [this message]
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=4c97b16c-19ee-402f-f692-96dbc1cd94f6@tarantool.org \ --to=kshcherbatov@tarantool.org \ --cc=aleks@tarantool.org \ --cc=tarantool-patches@freelists.org \ --cc=vdavydov.dev@gmail.com \ --subject='Re: [tarantool-patches] Re: [PATCH v3 7/7] memtx: introduce tuple compare hint' \ /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