From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lf1-f67.google.com (mail-lf1-f67.google.com [209.85.167.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by dev.tarantool.org (Postfix) with ESMTPS id 19AC8469710 for ; Mon, 25 May 2020 21:35:57 +0300 (MSK) Received: by mail-lf1-f67.google.com with SMTP id 82so10978011lfh.2 for ; Mon, 25 May 2020 11:35:56 -0700 (PDT) Date: Mon, 25 May 2020 21:35:54 +0300 From: Cyrill Gorcunov Message-ID: <20200525183554.GF2464@grain> References: <20200525163409.GC4272@atlas> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200525163409.GC4272@atlas> Subject: Re: [Tarantool-patches] [PATCH v2 2/2] wal: reorder tx rows so that a tx ends on a global row List-Id: Tarantool development patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Konstantin Osipov Cc: tarantool-patches@dev.tarantool.org, v.shpilevoy@tarantool.org On Mon, May 25, 2020 at 07:34:09PM +0300, Konstantin Osipov wrote: > * Serge Petrenko [20/05/25 14:00]: > > While I think it's an acceptable strategy for a bugfix, I still > think relaying has to be fixed to be transactional, the current > xstream api is a huge legacy we're stuck with since Tarantool 1.3! > > It saddens me a great deal the relay patch may be shuffled into > the desk once the problem is not as urgent. Kostya, could you please describe xstream api here, so I would file a bug and will assign it to myself/someone and we won't forget. (yes, I remember you've said me about rework in f2f conversation but i might be missing some details so please write it here, in email)