From: Konstantin Osipov <kostja@tarantool.org>
To: tarantool-patches@freelists.org
Cc: Kirill Shcherbatov <kshcherbatov@tarantool.org>,
v.shpilevoy@tarantool.org
Subject: [tarantool-patches] Re: [PATCH v5 3/3] box: introduce func_index
Date: Fri, 26 Jul 2019 22:31:30 +0300 [thread overview]
Message-ID: <20190726193130.GC14622@atlas> (raw)
In-Reply-To: <20190726101032.GB4080@esperanza>
* Vladimir Davydov <vdavydov.dev@gmail.com> [19/07/26 13:14]:
> On Fri, Jul 26, 2019 at 12:57:43PM +0300, Konstantin Osipov wrote:
> > * Vladimir Davydov <vdavydov.dev@gmail.com> [19/07/26 12:54]:
> > >
> > > There's one thing about _func_index space that keeps bothering me: since
> > > insertion of a tuple into this space is a yielding operation and this
> > > operation is executed after insertion of a tuple into _index, we won't
> > > be able to wrap space.create_index() into box.begin/commit, because only
> > > the first DDL statement in a transaction is allowed to be yielding.
> >
> > I think we agreed to solve this to build func index at recovery
> > in _func_index trigger and at create in _func trigger.
>
> I don't understand how it's connected with recovery. Could you please
> elaborate?
>
> Just to be clear, I mean the following:
>
> space.create_index():
> _index:insert{...}
> _func_index:insert{...}
>
> The latter may yield so we can't use box.begin/commit in
> space.create_index() Lua function.
It will yield only during recovery. During normal operation I
thought we're going to build the index ad _index:insert{}
--
Konstantin Osipov, Moscow, Russia
next prev parent reply other threads:[~2019-07-26 19:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-25 18:39 [PATCH v5 0/3] box: functional indexes Kirill Shcherbatov
2019-07-25 18:39 ` [PATCH v5 1/3] box: introduce opts.is_multikey function option Kirill Shcherbatov
2019-07-26 9:22 ` Vladimir Davydov
2019-07-26 9:55 ` Konstantin Osipov
2019-07-25 18:39 ` [PATCH v5 2/3] box: introduce tuple_chunk infrastructure Kirill Shcherbatov
2019-07-26 9:35 ` Vladimir Davydov
2019-07-25 18:39 ` [PATCH v5 3/3] box: introduce func_index Kirill Shcherbatov
2019-07-26 9:49 ` Vladimir Davydov
2019-07-26 9:57 ` Konstantin Osipov
2019-07-26 10:10 ` Vladimir Davydov
2019-07-26 19:31 ` Konstantin Osipov [this message]
2019-07-27 11:42 ` [tarantool-patches] " Vladimir Davydov
2019-07-28 21:30 ` Konstantin Osipov
2019-07-26 9:43 [PATCH v5 0/3] box: functional indexes Kirill Shcherbatov
2019-07-26 9:43 ` [PATCH v5 3/3] box: introduce func_index Kirill Shcherbatov
2019-07-26 12:15 ` Vladimir Davydov
2019-07-26 13:58 ` [tarantool-patches] " Kirill Shcherbatov
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=20190726193130.GC14622@atlas \
--to=kostja@tarantool.org \
--cc=kshcherbatov@tarantool.org \
--cc=tarantool-patches@freelists.org \
--cc=v.shpilevoy@tarantool.org \
--subject='[tarantool-patches] Re: [PATCH v5 3/3] box: introduce func_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