Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
MIME-Version: 1.0
References: <CAGt6o8=YtqTC7nYdK-Vvsc3Qkf4Tc3XjP9W63aSLu1=QdhEZQA@mail.gmail.com>
 <a183cd66-eaa5-b30d-187d-85e948556ebc@gmail.com> <CAGcMBHjj2=JucXNgNAP5161skfPk4M9XhqeuQqUpyyQdbzUv-w@mail.gmail.com>
 <CAFyTW-g6Pw3QyYg6Ysu_VQPLifKytD8ci+aiGFXC9p4tZ7VPBw@mail.gmail.com>
In-Reply-To: <CAFyTW-g6Pw3QyYg6Ysu_VQPLifKytD8ci+aiGFXC9p4tZ7VPBw@mail.gmail.com>
From: Dmitry Pavlov <dpavlov.spb@gmail.com>
Date: Tue, 19 Sep 2017 12:52:15 +0000
Message-ID: <CALUCNEvwHuZLu_-RrwMgiCtVWjiMeXqyft0qJnM4JxfeLG16ig@mail.gmail.com>
Subject: Re: Binary compatibility of persistent storage
To: dev@ignite.apache.org
Content-Type: multipart/alternative; boundary="089e0825f3ecc548bd05598a542d"
archived-at: Tue, 19 Sep 2017 12:52:31 -0000

--089e0825f3ecc548bd05598a542d
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

I have same idea about testing of WAL compatibilty between releases. It
will be actual since 2.3 release (as 2.2 was emergency release without
impact changes).

I look forward to IGNITE-5732 completion and merge. And then I able to
start writting first test.

I think it is quite unexpected for user if Ignite is not able to start from
existing database after updating to next release. That is why I vote for
backward compatibilty with automatic transparent migration (if needed).

=D0=B2=D1=82, 19 =D1=81=D0=B5=D0=BD=D1=82. 2017 =D0=B3. =D0=B2 15:16, Vyach=
eslav Daradur <daradurvs@gmail.com>:

> I vote for: =E2=80=9C4) Maintain compatibility between all versions withi=
n major
> release=E2=80=9D.
> I think this is a trade-off between the complexity of implementing new
> features and UX.
>
> We will be able to get rid of all legacy tools every major release.
>
> I=E2=80=99m working on a testing framework, which helps us testing compat=
ibility
> features between different Ignite version.
> Testing in the early stages will help us to consider the impact of change=
s
> in other releases and to be closer to the end user.
>
> Here is a dummy unit-test example:
>
> void testNodeStartByOldVersionPersistenceData() throws Exception {
>     try {
>         startGrid(1, "2.1.0", new PostConfigurationClosure(), new
> PostActionClosure());
>
>         stopAllGrids(); // Stopping 2.1.0
>
>         IgniteEx ignite =3D startGrid(0); // Starting current version
>
>         ignite.active(true);
>
>         IgniteCache<Integer, String> cache =3D
> ignite.getOrCreateCache(TEST_CACHE_NAME);
>
>         for (int i =3D 0; i < 10; i++)
>             assertEquals("data" + i, cache.get(i));
>     }
>     finally {
>         stopAllGrids();
>     }
> }
>
> class PostActionClosure implements IgniteInClosure<Ignite> {
>     @Override public void apply(Ignite ignite) {
>         ignite.active(true);
>
>         CacheConfiguration<Integer, String> cacheCfg =3D new
> CacheConfiguration<>();
>
>         IgniteCache<Integer, String> cache =3D ignite.createCache(cacheCf=
g);
>
>         for (int i =3D 0; i < 10; i++)
>             cache.put(i, "data" + i);
>     }
> }
>
> class PostConfigurationClosure implements
> IgniteInClosure<IgniteConfiguration> {
>     @Override public void apply(IgniteConfiguration cfg) {
>         // Post configuration actions
>         cfg.setPersistentStoreConfiguration(new
> PersistentStoreConfiguration());
>     }
> }
>
> [1] https://issues.apache.org/jira/browse/IGNITE-5732 - Provide API to
> test
> compatibility with old releases
>
> On Tue, Sep 19, 2017 at 2:51 PM, Yakov Zhdanov <yzhdanov@apache.org>
> wrote:
>
> > Vladimir,
> >
> > Can you please describe the situation when 2 is possible, but 4 is not?
> >
> > --Yakov
> >
>
>
>
> --
> Best Regards, Vyacheslav D.
>

--089e0825f3ecc548bd05598a542d--