THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Page History
...
| ID | IEP-69 |
| Author | |
| Sponsor | |
| Created |
|
| Status | DRAFT |
| Table of Contents |
|---|
Motivation
It is hard to believe that modern distributed databases can live for years without having releases with breaking backwards compatibility changes as the Apache Ignite does. The lot of @deprecated methods in the API and many obsolete documentation pages leads to a bad user experience. Moreover, the same problem exists for maintaining the obsolete source code for developers and blocks using modern technologies and the latest development language features.
...
- set Spring 5 as the default
- set compact footer = true for thin client
Risks and Assumptions
There are some public activities with the 3.0 Ignite version that already happened e.g. the 3.0-alpha version creation, some public online meetups. Thus, the main risk associated with the release of the new 3.0 version is mainly related to marketing activities. However, the amount of changes for the new Ignite architecture is too big to be completed within the next few years. The stabilization period of such a version may take even more time.
...
Reference Links
[1] Apache Ignite 3.0 Wishlist
[2] Apache Ignite 3.0.0-alpha1// Links to various reference documents, if applicable.
Tickets
// Links or report with relevant JIRA tickets.
Overview
Content Tools
Apps