In my view, there are two different scenarios. First - user just upgrades the version (to get some bug fix, for example), but does not intend to change anything in their project and/or use any new features. In this case it should work transparently and cluster must be able to work with older format. Ideally, we should detect this automatically, but if it's not possible we can introduce some kind of 'compatibility mode' enabled by a system property.
Second - user upgrades to get new features that require data format change. In this case, I think it's OK to suggest using a conversion tool. Or probably we can apply it automatically on node startup? -Val On Tue, Sep 19, 2017 at 6:38 AM, Yakov Zhdanov <[email protected]> wrote: > >Any major change in data/index page format. E.g. this could happen once > transactional SQL is ready. > > I would suggest we automatically disable this feature for databases created > with older versions. > > --Yakov >
