Tarantool development patches archive
 help / color / mirror / Atom feed
From: Vladimir Davydov <vdavydov.dev@gmail.com>
To: kostja@tarantool.org
Cc: tarantool-patches@freelists.org
Subject: [PATCH v2 0/3] Transactional DDL
Date: Wed, 10 Jul 2019 16:09:26 +0300	[thread overview]
Message-ID: <cover.1562763283.git.vdavydov.dev@gmail.com> (raw)

This patch set implements transactional DDL for the case when all
statements are non-yielding. There are only two DDL statements that
may yield implicitly - building of a new index and checking a space
format - so it must cover most user stories. For more details re
the implementation, see comments to the individual patches.

https://github.com/tarantool/tarantool/issues/4083
https://github.com/tarantool/tarantool/commits/dv/gh-4083-transactional-ddl

v1: https://www.freelists.org/post/tarantool-patches/PATCH-05-Transactional-DDL

Changes in v2:
 - Committed approved patches and rebased.
 - Fixed wrong index usage in AlterSpaceOp::commit,rollback
 - Reworked error reporting.
 - Reworked txn_on_yield management.

Vladimir Davydov (3):
  memtx: fix txn_on_yield for DDL transactions
  ddl: don't use space_index from AlterSpaceOp::commit,rollback
  ddl: allow to execute non-yielding DDL statements in transactions

 src/box/alter.cc              | 91 ++++++++++++++--------------------------
 src/box/errcode.h             |  2 +-
 src/box/memtx_engine.c        | 96 ++----------------------------------------
 src/box/memtx_space.c         | 10 +++++
 src/box/txn.c                 | 89 ++++++++++++++++++++++++++++++++++++---
 src/box/txn.h                 | 63 +++++++++++++++-------------
 src/box/user.cc               |  1 -
 src/box/vinyl.c               | 25 ++++++++---
 test/box/misc.result          |  1 +
 test/box/on_replace.result    | 53 +++++++++++------------
 test/box/on_replace.test.lua  | 13 +++---
 test/box/transaction.result   | 98 +++++++++++++++++++++++++++++++++----------
 test/box/transaction.test.lua | 64 +++++++++++++++++++++++-----
 test/engine/ddl.result        | 58 ++++++++++++++++++++++++-
 test/engine/ddl.test.lua      | 39 ++++++++++++++++-
 test/engine/truncate.result   | 10 +----
 test/engine/truncate.test.lua |  6 +--
 17 files changed, 440 insertions(+), 279 deletions(-)

-- 
2.11.0

             reply	other threads:[~2019-07-10 13:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-10 13:09 Vladimir Davydov [this message]
2019-07-10 13:09 ` [PATCH v2 1/3] memtx: fix txn_on_yield for DDL transactions Vladimir Davydov
2019-07-10 20:34   ` Konstantin Osipov
2019-07-12 14:54     ` Vladimir Davydov
2019-07-12 15:16       ` Konstantin Osipov
2019-07-10 13:09 ` [PATCH v2 2/3] ddl: don't use space_index from AlterSpaceOp::commit,rollback Vladimir Davydov
2019-07-15 15:05   ` Konstantin Osipov
2019-07-10 13:09 ` [PATCH v2 3/3] ddl: allow to execute non-yielding DDL statements in transactions Vladimir Davydov
2019-07-10 20:43   ` Konstantin Osipov
2019-07-12 14:55     ` Vladimir Davydov
2019-07-10 21:07   ` Konstantin Osipov
2019-07-15 15:03   ` Konstantin Osipov
2019-07-15 16:23 ` [PATCH v2 0/3] Transactional DDL Vladimir Davydov

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.1562763283.git.vdavydov.dev@gmail.com \
    --to=vdavydov.dev@gmail.com \
    --cc=kostja@tarantool.org \
    --cc=tarantool-patches@freelists.org \
    --subject='Re: [PATCH v2 0/3] Transactional DDL' \
    /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