Re: [VOTE] Release Apache Ignite 3.0.0-alpha5 RC1
+1 On Thu, Jun 9, 2022 at 9:17 AM Alexander Polovtcev wrote: > Looks good, so many great features! +1 > > On Thu, Jun 9, 2022 at 6:42 PM Andrey Gura wrote: > > > Dear Community, > > > > In the last few month the following major features have been added: > > > > - Pluggable storages: ability to choose a specific storage for a > > table (RocksDB 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 > improved > > 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 for executing SQL > > queries on a cluster. > > > > This is an important and interesting milestone and we should share the > > current state > > with the broader community. I propose to release 3.0.0 Alpha5 with the > > features listed above. > > > > Please vote. > > > > --- > > > > Release candidate: > > https://dist.apache.org/repos/dist/dev/ignite/3.0.0-alpha5-rc1/ > > Maven staging: > > https://repository.apache.org/content/repositories/orgapacheignite-1551/ > > Git tag: https://github.com/apache/ignite-3/tree/3.0.0-alpha5-rc1 > > > > +1 - accept Apache Ignite 3.0.0-alpha5 RC1 > > 0 - don't care either way > > -1 - DO NOT accept Apache Ignite 3.0.0-alpha5 RC1 (explain why) > > > > Voting guidelines: https://www.apache.org/foundation/voting.html > > How to verify the release: https://www.apache.org/info/verification.html > > > > The vote will be open for 96 hours and will close on June 13th at 6:45pm > > https://www.timeanddate.com/countdown/to?iso=20220613T1845=352 > > > > > -- > With regards, > Aleksandr Polovtcev >
Re: [VOTE] Release Apache Ignite 3.0.0-alpha5 RC1
Looks good, so many great features! +1 On Thu, Jun 9, 2022 at 6:42 PM Andrey Gura wrote: > Dear Community, > > In the last few month the following major features have been added: > > - Pluggable storages: ability to choose a specific storage for a > table (RocksDB 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 improved > 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 for executing SQL > queries on a cluster. > > This is an important and interesting milestone and we should share the > current state > with the broader community. I propose to release 3.0.0 Alpha5 with the > features listed above. > > Please vote. > > --- > > Release candidate: > https://dist.apache.org/repos/dist/dev/ignite/3.0.0-alpha5-rc1/ > Maven staging: > https://repository.apache.org/content/repositories/orgapacheignite-1551/ > Git tag: https://github.com/apache/ignite-3/tree/3.0.0-alpha5-rc1 > > +1 - accept Apache Ignite 3.0.0-alpha5 RC1 > 0 - don't care either way > -1 - DO NOT accept Apache Ignite 3.0.0-alpha5 RC1 (explain why) > > Voting guidelines: https://www.apache.org/foundation/voting.html > How to verify the release: https://www.apache.org/info/verification.html > > The vote will be open for 96 hours and will close on June 13th at 6:45pm > https://www.timeanddate.com/countdown/to?iso=20220613T1845=352 > -- With regards, Aleksandr Polovtcev
Re:[VOTE] Release Apache Ignite 3.0.0-alpha5 RC1
+1
Re: [VOTE] Release Apache Ignite 3.0.0-alpha5 RC1
+1 On 9 Jun 2022, 19:42 +0400, Andrey Gura , wrote: > Dear Community, > > In the last few month the following major features have been added: > > - Pluggable storages: ability to choose a specific storage for a > table (RocksDB 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 improved 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 for executing SQL > queries on a cluster. > > This is an important and interesting milestone and we should share the > current state > with the broader community. I propose to release 3.0.0 Alpha5 with the > features listed above. > > Please vote. > > --- > > Release candidate: > https://dist.apache.org/repos/dist/dev/ignite/3.0.0-alpha5-rc1/ > Maven staging: > https://repository.apache.org/content/repositories/orgapacheignite-1551/ > Git tag: https://github.com/apache/ignite-3/tree/3.0.0-alpha5-rc1 > > +1 - accept Apache Ignite 3.0.0-alpha5 RC1 > 0 - don't care either way > -1 - DO NOT accept Apache Ignite 3.0.0-alpha5 RC1 (explain why) > > Voting guidelines: https://www.apache.org/foundation/voting.html > How to verify the release: https://www.apache.org/info/verification.html > > The vote will be open for 96 hours and will close on June 13th at 6:45pm > https://www.timeanddate.com/countdown/to?iso=20220613T1845=352
[VOTE] Release Apache Ignite 3.0.0-alpha5 RC1
Dear Community, In the last few month the following major features have been added: - Pluggable storages: ability to choose a specific storage for a table (RocksDB 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 improved 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 for executing SQL queries on a cluster. This is an important and interesting milestone and we should share the current state with the broader community. I propose to release 3.0.0 Alpha5 with the features listed above. Please vote. --- Release candidate: https://dist.apache.org/repos/dist/dev/ignite/3.0.0-alpha5-rc1/ Maven staging: https://repository.apache.org/content/repositories/orgapacheignite-1551/ Git tag: https://github.com/apache/ignite-3/tree/3.0.0-alpha5-rc1 +1 - accept Apache Ignite 3.0.0-alpha5 RC1 0 - don't care either way -1 - DO NOT accept Apache Ignite 3.0.0-alpha5 RC1 (explain why) Voting guidelines: https://www.apache.org/foundation/voting.html How to verify the release: https://www.apache.org/info/verification.html The vote will be open for 96 hours and will close on June 13th at 6:45pm https://www.timeanddate.com/countdown/to?iso=20220613T1845=352
Re: [ANNOUNCE] Apache Ignite 3.0.0 alpha 5: Code freeze
Thanks a lot to all! We are ready to vote. On Thu, Jun 9, 2022 at 2:28 PM Andrey Gura wrote: > > Targeted to the release. > > Thanks, Alexander. > > On Thu, Jun 9, 2022 at 2:09 PM Alexander Polovtcev > wrote: > > > > Hello again, there's another issue that blocks building the release branch: > > https://issues.apache.org/jira/browse/IGNITE-17144. Fix will be provided > > shortly > > > > On Mon, Jun 6, 2022 at 5:56 PM Andrey Gura wrote: > > > > > Igniters, > > > > > > our release schedule has shifted a bit. But it is time for a code > > > freeze and a new branch creation. > > > > > > The following issues is still in progress (not an issues status, but > > > work state): > > > > > > Data rebalancing > > > https://issues.apache.org/jira/browse/IGNITE-14209 > > > > > > CLI MVP > > > https://issues.apache.org/jira/browse/IGNITE-16971 > > > > > > [Native Persistence 3.0] End-to-end test for persistent PageMemory > > > https://issues.apache.org/jira/browse/IGNITE-17107 > > > > > > SQL API: Implement query metadata > > > https://issues.apache.org/jira/browse/IGNITE-16962 > > > > > > SQL API: Add batched DML queries support. > > > https://issues.apache.org/jira/browse/IGNITE-16963 > > > > > > SQL API: Examples. > > > https://issues.apache.org/jira/browse/IGNITE-17088 > > > > > > Please, give some planned timelines for these issues. I would like to > > > create the ignite-3.0.0-alpha5 branch today and announce Code Freeze. > > > Otherwise, extra steps will be required to include the PR's to the > > > release branch. > > > > > > Thanks! > > > > > > > > > -- > > With regards, > > Aleksandr Polovtcev
Re: [ANNOUNCE] Apache Ignite 3.0.0 alpha 5: Code freeze
Targeted to the release. Thanks, Alexander. On Thu, Jun 9, 2022 at 2:09 PM Alexander Polovtcev wrote: > > Hello again, there's another issue that blocks building the release branch: > https://issues.apache.org/jira/browse/IGNITE-17144. Fix will be provided > shortly > > On Mon, Jun 6, 2022 at 5:56 PM Andrey Gura wrote: > > > Igniters, > > > > our release schedule has shifted a bit. But it is time for a code > > freeze and a new branch creation. > > > > The following issues is still in progress (not an issues status, but > > work state): > > > > Data rebalancing > > https://issues.apache.org/jira/browse/IGNITE-14209 > > > > CLI MVP > > https://issues.apache.org/jira/browse/IGNITE-16971 > > > > [Native Persistence 3.0] End-to-end test for persistent PageMemory > > https://issues.apache.org/jira/browse/IGNITE-17107 > > > > SQL API: Implement query metadata > > https://issues.apache.org/jira/browse/IGNITE-16962 > > > > SQL API: Add batched DML queries support. > > https://issues.apache.org/jira/browse/IGNITE-16963 > > > > SQL API: Examples. > > https://issues.apache.org/jira/browse/IGNITE-17088 > > > > Please, give some planned timelines for these issues. I would like to > > create the ignite-3.0.0-alpha5 branch today and announce Code Freeze. > > Otherwise, extra steps will be required to include the PR's to the > > release branch. > > > > Thanks! > > > > > -- > With regards, > Aleksandr Polovtcev
Re: [ANNOUNCE] Apache Ignite 3.0.0 alpha 5: Code freeze
Hello again, there's another issue that blocks building the release branch: https://issues.apache.org/jira/browse/IGNITE-17144. Fix will be provided shortly On Mon, Jun 6, 2022 at 5:56 PM Andrey Gura wrote: > Igniters, > > our release schedule has shifted a bit. But it is time for a code > freeze and a new branch creation. > > The following issues is still in progress (not an issues status, but > work state): > > Data rebalancing > https://issues.apache.org/jira/browse/IGNITE-14209 > > CLI MVP > https://issues.apache.org/jira/browse/IGNITE-16971 > > [Native Persistence 3.0] End-to-end test for persistent PageMemory > https://issues.apache.org/jira/browse/IGNITE-17107 > > SQL API: Implement query metadata > https://issues.apache.org/jira/browse/IGNITE-16962 > > SQL API: Add batched DML queries support. > https://issues.apache.org/jira/browse/IGNITE-16963 > > SQL API: Examples. > https://issues.apache.org/jira/browse/IGNITE-17088 > > Please, give some planned timelines for these issues. I would like to > create the ignite-3.0.0-alpha5 branch today and announce Code Freeze. > Otherwise, extra steps will be required to include the PR's to the > release branch. > > Thanks! > -- With regards, Aleksandr Polovtcev
