From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtpng1.m.smailru.net (smtpng1.m.smailru.net [94.100.181.251]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dev.tarantool.org (Postfix) with ESMTPS id 7EBBC469719 for ; Thu, 12 Nov 2020 00:55:07 +0300 (MSK) References: <2161b3318413560c0145f011a62c395b5e4fffad.1604425009.git.korablev@tarantool.org> From: Vladislav Shpilevoy Message-ID: <597d916f-21ce-d6f8-6a1a-4e6d62ae7a70@tarantool.org> Date: Wed, 11 Nov 2020 22:55:05 +0100 MIME-Version: 1.0 In-Reply-To: <2161b3318413560c0145f011a62c395b5e4fffad.1604425009.git.korablev@tarantool.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [Tarantool-patches] [PATCH] vinyl: update gh-4957-too-many-upserts test List-Id: Tarantool development patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Nikita Pettik , tarantool-patches@dev.tarantool.org Hi! Thanks for the patch! On 03.11.2020 18:37, Nikita Pettik wrote: > After upsert rework in 5a61c4717 (#5107 issue) update operations are > applied consistently corresponding to upserts they belong to: if update > operation from single upsert fails - all update operations from that > upsert are skipped. But the rest of update operations related to other > upserts (after squashing two upserts) are applied. So let's update #4957 > test case: now upsert operation can be processed only if it contains > more than BOX_UPDATE_OP_CNT_MAX (4000) operations before (before 'not more' instead of 'more'? Otherwise I don't understand.