Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
MIME-Version: 1.0
From: =?UTF-8?B?0JTQvNC40YLRgNC40Lkg0KDRj9Cx0L7Qsg==?= <somefireone@gmail.com>
Date: Fri, 31 Mar 2017 16:34:49 +0300
Message-ID: <CAKdXNOXh2P4KXjP0GFBCKDn4wNuHF8U_X010ecc5OzxBbVoHRA@mail.gmail.com>
Subject: IGNITE-4188, thoughts about realisation
To: dev@ignite.apache.org
Content-Type: multipart/alternative; boundary=001a114b3730e726ac054c06e00e
archived-at: Fri, 31 Mar 2017 13:35:15 -0000

--001a114b3730e726ac054c06e00e
Content-Type: text/plain; charset=UTF-8

Hello, community.

try (Transaction tx = ignite.transactions().txStart()) {
    c.put(1, 1);

    tx.savepoint("mysavepoint");

    c.put(2, 2);

    tx.rollbackToSavepoint("mysavepoint");

    c.put(3, 3);

    tx.commit();
}


I want to make it in such way:

When user calls tx.savepoint(""), Transaction delegate call to
IgniteInternalTx, which delegate it to its IgniteTxState.

IgniteTxState implementation will contain stack of savepoints, where
Savepoint is class containing snapshot of cache entries and any important
additional information.

What do you think?

--001a114b3730e726ac054c06e00e--