Tarantool development patches archive
 help / color / mirror / Atom feed
From: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
To: tarantool-patches@freelists.org
Cc: vdavydov.dev@gmail.com, kshcherbatov@tarantool.org
Subject: [PATCH v3 0/3] Implement json path access to tuple fields
Date: Tue, 10 Apr 2018 11:31:43 +0300	[thread overview]
Message-ID: <cover.1523349020.git.v.shpilevoy@tarantool.org> (raw)

Branch: http://github.com/tarantool/tarantool/tree/gh-1285-tuple-field-by-json-icu
Issue: https://github.com/tarantool/tarantool/issues/1285

Tuple field access by JSON path provides fast access to a field and field
internals with no unpacking an entire tuple or even the field into Lua.

This patchset is a first part of JSON introduction into Tarantool core. It
introduces the JSON path parser and tuple internals access by JSON. The next
patchsets will introduce tuple update by JSON - gh-1261, indexing by
JSON - gh-1012.

Kirill Shcherbatov (2):
  Introduce json_path_parser with Unicode support.
  Lua: implement json path access to tuple fields

Vladislav Shpilevoy (1):
  Allow gcov on Mac

 cmake/profile.cmake         |   9 --
 src/box/CMakeLists.txt      |   2 +-
 src/box/lua/tuple.c         |  63 ++++++++----
 src/box/lua/tuple.lua       |  49 +++------
 src/box/tuple.h             |  21 ++++
 src/box/tuple_format.c      | 164 +++++++++++++++++++++++++++++
 src/box/tuple_format.h      |  19 ++++
 src/lib/CMakeLists.txt      |   1 +
 src/lib/json/CMakeLists.txt |   6 ++
 src/lib/json/path.c         | 245 ++++++++++++++++++++++++++++++++++++++++++++
 src/lib/json/path.h         | 112 ++++++++++++++++++++
 test/engine/tuple.result    | 229 +++++++++++++++++++++++++++++++++++++++++
 test/engine/tuple.test.lua  |  67 ++++++++++++
 test/unit/CMakeLists.txt    |   3 +
 test/unit/json_path.c       | 172 +++++++++++++++++++++++++++++++
 test/unit/json_path.result  |  98 ++++++++++++++++++
 16 files changed, 1195 insertions(+), 65 deletions(-)
 create mode 100644 src/lib/json/CMakeLists.txt
 create mode 100644 src/lib/json/path.c
 create mode 100644 src/lib/json/path.h
 create mode 100644 test/unit/json_path.c
 create mode 100644 test/unit/json_path.result

-- 
2.14.3 (Apple Git-98)

             reply	other threads:[~2018-04-10  8:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-10  8:31 Vladislav Shpilevoy [this message]
2018-04-10  8:31 ` [PATCH v3 1/3] Allow gcov on Mac Vladislav Shpilevoy
2018-04-10 10:49   ` Vladimir Davydov
     [not found] ` <f1302082b4457a03b5d2b3c44526815428de4a0e.1523349020.git.v.shpilevoy@tarantool.org>
2018-04-10 16:36   ` [PATCH v3 2/3] Introduce json_path_parser with Unicode support Vladimir Davydov
2018-04-10 18:42     ` [tarantool-patches] " Vladislav Shpilevoy
2018-04-11  9:20       ` Vladimir Davydov
     [not found] ` <c3b64b7b4e638970864995c895bbd5f736282560.1523349020.git.v.shpilevoy@tarantool.org>
2018-04-13 11:33   ` [PATCH v3 3/3] Lua: implement json path access to tuple fields Vladimir Davydov
2018-04-13 21:51     ` [tarantool-patches] " Vladislav Shpilevoy
2018-04-16  8:35       ` Vladimir Davydov
2018-04-16 10:02         ` Vladislav Shpilevoy
2018-04-22 14:21         ` Vladislav Shpilevoy

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=cover.1523349020.git.v.shpilevoy@tarantool.org \
    --to=v.shpilevoy@tarantool.org \
    --cc=kshcherbatov@tarantool.org \
    --cc=tarantool-patches@freelists.org \
    --cc=vdavydov.dev@gmail.com \
    --subject='Re: [PATCH v3 0/3] Implement json path access to tuple fields' \
    /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