From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp48.i.mail.ru (smtp48.i.mail.ru [94.100.177.108]) (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 93E0346970E for ; Thu, 19 Dec 2019 11:34:51 +0300 (MSK) Date: Thu, 19 Dec 2019 11:34:51 +0300 From: Kirill Yukhin Message-ID: <20191219083451.7rzz2mb2h2a2jjo5@tarantool.org> References: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Subject: Re: [Tarantool-patches] [PATCH 1/1] tuple: enable isolated JSON updates List-Id: Tarantool development patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Vladislav Shpilevoy Cc: tarantool-patches@dev.tarantool.org Hello, On 22 ноя 00:19, Vladislav Shpilevoy wrote: > Isolated tuple update is an update by JSON path, which hasn't a > common prefix with any other JSON update operation in the same > set. For example, these JSON update operations are isolated: > > {'=', '[1][2][3]', 100}, > {'+', '[2].b.c', 200} > > Their JSON paths has no a common prefix. But these operations are > not isolated: > > {'=', '[1][2][3]', 100}, > {'+', '[1].b.c', 200} > > They have a common prefix '[1]'. > > Isolated updates are a first part of fully functional JSON > updates. Their feature is that their implementation is relatively > simple and lightweight - an isolated JSON update does not store > each part of the JSON path as a separate object. Isolated update > stores just string with JSON and pointer to the MessagePack > object to update. > > Such isolated updates are called 'bar update'. They are a basic > brick of more complex JSON updates. > > Part of #1261 > --- > Branch: https://github.com/tarantool/tarantool/tree/gerold103/gh-1261-json-bar-update > Issue: https://github.com/tarantool/tarantool/issues/1261 The patch LGTM. I've checked it into master. -- Regards, Kirill Yukhin