From: Nikita Pettik <korablev@tarantool.org> To: tarantool-patches@dev.tarantool.org Cc: v.shpilevoy@tarantool.org Subject: Re: [Tarantool-patches] [PATCH v3 0/2] vinyl: rework upsert operation Date: Sat, 3 Oct 2020 13:52:41 +0000 [thread overview] Message-ID: <20201003135241.GB3158@tarantool.org> (raw) In-Reply-To: <cover.1601729099.git.korablev@tarantool.org> On 03 Oct 16:28, Nikita Pettik wrote: > Issues: > https://github.com/tarantool/tarantool/issues/1622 > https://github.com/tarantool/tarantool/issues/5105 > https://github.com/tarantool/tarantool/issues/5092 > https://github.com/tarantool/tarantool/issues/5107 > Branch: > https://github.com/tarantool/tarantool/tree/np/gh-5107-dont-squash-ops Sorry guys, the real branch is https://github.com/tarantool/tarantool/tree/np/gh-5107-dont-squash-and-merge-ops > @ChangeLog: > - Rework upsert operation in vinyl so that now (gh-5107): > - if upsert can't be applied it is skipped and corresponding error is logged (gh-1622); > - upserts now follow associative property: result of several upserts > doesn't depend on the order of their application (gh-5105); > - upserts referring to -1 fieldno are handled correctly now (gh-5087). > - there's no more upserts squash procedure: upserts referring to the > same field with arithmetic operations are not merged into one > operation since resulting upsert might not be applied - as a result > both upserts would be ignored (meanwhile only one should be). > > Changes in v3: > - Removed upsert squashing procedure; > - Added two additional test covering overflow error during upsert > application; > - Fixed NULL dereference bug in vy_apply_upsert_on_terminal_stmt(). > > Nikita Pettik (2): > vinyl: rework upsert operation > vinyl: remove squash procedures from source code > > src/box/vinyl.c | 2 +- > src/box/vy_stmt.c | 28 +- > src/box/vy_stmt.h | 5 +- > src/box/vy_upsert.c | 302 +++++++++++--------- > src/box/xrow_update.c | 144 ---------- > src/box/xrow_update.h | 14 - > test/unit/vy_iterators_helper.c | 2 +- > test/vinyl/upsert.result | 473 ++++++++++++++++++++++++++++++++ > test/vinyl/upsert.test.lua | 194 +++++++++++++ > 9 files changed, 867 insertions(+), 297 deletions(-) > > -- > 2.17.1 >
next prev parent reply other threads:[~2020-10-03 13:52 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-03 13:28 Nikita Pettik 2020-10-03 13:28 ` [Tarantool-patches] [PATCH v3 1/2] " Nikita Pettik 2020-10-06 22:12 ` Vladislav Shpilevoy 2020-10-09 15:06 ` Nikita Pettik 2020-10-13 19:00 ` Aleksandr Lyapunov 2020-10-14 0:15 ` Nikita Pettik 2020-10-14 8:58 ` Aleksandr Lyapunov 2020-10-14 10:42 ` Nikita Pettik 2020-10-14 11:47 ` Aleksandr Lyapunov 2020-10-15 0:36 ` Nikita Pettik 2020-10-03 13:28 ` [Tarantool-patches] [PATCH v3 2/2] vinyl: remove squash procedures from source code Nikita Pettik 2020-10-03 13:52 ` Nikita Pettik [this message] 2020-10-06 22:12 ` [Tarantool-patches] [PATCH v3 0/2] vinyl: rework upsert operation Vladislav Shpilevoy 2020-10-09 15:10 ` Nikita Pettik 2020-10-11 15:35 ` Vladislav Shpilevoy 2020-10-11 15:35 ` Vladislav Shpilevoy 2020-10-13 10:18 ` Nikita Pettik 2020-10-14 23:44 ` Vladislav Shpilevoy 2020-10-15 1:42 ` Nikita Pettik
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=20201003135241.GB3158@tarantool.org \ --to=korablev@tarantool.org \ --cc=tarantool-patches@dev.tarantool.org \ --cc=v.shpilevoy@tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH v3 0/2] vinyl: rework upsert operation' \ /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