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 0/2] vinyl: rework upsert internals
Date: Sat, 8 Aug 2020 14:23:01 +0000	[thread overview]
Message-ID: <20200808142301.GA28157@tarantool.org> (raw)
In-Reply-To: <2566473a-c279-5b2a-0864-aee5c0e930db@tarantool.org>

On 31 Jul 01:32, Vladislav Shpilevoy wrote:
> Hi! Thanks for the patchset!
> 
> On 29.07.2020 03:15, 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
> 
> Need a changelog here.

Added in V2:

@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).

      reply	other threads:[~2020-08-08 14:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-29  1:15 Nikita Pettik
2020-07-29  1:15 ` [Tarantool-patches] [PATCH 1/2] vy_stmt: introduce vy_stmt_is_void() helper Nikita Pettik
2020-07-29  1:15 ` [Tarantool-patches] [PATCH 2/2] vinyl: rework upsert operation Nikita Pettik
2020-07-30 23:31   ` Vladislav Shpilevoy
2020-08-02 14:44   ` Vladislav Shpilevoy
2020-08-08 14:51     ` Nikita Pettik
2020-07-30 23:32 ` [Tarantool-patches] [PATCH 0/2] vinyl: rework upsert internals Vladislav Shpilevoy
2020-08-08 14:23   ` Nikita Pettik [this message]

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=20200808142301.GA28157@tarantool.org \
    --to=korablev@tarantool.org \
    --cc=tarantool-patches@dev.tarantool.org \
    --cc=v.shpilevoy@tarantool.org \
    --subject='Re: [Tarantool-patches] [PATCH 0/2] vinyl: rework upsert internals' \
    /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