[ANNOUNCE] Apache Ignite 3.0.0-alpha3 is released!
Igniters, I'm happy to announce that the third alpha version of Ignite 3 is out! On top of the functionality that was previously released, Alpha 3 adds the following major features: - New SQL engine based on Apache Calcite with implemented JDBC driver. - Persistence implementation based on RocksDB. - New binary client protocol with an implementation in Java. - Data rebalancing. Code examples have been added for the new features, you can check them out here: https://github.com/apache/ignite-3/tree/3.0.0-alpha3/examples The best way to try the release out is to go through the Getting Started Guide: https://ignite.apache.org/docs/3.0.0-alpha If there are any questions, issues, or thoughts, please do not hesitate to reply to this email. Ignite Community is welcoming any feedback and will consider it in future development. -Val
Re: Apache Ignite 2.12 RELEASE [Time, Scope, Manager]
Petr, thank you! чт, 21 окт. 2021 г. в 18:19, Petr Ivanov : > > Try now, please. > > > On 21 Oct 2021, at 17:47, Nikita Amelchev wrote: > > > > Hi, > > > > Petr, could you grant me TC permissions to run release builds please? > > > > ср, 20 окт. 2021 г. в 10:25, Pavel Tupitsyn : > > > >> > >> Igniters, > >> > >> I've filed a blocker - release configurations on TeamCity should be fixed > >> after recent .NET project structure refactoring: > >> https://issues.apache.org/jira/browse/IGNITE-15779 > >> > >> I'm on vacation right now with limited internet access, I'll work on this > >> ASAP next week. > >> > >> On Wed, Oct 13, 2021 at 2:33 PM Nikita Amelchev > >> wrote: > >> > >>> Igniters, > >>> > >>> Scope freeze is planned for Friday, October 15. > >>> I suggest creating the release branch on that date. > >>> > >>> The wiki page with the release info. [1] Please, check the fix version > >>> of your issues. > >>> > >>> There are no unresolved blockers. > >>> There are 3 important issues in the review state. [2] > >>> > >>> Also, please, pay attention to unresolved documentation issues. [3] > >>> > >>> [1] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.12 > >>> [2] > >>> https://issues.apache.org/jira/issues/?jql=(resolution%20%3D%20Unresolved%20AND%20project%20%3D%20%27Ignite%27%20AND%20type%20in%20(%22New%20Feature%22%2C%20Task%2C%20Sub-task%2C%20Improvement)%20AND%20fixVersion%20in%20(%272.12%27)%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20AND%20(labels%20in%20(%27important%27)%20OR%20Flags%20%3D%20Important))%20order%20by%20summary > >>> [3] > >>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.12%27)%20AND%20status%20NOT%20IN%20(Resolved%2C%20Closed)%20AND%20component%20in%20(documentation)%20ORDER%20BY%20priority%20%20%20%20%20%20%20%20%20 > >>> > >>> пт, 1 окт. 2021 г. в 19:06, Pavel Tupitsyn : > > I'm working on IGNITE-15504 and plan to finish it early next week. > > On Fri, Oct 1, 2021 at 6:08 PM Nikita Amelchev > >>> wrote: > > > Igniters, > > > > I have created the wiki page for the 2.12 release. [1] > > > > The release scope contains 1 issue that is marked as a blocker: > > IGNITE-15504 .NET: SDK 2.1 is out of support, make sure project can be > > developed with newer SDKs [2] > > > > Folks, do not forget to document features (65 issues still not > >>> resolved). > > [3] > > > > Maxim, Ivan, > > +1 to add these issues to the 2.12 scope. > > > > [1] > >>> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.12 > > [2] https://issues.apache.org/jira/browse/IGNITE-15504 > > [3] > > > >>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.12%27)%20AND%20status%20NOT%20IN%20(Resolved%2C%20Closed)%20AND%20component%20in%20(documentation)%20ORDER%20BY%20priority%20%20%20%20%20%20%20%20%20 > > > > ср, 29 сент. 2021 г. в 11:28, Ivan Daschinsky : > >> > >> Created issues related building ODBC module, running C++ suites and > >> removing VS project files > >> > >> 1. https://issues.apache.org/jira/browse/IGNITE-15637 > >> 2.https://issues.apache.org/jira/browse/IGNITE-15636 > >> > >> вс, 26 сент. 2021 г. в 19:50, Ivan Daschinsky : > >> > >>> +1 > >>> > >>> Let's consider building odbc driver using Visual C++ 2017? > >>> > >>> 2015, 2017 and 2019 share the same redistributable package and it > >>> is > > the > >>> default one in Windows 10. > >>> > >>> Also, let's remove vs project files, since the most of you all > >>> agree > > that > >>> it is redundant. > >>> > >>> If both suggestions are ok, I will create ticketa soon. > >>> > >>> вс, 26 сент. 2021 г., 17:10 Pavel Tupitsyn : > >>> > +1 > > On Fri, Sep 24, 2021 at 8:04 PM Maxim Muzafarov < > >>> mmu...@apache.org> > wrote: > > > Hello Nikita, > > > > +1 if you will lead this release. > > > > > > I'd suggest including into the release scope this one issue too: > > > > Snapshot restore must support restoring with indexes rebuild > > https://issues.apache.org/jira/browse/IGNITE-14744 > > > > Hopefully, it will be completed by the end of October. > > > > On Fri, 24 Sept 2021 at 19:48, Nikita Amelchev < > > namelc...@apache.org> > > wrote: > >> > >> Dear Ignite Community! > >> > >> I suggest starting Apache Ignite 2.12 release activities. > >> > >> For now, we've accumulated a hundred resolved issues with new > > features > >> and bug fixes which are waiting for their release date. For > >
Re: Ci and ci2 settings synchronization
Folks, you don't need me on that call. I'm of a little value/help here. - Denis On Thu, Oct 21, 2021 at 9:51 AM Nikolay Izhikov wrote: > Hello, Igniters. > > As you may know, recently, Sberbank sponsored servers capacity to setup > new instance of Team City [1] to run Ignite tests. > > Right now, ci2 is fully ready for daily usage. > We have exported and prepared Kotlin scripts [2] to keep TC settings as a > code [3]. > > I think we should adjust both TC instances to use the same settings and > run tests in the same way. > > ci.ignite.apache.org is sponsored and run by Grid Gain so > > Denis, Valentin, Petr, let's have a call to discuss how and when we can > implement these changes? > > [1] https://ci2.ignite.apache.org > [2] https://github.com/willy983/ci_tc_configuration > [3] https://www.jetbrains.com/help/teamcity/kotlin-dsl.html > > > > 3 авг. 2021 г., в 18:33, Dmitry Pavlov написал(а): > > > > Hi Igniters, > > > > I'm glad to announce that SberTech made an internal aggreement to > sponsor a computing power to provide backup TeamCity instance. This > instance is intended to be a geo-independent, secondary instance with > availablility for community members. > > > > Thanks to JetBrains for providing license keys for TeamCity as their > part of opensource sponsoring program. > > > > Most likely, we'll setup some domain name as tc.i.a.o or ci2.i.a.o. > Please share your vision what would be most obvious. > > > > After a private discussions with Vitaliy Osipov and Petr Ivanov, I do > believe that it would be possible to preserve current registered users. > Build configurations are to be the same for the secondary instance. > Technical details on how is could be achieved will be available later (most > likely we'll start a sepearate thread to dicuss that). > > > > You are more than welcome to be an early adopters. > > > > Sincerely, > > Dmitriy Pavlov > > > >
Re: Ci and ci2 settings synchronization
Hi, Nikolay. Currently, I know only how to sync build settings — we should move to Kotlin. But that is not an easy task — lots of code should be written before we can move, several repositories established and so on. Considering server instance settings like user database — tempted DB admin is required to prepare custom scripts that will replicate users info directly in database (and script maintenance will also be required due to annual DB scheme migration). > On 21 Oct 2021, at 16:51, Nikolay Izhikov wrote: > > Hello, Igniters. > > As you may know, recently, Sberbank sponsored servers capacity to setup new > instance of Team City [1] to run Ignite tests. > > Right now, ci2 is fully ready for daily usage. > We have exported and prepared Kotlin scripts [2] to keep TC settings as a > code [3]. > > I think we should adjust both TC instances to use the same settings and run > tests in the same way. > > ci.ignite.apache.org is sponsored and run by Grid Gain so > > Denis, Valentin, Petr, let's have a call to discuss how and when we can > implement these changes? > > [1] https://ci2.ignite.apache.org > [2] https://github.com/willy983/ci_tc_configuration > [3] https://www.jetbrains.com/help/teamcity/kotlin-dsl.html > > >> 3 авг. 2021 г., в 18:33, Dmitry Pavlov написал(а): >> >> Hi Igniters, >> >> I'm glad to announce that SberTech made an internal aggreement to sponsor a >> computing power to provide backup TeamCity instance. This instance is >> intended to be a geo-independent, secondary instance with availablility for >> community members. >> >> Thanks to JetBrains for providing license keys for TeamCity as their part of >> opensource sponsoring program. >> >> Most likely, we'll setup some domain name as tc.i.a.o or ci2.i.a.o. Please >> share your vision what would be most obvious. >> >> After a private discussions with Vitaliy Osipov and Petr Ivanov, I do >> believe that it would be possible to preserve current registered users. >> Build configurations are to be the same for the secondary instance. >> Technical details on how is could be achieved will be available later (most >> likely we'll start a sepearate thread to dicuss that). >> >> You are more than welcome to be an early adopters. >> >> Sincerely, >> Dmitriy Pavlov >> >
Re: Apache Ignite 2.12 RELEASE [Time, Scope, Manager]
Try now, please. > On 21 Oct 2021, at 17:47, Nikita Amelchev wrote: > > Hi, > > Petr, could you grant me TC permissions to run release builds please? > > ср, 20 окт. 2021 г. в 10:25, Pavel Tupitsyn : > >> >> Igniters, >> >> I've filed a blocker - release configurations on TeamCity should be fixed >> after recent .NET project structure refactoring: >> https://issues.apache.org/jira/browse/IGNITE-15779 >> >> I'm on vacation right now with limited internet access, I'll work on this >> ASAP next week. >> >> On Wed, Oct 13, 2021 at 2:33 PM Nikita Amelchev >> wrote: >> >>> Igniters, >>> >>> Scope freeze is planned for Friday, October 15. >>> I suggest creating the release branch on that date. >>> >>> The wiki page with the release info. [1] Please, check the fix version >>> of your issues. >>> >>> There are no unresolved blockers. >>> There are 3 important issues in the review state. [2] >>> >>> Also, please, pay attention to unresolved documentation issues. [3] >>> >>> [1] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.12 >>> [2] >>> https://issues.apache.org/jira/issues/?jql=(resolution%20%3D%20Unresolved%20AND%20project%20%3D%20%27Ignite%27%20AND%20type%20in%20(%22New%20Feature%22%2C%20Task%2C%20Sub-task%2C%20Improvement)%20AND%20fixVersion%20in%20(%272.12%27)%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20AND%20(labels%20in%20(%27important%27)%20OR%20Flags%20%3D%20Important))%20order%20by%20summary >>> [3] >>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.12%27)%20AND%20status%20NOT%20IN%20(Resolved%2C%20Closed)%20AND%20component%20in%20(documentation)%20ORDER%20BY%20priority%20%20%20%20%20%20%20%20%20 >>> >>> пт, 1 окт. 2021 г. в 19:06, Pavel Tupitsyn : I'm working on IGNITE-15504 and plan to finish it early next week. On Fri, Oct 1, 2021 at 6:08 PM Nikita Amelchev >>> wrote: > Igniters, > > I have created the wiki page for the 2.12 release. [1] > > The release scope contains 1 issue that is marked as a blocker: > IGNITE-15504 .NET: SDK 2.1 is out of support, make sure project can be > developed with newer SDKs [2] > > Folks, do not forget to document features (65 issues still not >>> resolved). > [3] > > Maxim, Ivan, > +1 to add these issues to the 2.12 scope. > > [1] >>> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.12 > [2] https://issues.apache.org/jira/browse/IGNITE-15504 > [3] > >>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.12%27)%20AND%20status%20NOT%20IN%20(Resolved%2C%20Closed)%20AND%20component%20in%20(documentation)%20ORDER%20BY%20priority%20%20%20%20%20%20%20%20%20 > > ср, 29 сент. 2021 г. в 11:28, Ivan Daschinsky : >> >> Created issues related building ODBC module, running C++ suites and >> removing VS project files >> >> 1. https://issues.apache.org/jira/browse/IGNITE-15637 >> 2.https://issues.apache.org/jira/browse/IGNITE-15636 >> >> вс, 26 сент. 2021 г. в 19:50, Ivan Daschinsky : >> >>> +1 >>> >>> Let's consider building odbc driver using Visual C++ 2017? >>> >>> 2015, 2017 and 2019 share the same redistributable package and it >>> is > the >>> default one in Windows 10. >>> >>> Also, let's remove vs project files, since the most of you all >>> agree > that >>> it is redundant. >>> >>> If both suggestions are ok, I will create ticketa soon. >>> >>> вс, 26 сент. 2021 г., 17:10 Pavel Tupitsyn : >>> +1 On Fri, Sep 24, 2021 at 8:04 PM Maxim Muzafarov < >>> mmu...@apache.org> wrote: > Hello Nikita, > > +1 if you will lead this release. > > > I'd suggest including into the release scope this one issue too: > > Snapshot restore must support restoring with indexes rebuild > https://issues.apache.org/jira/browse/IGNITE-14744 > > Hopefully, it will be completed by the end of October. > > On Fri, 24 Sept 2021 at 19:48, Nikita Amelchev < > namelc...@apache.org> > wrote: >> >> Dear Ignite Community! >> >> I suggest starting Apache Ignite 2.12 release activities. >> >> For now, we've accumulated a hundred resolved issues with new > features >> and bug fixes which are waiting for their release date. For > example, >> >> CDC Application >> Index Query API >> Utility for analyzing indexes >> Java compute tasks for C++ >> SQL commands statistics >> etc. >> >> I want to propose myself to be the releas
Re: Apache Ignite 2.12 RELEASE [Time, Scope, Manager]
Hi, Petr, could you grant me TC permissions to run release builds please? ср, 20 окт. 2021 г. в 10:25, Pavel Tupitsyn : > > Igniters, > > I've filed a blocker - release configurations on TeamCity should be fixed > after recent .NET project structure refactoring: > https://issues.apache.org/jira/browse/IGNITE-15779 > > I'm on vacation right now with limited internet access, I'll work on this > ASAP next week. > > On Wed, Oct 13, 2021 at 2:33 PM Nikita Amelchev > wrote: > > > Igniters, > > > > Scope freeze is planned for Friday, October 15. > > I suggest creating the release branch on that date. > > > > The wiki page with the release info. [1] Please, check the fix version > > of your issues. > > > > There are no unresolved blockers. > > There are 3 important issues in the review state. [2] > > > > Also, please, pay attention to unresolved documentation issues. [3] > > > > [1] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.12 > > [2] > > https://issues.apache.org/jira/issues/?jql=(resolution%20%3D%20Unresolved%20AND%20project%20%3D%20%27Ignite%27%20AND%20type%20in%20(%22New%20Feature%22%2C%20Task%2C%20Sub-task%2C%20Improvement)%20AND%20fixVersion%20in%20(%272.12%27)%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20AND%20(labels%20in%20(%27important%27)%20OR%20Flags%20%3D%20Important))%20order%20by%20summary > > [3] > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.12%27)%20AND%20status%20NOT%20IN%20(Resolved%2C%20Closed)%20AND%20component%20in%20(documentation)%20ORDER%20BY%20priority%20%20%20%20%20%20%20%20%20 > > > > пт, 1 окт. 2021 г. в 19:06, Pavel Tupitsyn : > > > > > > I'm working on IGNITE-15504 and plan to finish it early next week. > > > > > > On Fri, Oct 1, 2021 at 6:08 PM Nikita Amelchev > > wrote: > > > > > > > Igniters, > > > > > > > > I have created the wiki page for the 2.12 release. [1] > > > > > > > > The release scope contains 1 issue that is marked as a blocker: > > > > IGNITE-15504 .NET: SDK 2.1 is out of support, make sure project can be > > > > developed with newer SDKs [2] > > > > > > > > Folks, do not forget to document features (65 issues still not > > resolved). > > > > [3] > > > > > > > > Maxim, Ivan, > > > > +1 to add these issues to the 2.12 scope. > > > > > > > > [1] > > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.12 > > > > [2] https://issues.apache.org/jira/browse/IGNITE-15504 > > > > [3] > > > > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.12%27)%20AND%20status%20NOT%20IN%20(Resolved%2C%20Closed)%20AND%20component%20in%20(documentation)%20ORDER%20BY%20priority%20%20%20%20%20%20%20%20%20 > > > > > > > > ср, 29 сент. 2021 г. в 11:28, Ivan Daschinsky : > > > > > > > > > > Created issues related building ODBC module, running C++ suites and > > > > > removing VS project files > > > > > > > > > > 1. https://issues.apache.org/jira/browse/IGNITE-15637 > > > > > 2.https://issues.apache.org/jira/browse/IGNITE-15636 > > > > > > > > > > вс, 26 сент. 2021 г. в 19:50, Ivan Daschinsky : > > > > > > > > > > > +1 > > > > > > > > > > > > Let's consider building odbc driver using Visual C++ 2017? > > > > > > > > > > > > 2015, 2017 and 2019 share the same redistributable package and it > > is > > > > the > > > > > > default one in Windows 10. > > > > > > > > > > > > Also, let's remove vs project files, since the most of you all > > agree > > > > that > > > > > > it is redundant. > > > > > > > > > > > > If both suggestions are ok, I will create ticketa soon. > > > > > > > > > > > > вс, 26 сент. 2021 г., 17:10 Pavel Tupitsyn : > > > > > > > > > > > >> +1 > > > > > >> > > > > > >> On Fri, Sep 24, 2021 at 8:04 PM Maxim Muzafarov < > > mmu...@apache.org> > > > > > >> wrote: > > > > > >> > > > > > >> > Hello Nikita, > > > > > >> > > > > > > >> > +1 if you will lead this release. > > > > > >> > > > > > > >> > > > > > > >> > I'd suggest including into the release scope this one issue too: > > > > > >> > > > > > > >> > Snapshot restore must support restoring with indexes rebuild > > > > > >> > https://issues.apache.org/jira/browse/IGNITE-14744 > > > > > >> > > > > > > >> > Hopefully, it will be completed by the end of October. > > > > > >> > > > > > > >> > On Fri, 24 Sept 2021 at 19:48, Nikita Amelchev < > > > > namelc...@apache.org> > > > > > >> > wrote: > > > > > >> > > > > > > > >> > > Dear Ignite Community! > > > > > >> > > > > > > > >> > > I suggest starting Apache Ignite 2.12 release activities. > > > > > >> > > > > > > > >> > > For now, we've accumulated a hundred resolved issues with new > > > > features > > > > > >> > > and bug fixes which are waiting for their release date. For > > > > example, > > > > > >> > > > > > > > >> > > CDC Application > > > > > >> > > Index Query API > > > > > >> > > Utility for analyzing indexes
Ci and ci2 settings synchronization
Hello, Igniters. As you may know, recently, Sberbank sponsored servers capacity to setup new instance of Team City [1] to run Ignite tests. Right now, ci2 is fully ready for daily usage. We have exported and prepared Kotlin scripts [2] to keep TC settings as a code [3]. I think we should adjust both TC instances to use the same settings and run tests in the same way. ci.ignite.apache.org is sponsored and run by Grid Gain so Denis, Valentin, Petr, let's have a call to discuss how and when we can implement these changes? [1] https://ci2.ignite.apache.org [2] https://github.com/willy983/ci_tc_configuration [3] https://www.jetbrains.com/help/teamcity/kotlin-dsl.html > 3 авг. 2021 г., в 18:33, Dmitry Pavlov написал(а): > > Hi Igniters, > > I'm glad to announce that SberTech made an internal aggreement to sponsor a > computing power to provide backup TeamCity instance. This instance is > intended to be a geo-independent, secondary instance with availablility for > community members. > > Thanks to JetBrains for providing license keys for TeamCity as their part of > opensource sponsoring program. > > Most likely, we'll setup some domain name as tc.i.a.o or ci2.i.a.o. Please > share your vision what would be most obvious. > > After a private discussions with Vitaliy Osipov and Petr Ivanov, I do believe > that it would be possible to preserve current registered users. Build > configurations are to be the same for the secondary instance. Technical > details on how is could be achieved will be available later (most likely > we'll start a sepearate thread to dicuss that). > > You are more than welcome to be an early adopters. > > Sincerely, > Dmitriy Pavlov >
A new feedback has been added : 23
A new feedback has been added, go to bugyard.io to see all the details... https://bugyard.io A new feedback has been added "Change "GGCE" to "Ignite'" by AlexeyKukushkin View feedback https://app.bugyard.io/web/app/rycqZJDyY/f/61715e913ba4af0014cfb966
