From: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
To: Nikita Pettik <korablev@tarantool.org>,
tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH 0/2] Validate result of upserts squash & skip invalid upserts which can't be applied
Date: Thu, 21 May 2020 00:13:29 +0200 [thread overview]
Message-ID: <0bdc1b5e-82b4-2e24-ad06-26587b007742@tarantool.org> (raw)
In-Reply-To: <cover.1586808463.git.korablev@tarantool.org>
Thanks for the patchset!
I grepped for other vy_apply_upsert() usage cases and found these:
- vy_build_recover_stmt() - should we patch it too?
- vy_tx_write() - here the upsert is skipped in case of any error, but
what if it was not a ClientError?
On 13/04/2020 23:55, Nikita Pettik wrote:
> Branch: https://github.com/tarantool/tarantool/tree/np/gh-1622-skip-invalid-upserts
> Issue: https://github.com/tarantool/tarantool/issues/1622
>
> In fact, the first patch in series does not make much sense without
> second since otherwise dump or compaction processes (and any other
> operations that read data as well) will fail whenever they are started.
> But still I've divided fix into two patches for the sake of review
> simplicity.
>
> Nikita Pettik (2):
> vinyl: validate resulting tuple after upsert is applied
> vinyl: skip invalid upserts during squash
>
> src/box/vy_history.c | 20 ++-
> src/box/vy_lsm.c | 13 +-
> src/box/vy_tx.c | 29 ++--
> src/box/vy_upsert.c | 4 +
> src/box/vy_write_iterator.c | 34 +++--
> .../vinyl/gh-1622-skip-invalid-upserts.result | 135 ++++++++++++++++++
> .../gh-1622-skip-invalid-upserts.test.lua | 50 +++++++
> 7 files changed, 258 insertions(+), 27 deletions(-)
> create mode 100644 test/vinyl/gh-1622-skip-invalid-upserts.result
> create mode 100644 test/vinyl/gh-1622-skip-invalid-upserts.test.lua
>
next prev parent reply other threads:[~2020-05-20 22:13 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-13 21:55 Nikita Pettik
2020-04-13 21:55 ` [Tarantool-patches] [PATCH 1/2] vinyl: validate resulting tuple after upsert is applied Nikita Pettik
2020-06-22 19:28 ` Aleksandr Lyapunov
2020-04-13 21:55 ` [Tarantool-patches] [PATCH 2/2] vinyl: skip invalid upserts during squash Nikita Pettik
2020-04-13 22:12 ` Konstantin Osipov
2020-05-14 2:11 ` Nikita Pettik
2020-05-14 6:56 ` Konstantin Osipov
2020-05-19 19:10 ` Nikita Pettik
2020-05-19 19:39 ` Konstantin Osipov
2020-05-21 2:51 ` Nikita Pettik
2020-05-21 8:36 ` Konstantin Osipov
2020-05-01 0:31 ` Vladislav Shpilevoy
2020-05-14 2:21 ` Nikita Pettik
2020-05-14 21:32 ` Vladislav Shpilevoy
2020-05-19 18:18 ` Nikita Pettik
2020-05-20 22:13 ` Vladislav Shpilevoy
2020-05-26 21:33 ` Vladislav Shpilevoy
2020-05-27 20:05 ` Nikita Pettik
2020-05-29 21:47 ` Vladislav Shpilevoy
2020-06-01 19:24 ` Nikita Pettik
2020-05-20 22:13 ` Vladislav Shpilevoy [this message]
2020-05-22 2:42 ` [Tarantool-patches] [PATCH 0/2] Validate result of upserts squash & skip invalid upserts which can't be applied Nikita Pettik
2020-05-26 21:33 ` Vladislav Shpilevoy
2020-05-27 20:10 ` Nikita Pettik
2020-06-22 14:13 ` Aleksandr Lyapunov
2020-06-22 20:21 ` Nikita Pettik
2020-06-23 12:32 ` Aleksandr Lyapunov
2020-06-02 21:36 ` Vladislav Shpilevoy
2020-06-02 21:37 ` 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=0bdc1b5e-82b4-2e24-ad06-26587b007742@tarantool.org \
--to=v.shpilevoy@tarantool.org \
--cc=korablev@tarantool.org \
--cc=tarantool-patches@dev.tarantool.org \
--subject='Re: [Tarantool-patches] [PATCH 0/2] Validate result of upserts squash & skip invalid upserts which can'\''t be applied' \
/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