Hi Igniters, Four months have passed already since the Ignite 3 alpha 4 release. At the moment we have a set of features that can be released in order to give to a user an ability to try the features and share some feedback with the community. The expected feature list consists of:
- Pluggable storages: ability to choose a specific storage for a table (LSM based storage, Page memory persistent and in-memory storage) with some known limitations. - Compute API (A simple remote job execution): The first phase of Compute API design and implementation. Of course, with known limitations. - Data colocation: The colocation key concept replaces the affinity key concept. DDL introduces COLOCATE BY clause. Colocated job execution. - Open API for the Ignite REST endpoints: A Specification to generate a client for any language + auto-generated docs for REST API. - Ignite REPL: The Ignite CLI as a REPL with autocompletion and improves UX. - Cluster lifecycle: It introduces cluster initialization logic and allows to specify cluster management and meta storage groups. Improved node join protocol. - Local and distributed recovery: Now it is possible to restart a cluster/node without data loss. - Data rebalance improvements (in progress and could be excluded from the release), including dynamically changing the number of partition replicas. - Robust client connection with seamless reconnection support and retry policies. - Java API for SQL: A simplified API (design only) for executing SQL queries on a cluster. I want to propose myself to be the release manager of the Ignite 3 alpha 5. Also I propose the following milestones for the release: Scope Freeze: June 1, 2022 Code Freeze: June 3, 2022 Voting Date: June 6, 2022 Release Date: June 10, 2012 Please, take into account that the proposed release is still alpha, so we can afford to have such a compressed schedule. WDYT?
