Tarantool development patches archive
 help / color / mirror / Atom feed
From: Vladimir Davydov <vdavydov.dev@gmail.com>
To: Georgy Kirichenko <georgy@tarantool.org>
Cc: tarantool-patches@freelists.org
Subject: Re: [tarantool-patches] [PATCH v3 2/5] Synchronize lua schema update with space cache
Date: Wed, 27 Mar 2019 13:32:29 +0300	[thread overview]
Message-ID: <20190327103229.4mfg6ptmqiz4vdub@esperanza> (raw)
In-Reply-To: <20190327100351.gpo2befo6mulqw2k@esperanza>

On Wed, Mar 27, 2019 at 01:03:51PM +0300, Vladimir Davydov wrote:
> On Fri, Mar 22, 2019 at 03:06:07PM +0300, Georgy Kirichenko wrote:
> > Update lua schema as soon as space cache replace was done instead of
> > doing this while on_commit trigger executes. In opposite then case
> > schema changes would not be visible until commit was finished.
> > 
> > Needed for: #2798
> > ---
> >  src/box/alter.cc | 13 ++++++++-----
> >  1 file changed, 8 insertions(+), 5 deletions(-)
> > 
> > diff --git a/src/box/alter.cc b/src/box/alter.cc
> > index daaa9cd57..275e39dd5 100644
> > --- a/src/box/alter.cc
> > +++ b/src/box/alter.cc
> > @@ -750,8 +750,6 @@ alter_space_commit(struct trigger *trigger, void *event)
> >  		op->commit(alter, txn->signature);
> >  	}
> >  
> > -	trigger_run_xc(&on_alter_space, alter->new_space);
> > -
> >  	alter->new_space = NULL; /* for alter_space_delete(). */
> >  	/*
> >  	 * Delete the old version of the space, we are not
> > @@ -787,6 +785,8 @@ alter_space_rollback(struct trigger *trigger, void * /* event */)
> >  	space_swap_triggers(alter->new_space, alter->old_space);
> >  	space_swap_fk_constraints(alter->new_space, alter->old_space);
> >  	space_cache_replace(alter->new_space, alter->old_space);
> > +	trigger_run(&on_alter_space, alter->old_space);
> > +
> >  	alter_space_delete(alter);
> >  }
> >  
> > @@ -888,6 +888,7 @@ alter_space_do(struct txn *txn, struct alter_space *alter)
> >  	 * cache with it.
> >  	 */
> >  	space_cache_replace(alter->old_space, alter->new_space);
> > +	trigger_run_xc(&on_alter_space, alter->new_space);
> 
> The comment right above says that this function must not throw an
> exception here so I guess we should use _xc free variant. Not that it
> really matters, as on_alter_space trigger can only fail on OOM, which
> is hardly ever possible.

Guess we should simply fold trigger_run_xc in space_cache_replace and
panic on error.

BTW this is how things were before

commit 1f736583361f537c8e1fb4ea0df0b92ee8d50c6d
Author: Vladimir Davydov <vdavydov.dev@gmail.com>
Date:   Tue Sep 19 14:21:59 2017 +0300

    box: use trigger to push space data to Lua

    Currently, it is done by space_cache_replace/delete which violates
    incapsulation. Let's introduce a trigger that is fired after a change in
    a space definition is committed and use it to propagate changes to Lua.
    Patch by @kostja.

  reply	other threads:[~2019-03-27 10:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-22 12:06 [tarantool-patches] [PATCH v3 0/5] Transaction in replication protocol Georgy Kirichenko
2019-03-22 12:06 ` [tarantool-patches] [PATCH v3 1/5] Abort vinyl index creation in case of truncation rollback Georgy Kirichenko
2019-03-27  9:59   ` Vladimir Davydov
2019-03-22 12:06 ` [tarantool-patches] [PATCH v3 2/5] Synchronize lua schema update with space cache Georgy Kirichenko
2019-03-27 10:03   ` Vladimir Davydov
2019-03-27 10:32     ` Vladimir Davydov [this message]
2019-03-27 11:45       ` [tarantool-patches] " Konstantin Osipov
2019-03-22 12:06 ` [tarantool-patches] [PATCH v3 3/5] Require for single statement not autocommit in case of ddl Georgy Kirichenko
2019-03-27 10:49   ` Vladimir Davydov
2019-03-22 12:06 ` [tarantool-patches] [PATCH v3 4/5] Transaction support for applier Georgy Kirichenko
2019-03-27 11:41   ` Vladimir Davydov
2019-03-27 11:48   ` Vladimir Davydov
2019-03-22 12:06 ` [tarantool-patches] [PATCH v3 5/5] Raise an error if remote transaction produces non-local changes Georgy Kirichenko
2019-03-27 12:06   ` Vladimir Davydov

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=20190327103229.4mfg6ptmqiz4vdub@esperanza \
    --to=vdavydov.dev@gmail.com \
    --cc=georgy@tarantool.org \
    --cc=tarantool-patches@freelists.org \
    --subject='Re: [tarantool-patches] [PATCH v3 2/5] Synchronize lua schema update with space cache' \
    /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