From: Vladimir Davydov <vdavydov.dev@gmail.com> To: kostja@tarantool.org Cc: tarantool-patches@freelists.org Subject: [PATCH v2 1/7] vinyl: do not store meta in secondary index runs Date: Tue, 21 Aug 2018 14:15:34 +0300 [thread overview] Message-ID: <98b102827b334d6a8664a7ea6f78d01d1880beef.1534847663.git.vdavydov.dev@gmail.com> (raw) In-Reply-To: <cover.1534847663.git.vdavydov.dev@gmail.com> In-Reply-To: <cover.1534847663.git.vdavydov.dev@gmail.com> Currenlty, tuple meta is only needed for storing statement flags in run files. In the scope of #2129 two statement flags will be introduced, VY_STMT_SKIP_READ and VY_STMT_DEFERRED_DELETE. None of them makes any sense for secondary indexes. If we encode meta for secondary index statements, we will have to either clear the flags on the upper level (e.g. in the write iterator) or filter them out before encoding a statement. Alternatively, we can skip encoding meta for secondary index statements altogether, and this is what this patch does, because it's the simplest and clearest method for now. If tuple meta is ever used for storing anything else besides statement flags or a new statement flag appears that may be used with secondary index statements, we will recover the code and mask out those flags for secondary indexes. --- src/box/vy_stmt.c | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/src/box/vy_stmt.c b/src/box/vy_stmt.c index d6ebee80..37da282d 100644 --- a/src/box/vy_stmt.c +++ b/src/box/vy_stmt.c @@ -615,8 +615,11 @@ vy_stmt_encode_secondary(const struct tuple *value, request.key = extracted; request.key_end = extracted + size; } - if (vy_stmt_meta_encode(value, &request) != 0) - return -1; + /* + * Note, all flags used with vinyl statements make sense + * only for primary indexes so we do not encode meta for + * secondary index statements. + */ xrow->bodycnt = xrow_encode_dml(&request, xrow->body); if (xrow->bodycnt < 0) return -1; -- 2.11.0
next prev parent reply other threads:[~2018-08-21 11:15 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-08-21 11:15 [PATCH v2 0/7] vinyl: eliminate disk read on REPLACE/DELETE Vladimir Davydov 2018-08-21 11:15 ` Vladimir Davydov [this message] 2018-08-21 15:08 ` [PATCH v2 1/7] vinyl: do not store meta in secondary index runs Konstantin Osipov 2018-08-21 11:15 ` [PATCH v2 2/7] vinyl: teach write iterator to return overwritten tuples Vladimir Davydov 2018-08-21 15:14 ` Konstantin Osipov 2018-08-21 15:37 ` Vladimir Davydov 2018-08-21 11:15 ` [PATCH v2 3/7] vinyl: prepare write iterator heap comparator for deferred DELETEs Vladimir Davydov 2018-08-21 15:38 ` Konstantin Osipov 2018-08-21 11:15 ` [PATCH v2 4/7] vinyl: allow to skip certain statements on read Vladimir Davydov 2018-08-21 15:39 ` Konstantin Osipov 2018-08-21 11:15 ` [PATCH v2 5/7] Introduce _vinyl_deferred_delete system space Vladimir Davydov 2018-08-21 15:42 ` Konstantin Osipov 2018-08-22 17:04 ` Vladimir Davydov 2018-08-21 11:15 ` [PATCH v2 6/7] vinyl: zap vy_mem::min_lsn and rename max_lsn to dump_lsn Vladimir Davydov 2018-08-21 15:44 ` Konstantin Osipov 2018-08-22 13:00 ` Vladimir Davydov 2018-08-21 11:15 ` [PATCH v2 7/7] vinyl: eliminate disk read on REPLACE/DELETE Vladimir Davydov 2018-08-21 16:13 ` Konstantin Osipov 2018-08-22 17:08 ` Vladimir Davydov 2018-08-22 17:50 ` [PATCH v2 0/7] " Vladimir Davydov
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=98b102827b334d6a8664a7ea6f78d01d1880beef.1534847663.git.vdavydov.dev@gmail.com \ --to=vdavydov.dev@gmail.com \ --cc=kostja@tarantool.org \ --cc=tarantool-patches@freelists.org \ --subject='Re: [PATCH v2 1/7] vinyl: do not store meta in secondary index runs' \ /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