From: Vladimir Davydov <vdavydov.dev@gmail.com>
To: Kirill Shcherbatov <kshcherbatov@tarantool.org>
Cc: tarantool-patches@freelists.org, kostja@tarantool.org
Subject: Re: [PATCH v1 0/4] box: JSON preparatory patchset
Date: Thu, 27 Dec 2018 22:13:32 +0300 [thread overview]
Message-ID: <20181227191332.ruxcmeoh67olgcqt@esperanza> (raw)
In-Reply-To: <cover.1545909236.git.kshcherbatov@tarantool.org>
v1? I thought it at least v2
On Thu, Dec 27, 2018 at 02:15:51PM +0300, Kirill Shcherbatov wrote:
> Preparatory patch set for JSON indexes:
> - Implemented a new json_token_path_snprint routine able to print
> JSON path to field by field specified working like cannonical
> snprintf routine
> - New json_token_is_leaf helper to test node is JSON tree leaf
> - Implemented a new bitmap_majority_test routine to check if the
> passed bitmap a "majorates" bitmap b (test that a contains at
> least all b bits).
> - Reworked tuple_init_field_map with required fields bitmap -
> a scallable approach able to work with JSON multilevel fields
> tree.
>
> http://github.com/tarantool/tarantool/tree/kshch/gh-3908-fix-ast-alter-memleak
Bad link.
> https://github.com/tarantool/tarantool/issues/3908
>
> Kirill Shcherbatov (4):
> lib: introduce json_tree_snprint_path
> lib: introduce json_token_is_leaf helper
> box: introduce bitmap_majority_test routine
> box: refactor tuple_init_field_map to use bitmap
>
> src/box/errcode.h | 2 +-
> src/box/tuple_format.c | 103 ++++++++++++++++++++++++++--
> src/box/tuple_format.h | 18 +++++
> src/lib/bit/bit.h | 45 ++++++++++++
> src/lib/json/json.c | 68 ++++++++++++++++++
> src/lib/json/json.h | 21 ++++++
> test/box/alter_limits.result | 6 +-
> test/box/ddl.result | 18 ++---
> test/box/misc.result | 2 +-
> test/box/sql.result | 9 +--
> test/box/tree_pk_multipart.result | 6 +-
> test/engine/ddl.result | 21 ++----
> test/engine/null.result | 39 ++++-------
> test/unit/bit.c | 52 ++++++++++++++
> test/unit/bit.result | 2 +
> test/unit/json.c | 110 +++++++++++++++++++++++++++++-
> test/unit/json.result | 32 ++++++++-
> test/vinyl/constraint.result | 9 +--
> test/vinyl/errinj.result | 9 +--
> test/vinyl/savepoint.result | 6 +-
> 20 files changed, 485 insertions(+), 93 deletions(-)
prev parent reply other threads:[~2018-12-27 19:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-27 11:15 Kirill Shcherbatov
2018-12-27 11:15 ` [PATCH v1 1/4] lib: introduce json_tree_snprint_path Kirill Shcherbatov
2018-12-27 18:51 ` Vladimir Davydov
2018-12-27 11:15 ` [PATCH v1 2/4] lib: introduce json_token_is_leaf helper Kirill Shcherbatov
2018-12-27 18:52 ` Vladimir Davydov
2018-12-27 11:15 ` [PATCH v1 3/4] box: introduce bitmap_majority_test routine Kirill Shcherbatov
2018-12-27 18:59 ` Vladimir Davydov
2018-12-29 12:58 ` [tarantool-patches] " Kirill Shcherbatov
2018-12-29 13:19 ` Vladimir Davydov
2018-12-29 13:57 ` Kirill Shcherbatov
2018-12-29 16:16 ` Vladimir Davydov
2018-12-27 11:15 ` [PATCH v1 4/4] box: refactor tuple_init_field_map to use bitmap Kirill Shcherbatov
2018-12-27 11:48 ` [tarantool-patches] " Konstantin Osipov
2018-12-27 19:12 ` Vladimir Davydov
2018-12-29 12:58 ` [tarantool-patches] " Kirill Shcherbatov
2018-12-29 13:22 ` Vladimir Davydov
2018-12-29 16:25 ` Vladimir Davydov
2018-12-27 19:13 ` Vladimir Davydov [this message]
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=20181227191332.ruxcmeoh67olgcqt@esperanza \
--to=vdavydov.dev@gmail.com \
--cc=kostja@tarantool.org \
--cc=kshcherbatov@tarantool.org \
--cc=tarantool-patches@freelists.org \
--subject='Re: [PATCH v1 0/4] box: JSON preparatory patchset' \
/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