Tarantool development patches archive
 help / color / mirror / Atom feed
From: Vladimir Davydov <vdavydov.dev@gmail.com>
To: "v.shpilevoy@tarantool.org" <v.shpilevoy@tarantool.org>
Cc: Konstantin Osipov <kostja@tarantool.org>,
	tarantool-patches@freelists.org
Subject: Re: [PATCH 2/2] vinyl: zap upsert_format
Date: Mon, 2 Apr 2018 14:06:12 +0300	[thread overview]
Message-ID: <20180402110612.sen2y42ugthjcreh@esperanza> (raw)
In-Reply-To: <76D257AF-8668-41E8-B1EB-2D1E7C541189@tarantool.org>

On Mon, Apr 02, 2018 at 01:58:36PM +0300, v.shpilevoy@tarantool.org wrote:
> 1. This functions seems to be unused. Can you delete it, please?

Already did, in a separate patch:

  https://www.freelists.org/post/tarantool-patches/PATCH-0712-vinyl-zap-vy-mem-update-formats

> > void
> > vy_mem_update_formats(struct vy_mem *mem, struct tuple_format *new_format,
> > -		      struct tuple_format *new_format_with_colmask,
> > -		      struct tuple_format *new_upsert_format)
> > +		      struct tuple_format *new_format_with_colmask)
> > {
> > 	assert(mem->count.rows == 0);
> > 	tuple_format_unref(mem->format);
> > 	tuple_format_unref(mem->format_with_colmask);
> > -	tuple_format_unref(mem->upsert_format);
> > 	mem->format = new_format;
> > 	mem->format_with_colmask = new_format_with_colmask;
> > -	mem->upsert_format = new_upsert_format;
> > 	tuple_format_ref(mem->format);
> > 	tuple_format_ref(mem->format_with_colmask);
> > -	tuple_format_ref(mem->upsert_format);
> > }
> > 
> > void
> > diff --git a/src/box/vy_run.c b/src/box/vy_run.c
> > index da6d5872..637f63fa 100644
> > --- a/src/box/vy_run.c
> > +++ b/src/box/vy_run.c
> > @@ -2205,7 +2202,6 @@ vy_run_rebuild_index(struct vy_run *run, const char *dir,
> 
> 2. Please, update a comment - it seems to be very out of date: user_key_def is omitted,
> and bloom_fpr is already removed.

OK. And it looks like this function should use disk_format instead of
mem_format. I'll update it in a separate patch.

> 
> > 		     const struct key_def *cmp_def,
> > 		     const struct key_def *key_def,
> > 		     struct tuple_format *mem_format,
> > -		     struct tuple_format *upsert_format,
> > 		     const struct index_opts *opts)
> > {
> > 	assert(run->info.bloom == NULL);

      reply	other threads:[~2018-04-02 11:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-30 15:47 [PATCH 0/2] " Vladimir Davydov
2018-03-30 15:47 ` [PATCH 1/2] vinyl: allocate upsert counter on lsregion Vladimir Davydov
2018-04-02 10:27   ` [tarantool-patches] " v.shpilevoy
2018-04-02 10:50     ` Vladimir Davydov
2018-03-30 15:47 ` [PATCH 2/2] vinyl: zap upsert_format Vladimir Davydov
2018-04-02 10:58   ` v.shpilevoy
2018-04-02 11:06     ` Vladimir Davydov [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=20180402110612.sen2y42ugthjcreh@esperanza \
    --to=vdavydov.dev@gmail.com \
    --cc=kostja@tarantool.org \
    --cc=tarantool-patches@freelists.org \
    --cc=v.shpilevoy@tarantool.org \
    --subject='Re: [PATCH 2/2] vinyl: zap upsert_format' \
    /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