Tarantool development patches archive
 help / color / mirror / Atom feed
From: Nikita Pettik <korablev@tarantool.org>
To: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH 3/3] upgrade: fix generated sequence upgrade from 2.1
Date: Fri, 21 Feb 2020 18:42:44 +0300	[thread overview]
Message-ID: <20200221154244.GE51816@tarantool.org> (raw)
In-Reply-To: <da0291cced7a8771fa7c2187bff271d148f948b7.1581972845.git.v.shpilevoy@tarantool.org>

On 17 Feb 21:57, Vladislav Shpilevoy wrote:
> The bug was in an attempt to update a record in _space_sequence
> in-place, to add field path and number. This was not properly
> supported by the system space's trigger, and was banned in the
> previous patch of this series.
> 
> But delete + tuple update + insert work fine. The patch uses them.
> 
> To test it the old disabled and heavily outdated
> xlog/upgrade.test.lua was replaced with a smaller analogue, which
> is supposed to be created separately for each upgrade bug.
> According to the new policy of creating test files.
> 
> The patch tries to make it easy to add new upgrade tests and
> snapshots. A new test should consist of fill.lua script to
> populate spaces, snapshot, needed xlogs, and a .test.lua file.
> Fill script and binaries should be in the same folder as test file
> name, which is located in version folder. Like this:

I'm okay with this approach but could you document it somewhere
(e.g. on our wiki github page)?

>  xlog/
>  |
>  + <test_name>.test.lua
>  |
>  +- upgrade/
>     |
>     +- <version>/
>     |   |
>     |   +-<test_name>/
>     |     |
>     |     +- fill.lua
>     |     +- *.snap
>     |     +- *.xlog
> 
> Version is supposed to say explicitly what a version files in
> there have.

Patch itself is LGTM.

  reply	other threads:[~2020-02-21 15:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-17 20:57 [Tarantool-patches] [PATCH 0/3] Fix upgrade from 2.1 sequence Vladislav Shpilevoy
2020-02-17 20:57 ` [Tarantool-patches] [PATCH 1/3] upgrade: add missing sys triggers off and erasure Vladislav Shpilevoy
2020-02-21 15:20   ` Nikita Pettik
2020-02-22 16:17     ` Vladislav Shpilevoy
2020-02-17 20:57 ` [Tarantool-patches] [PATCH 2/3] box: forbid to update/replace _space_sequence Vladislav Shpilevoy
2020-02-21 15:29   ` Nikita Pettik
2020-02-22 16:16     ` Vladislav Shpilevoy
2020-02-17 20:57 ` [Tarantool-patches] [PATCH 3/3] upgrade: fix generated sequence upgrade from 2.1 Vladislav Shpilevoy
2020-02-21 15:42   ` Nikita Pettik [this message]
2020-02-22 16:16     ` Vladislav Shpilevoy
2020-02-24 19:48 ` [Tarantool-patches] [PATCH 0/3] Fix upgrade from 2.1 sequence Kirill Yukhin

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=20200221154244.GE51816@tarantool.org \
    --to=korablev@tarantool.org \
    --cc=tarantool-patches@dev.tarantool.org \
    --cc=v.shpilevoy@tarantool.org \
    --subject='Re: [Tarantool-patches] [PATCH 3/3] upgrade: fix generated sequence upgrade from 2.1' \
    /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