From: Konstantin Osipov <kostja.osipov@gmail.com>
To: Nikita Pettik <korablev@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org, v.shpilevoy@tarantool.org
Subject: Re: [Tarantool-patches] [PATCH 2/2] vinyl: skip invalid upserts during squash
Date: Thu, 21 May 2020 11:36:01 +0300 [thread overview]
Message-ID: <20200521083601.GA42063@atlas> (raw)
In-Reply-To: <20200521025153.GC19031@tarantool.org>
* Nikita Pettik <korablev@tarantool.org> [20/05/21 05:54]:
> Data will always will be acceptable according to the format because
> PK format can't change.
The format used for squashing may be taken from the primary key
lsm, but there are type constraints which impact even non-indexed
fields.
Imagine nullable -> not null change in SQL, and a pending upsert
which assigns NULL to a not nullable field.
Or addition/removal of is_optional on a field in the format.
We don't allow much there, but it would be good to at least
*consider* what we allow and make sure it's safe.
--
Konstantin Osipov, Moscow, Russia
next prev parent reply other threads:[~2020-05-21 8:36 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-13 21:55 [Tarantool-patches] [PATCH 0/2] Validate result of upserts squash & skip invalid upserts which can't be applied 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 [this message]
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 ` [Tarantool-patches] [PATCH 0/2] Validate result of upserts squash & skip invalid upserts which can't be applied Vladislav Shpilevoy
2020-05-22 2:42 ` 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=20200521083601.GA42063@atlas \
--to=kostja.osipov@gmail.com \
--cc=korablev@tarantool.org \
--cc=tarantool-patches@dev.tarantool.org \
--cc=v.shpilevoy@tarantool.org \
--subject='Re: [Tarantool-patches] [PATCH 2/2] vinyl: skip invalid upserts during squash' \
/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