Tarantool development patches archive
 help / color / mirror / Atom feed
From: Nikita Pettik <korablev@tarantool.org>
To: Ilya Kosarev <i.kosarev@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH] tuple: drop extra restrictions for multikey index
Date: Mon, 3 Aug 2020 08:42:35 +0000	[thread overview]
Message-ID: <20200803084235.GA8230@tarantool.org> (raw)
In-Reply-To: <1596201198.417099977@f747.i.mail.ru>

On 31 Jul 16:13, Ilya Kosarev wrote:
> 
> Hi!
>  
> Thanks for your review.
>  
> See my answers below.
>  
> I will send v2 of the patch but i think 2 questions above should be clarified.
>   
> >Четверг, 30 июля 2020, 17:26 +03:00 от Nikita Pettik <korablev@tarantool.org>:
> > 
> >On 24 Jul 23:06, Ilya Kosarev wrote:
> >
> >I *strongly dislike* that the patch is in fact should be 10 lines
> >but instead we have 250 diff lines. Please elaborate on that
> >(comments above are mostly about that).
> Well, this patch reverts the majority of changes from
> 4cf94ef8cb90b84ea71f313cff3e016f85894fd5 (tuple: make fields nullable
> by default except array/map). That is where the size comes from.

Then you are able simply to revert that patch and introduce new one.
But I'd provide only required fixes.

> >> diff --git a/src/box/memtx_space.c b/src/box/memtx_space.c
> >> index 8452ab430..875592026 100644
> >> --- a/src/box/memtx_space.c
> >> +++ b/src/box/memtx_space.c
> >> @@ -589,9 +589,7 @@ memtx_space_ephemeral_rowid_next(struct space *space, uint64_t *rowid)
> >> static int
> >> memtx_space_check_index_def(struct space *space, struct index_def *index_def)
> >> {
> >> - struct key_def *key_def = index_def->key_def;
> >> -
> >> - if (key_def->is_nullable) {
> >> + if (index_def->key_def->is_nullable) {
> >
> >Again I see this redundant diff. Please drop it, it doesn't fix
> >refactor/fix anything but makes diff bigger and complicates git
> >history.
> The problem is that this is the reversion of that diff. Well, I guess
> as far as that patch was pushed to master we can leave that change
> there and revert only the meaningful part?

Yes.

      reply	other threads:[~2020-08-03  8:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-24 20:06 Ilya Kosarev
2020-07-30 14:26 ` Nikita Pettik
2020-07-31 13:13   ` Ilya Kosarev
2020-08-03  8:42     ` 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=20200803084235.GA8230@tarantool.org \
    --to=korablev@tarantool.org \
    --cc=i.kosarev@tarantool.org \
    --cc=tarantool-patches@dev.tarantool.org \
    --subject='Re: [Tarantool-patches] [PATCH] tuple: drop extra restrictions for multikey index' \
    /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