From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Fri, 26 Jul 2019 12:57:43 +0300 From: Konstantin Osipov Subject: Re: [PATCH v5 3/3] box: introduce func_index Message-ID: <20190726095743.GG9916@atlas> References: <25789ea46e8fcec527bd7864209bb6ea2113dca5.1564079799.git.kshcherbatov@tarantool.org> <20190726094958.GA4080@esperanza> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190726094958.GA4080@esperanza> To: Vladimir Davydov Cc: Kirill Shcherbatov , tarantool-patches@freelists.org, v.shpilevoy@tarantool.org List-ID: * Vladimir Davydov [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. Let's work on a follow up patch right away. > > I assume that it's not important, because the corresponding ticket > (#4348) is scheduled for 2.3 so we will probably figure something out > until then (may be, implement support of yielding statements in DDL). -- Konstantin Osipov, Moscow, Russia