Re: Apache Ignite 2.12 RELEASE [Time, Scope, Manager]
NuGet packages are now prepared as part of the main config "[1] Release Build". They are placed to svn/vote/apache-ignite-2.12.0-nuget.zip [1] I propose to remove "[3] Build & Upload Nuget Staging Packages" configuration. NuGet packages can be downloaded from vote artifacts and verified locally by installing from a folder: dotnet add package Apache.Ignite --source ~/Downloads/and/so/on Thoughts, objections? [1] https://ci.ignite.apache.org/buildConfiguration/Releases_ApacheIgniteMain_ReleaseBuild/6347367?buildTab=artifacts#%2Frelease-2.12.0-rc1.zip!%2Fpackages;%2Frelease-2.12.0-rc1.zip!%2Fsvn%2Fvote%2Fapache-ignite-2.12.0-nuget.zip On Thu, Dec 30, 2021 at 9:29 AM Pavel Tupitsyn wrote: > Hello Nikita, > > I'll have a look. > > On Wed, Dec 29, 2021 at 6:12 PM Nikita Amelchev > wrote: > >> Hello. Petr, Pavel, >> >> It seems that the release profile to build the Nuget package was >> broken. Could you please help with fixing it? >> >> [1] >> https://ci.ignite.apache.org/buildConfiguration/ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages/6347635 >> >> вс, 26 дек. 2021 г. в 16:29, Nikita Amelchev : >> > >> > Igniters, >> > >> > There are two issues left to release 2.12: >> > >> > 1. The log4j dependency update in the REST module. The fix is leaving >> > only the slf4j facade for third-party libraries and allowing a user to >> > configure the underlying logging framework yourself. [1] >> > >> > 2. Migration zookeeper-ip-finder to the extensions [2] (and then >> > update log4j dependency) as discussed in the thread [3]. >> > >> > Please, join the review. I have a plan to merge it at the nearest time >> > and prepare RC. >> > >> > Also, I suggest including issues [4, 5] that block the snapshot restore >> process. >> > >> > [1] https://issues.apache.org/jira/browse/IGNITE-13464 >> > [2] https://issues.apache.org/jira/browse/IGNITE-16182 >> > [3] https://lists.apache.org/thread/bdt9yoy3so9p26ymox3rxh45vk85toc5 >> > [4] https://issues.apache.org/jira/browse/IGNITE-16194 >> > [5] https://issues.apache.org/jira/browse/IGNITE-16177 >> > >> > вт, 21 дек. 2021 г. в 13:34, Ivan Daschinsky : >> > > >> > > Also, zookeeper ip finder depends on good old log4j 1.x >> > > >> > > вт, 21 дек. 2021 г. в 13:32, Ivan Daschinsky : >> > > >> > > > As for me, I am +1 for removing ZookeeperIpFinder from >> ignite-zookeeper. >> > > > >> > > > >> > > > вт, 21 дек. 2021 г. в 13:26, Nikita Amelchev > >: >> > > > >> > > >> Folks, >> > > >> >> > > >> What do you think about fixing vulnerability log4j dependencies in >> > > >> rest-http, zookeeper modules in 2.12? >> > > >> >> > > >> The issue is in progress and can be resolved in a few days. [1] >> > > >> >> > > >> I suggest including it to the scope. >> > > >> >> > > >> [1] https://issues.apache.org/jira/browse/IGNITE-13464 >> > > >> >> > > >> пт, 17 дек. 2021 г. в 16:22, Вячеслав Коптилин < >> slava.kopti...@gmail.com >> > > >> >: >> > > >> > >> > > >> > Hi Nikita, >> > > >> > >> > > >> > The proposed timeline looks great. Thank you! >> > > >> > >> > > >> > Slava. >> > > >> > >> > > >> > пт, 17 дек. 2021 г. в 15:32, Nikita Amelchev < >> namelc...@apache.org>: >> > > >> > >> > > >> > > Hello, Slava. >> > > >> > > >> > > >> > > I am planning the following timeline: >> > > >> > > >> > > >> > > Voting Date: December 20, 2021 >> > > >> > > Release Date: December 27, 2021 >> > > >> > > >> > > >> > > чт, 16 дек. 2021 г. в 11:52, Вячеслав Коптилин < >> > > >> slava.kopti...@gmail.com>: >> > > >> > > > >> > > >> > > > Hello Nikita, >> > > >> > > > >> > > >> > > > > I have cherry-picked the issue [1] to the 2.12. It updates >> the >> > > >> log4j >> > > >> > > > version to 2.16. >> > > >> > > > Thanks a lot! >> > > >> > > > >> > > >> > > > Could you please share a current timeline for the rest steps >> > > >> related to >> > > >> > > the >> > > >> > > > release? >> > > >> > > > >> > > >> > > > Thanks, >> > > >> > > > S. >> > > >> > > > >> > > >> > > > ср, 15 дек. 2021 г. в 21:45, Nikita Amelchev < >> namelc...@apache.org >> > > >> >: >> > > >> > > > >> > > >> > > > > I have cherry-picked the issue [1] to the 2.12. It updates >> the >> > > >> log4j >> > > >> > > > > version to 2.16. >> > > >> > > > > >> > > >> > > > > Slava, thank you. >> > > >> > > > > >> > > >> > > > > [1] https://issues.apache.org/jira/browse/IGNITE-16127 >> > > >> > > > > >> > > >> > > > > ср, 15 дек. 2021 г. в 14:14, Вячеслав Коптилин < >> > > >> > > slava.kopti...@gmail.com>: >> > > >> > > > > > >> > > >> > > > > > Hello, >> > > >> > > > > > >> > > >> > > > > > Nikita, it seems that we have to add the following ticket >> > > >> > > > > > https://issues.apache.org/jira/browse/IGNITE-16127 to >> Apache >> > > >> Ignite >> > > >> > > 2.12 >> > > >> > > > > > release. >> > > >> > > > > > >> > > >> > > > > > Thanks, >> > > >> > > > > > S. >> > > >> > > > > > >> > > >> > > > > > >> > > >> > > > > > вт, 14 дек. 2021 г. в 09:54, Nikita Amelchev < >> > > >> namelc...@apache.org>: >> > > >> > > > > > >> > > >> > > > > > > +1 to
Re: Apache Ignite 2.12 RELEASE [Time, Scope, Manager]
Hello Nikita, I'll have a look. On Wed, Dec 29, 2021 at 6:12 PM Nikita Amelchev wrote: > Hello. Petr, Pavel, > > It seems that the release profile to build the Nuget package was > broken. Could you please help with fixing it? > > [1] > https://ci.ignite.apache.org/buildConfiguration/ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages/6347635 > > вс, 26 дек. 2021 г. в 16:29, Nikita Amelchev : > > > > Igniters, > > > > There are two issues left to release 2.12: > > > > 1. The log4j dependency update in the REST module. The fix is leaving > > only the slf4j facade for third-party libraries and allowing a user to > > configure the underlying logging framework yourself. [1] > > > > 2. Migration zookeeper-ip-finder to the extensions [2] (and then > > update log4j dependency) as discussed in the thread [3]. > > > > Please, join the review. I have a plan to merge it at the nearest time > > and prepare RC. > > > > Also, I suggest including issues [4, 5] that block the snapshot restore > process. > > > > [1] https://issues.apache.org/jira/browse/IGNITE-13464 > > [2] https://issues.apache.org/jira/browse/IGNITE-16182 > > [3] https://lists.apache.org/thread/bdt9yoy3so9p26ymox3rxh45vk85toc5 > > [4] https://issues.apache.org/jira/browse/IGNITE-16194 > > [5] https://issues.apache.org/jira/browse/IGNITE-16177 > > > > вт, 21 дек. 2021 г. в 13:34, Ivan Daschinsky : > > > > > > Also, zookeeper ip finder depends on good old log4j 1.x > > > > > > вт, 21 дек. 2021 г. в 13:32, Ivan Daschinsky : > > > > > > > As for me, I am +1 for removing ZookeeperIpFinder from > ignite-zookeeper. > > > > > > > > > > > > вт, 21 дек. 2021 г. в 13:26, Nikita Amelchev : > > > > > > > >> Folks, > > > >> > > > >> What do you think about fixing vulnerability log4j dependencies in > > > >> rest-http, zookeeper modules in 2.12? > > > >> > > > >> The issue is in progress and can be resolved in a few days. [1] > > > >> > > > >> I suggest including it to the scope. > > > >> > > > >> [1] https://issues.apache.org/jira/browse/IGNITE-13464 > > > >> > > > >> пт, 17 дек. 2021 г. в 16:22, Вячеслав Коптилин < > slava.kopti...@gmail.com > > > >> >: > > > >> > > > > >> > Hi Nikita, > > > >> > > > > >> > The proposed timeline looks great. Thank you! > > > >> > > > > >> > Slava. > > > >> > > > > >> > пт, 17 дек. 2021 г. в 15:32, Nikita Amelchev < > namelc...@apache.org>: > > > >> > > > > >> > > Hello, Slava. > > > >> > > > > > >> > > I am planning the following timeline: > > > >> > > > > > >> > > Voting Date: December 20, 2021 > > > >> > > Release Date: December 27, 2021 > > > >> > > > > > >> > > чт, 16 дек. 2021 г. в 11:52, Вячеслав Коптилин < > > > >> slava.kopti...@gmail.com>: > > > >> > > > > > > >> > > > Hello Nikita, > > > >> > > > > > > >> > > > > I have cherry-picked the issue [1] to the 2.12. It updates > the > > > >> log4j > > > >> > > > version to 2.16. > > > >> > > > Thanks a lot! > > > >> > > > > > > >> > > > Could you please share a current timeline for the rest steps > > > >> related to > > > >> > > the > > > >> > > > release? > > > >> > > > > > > >> > > > Thanks, > > > >> > > > S. > > > >> > > > > > > >> > > > ср, 15 дек. 2021 г. в 21:45, Nikita Amelchev < > namelc...@apache.org > > > >> >: > > > >> > > > > > > >> > > > > I have cherry-picked the issue [1] to the 2.12. It updates > the > > > >> log4j > > > >> > > > > version to 2.16. > > > >> > > > > > > > >> > > > > Slava, thank you. > > > >> > > > > > > > >> > > > > [1] https://issues.apache.org/jira/browse/IGNITE-16127 > > > >> > > > > > > > >> > > > > ср, 15 дек. 2021 г. в 14:14, Вячеслав Коптилин < > > > >> > > slava.kopti...@gmail.com>: > > > >> > > > > > > > > >> > > > > > Hello, > > > >> > > > > > > > > >> > > > > > Nikita, it seems that we have to add the following ticket > > > >> > > > > > https://issues.apache.org/jira/browse/IGNITE-16127 to > Apache > > > >> Ignite > > > >> > > 2.12 > > > >> > > > > > release. > > > >> > > > > > > > > >> > > > > > Thanks, > > > >> > > > > > S. > > > >> > > > > > > > > >> > > > > > > > > >> > > > > > вт, 14 дек. 2021 г. в 09:54, Nikita Amelchev < > > > >> namelc...@apache.org>: > > > >> > > > > > > > > >> > > > > > > +1 to move these auth issues to the next release. I will > > > >> prepare > > > >> > > RC at > > > >> > > > > > > the nearest time. > > > >> > > > > > > > > > >> > > > > > > пн, 13 дек. 2021 г. в 16:13, Pavel Tupitsyn < > > > >> ptupit...@apache.org > > > >> > > >: > > > >> > > > > > > > > > > >> > > > > > > > Agree with Nikolay, let's proceed with the release. > > > >> > > > > > > > > > > >> > > > > > > > On Mon, Dec 13, 2021 at 3:31 PM Nikolay Izhikov < > > > >> > > nizhi...@apache.org > > > >> > > > > > > > > >> > > > > > > wrote: > > > >> > > > > > > > > > > >> > > > > > > > > Nikita. > > > >> > > > > > > > > > > > >> > > > > > > > > I don’t think IGNITE-16068 is a release blocker. > > > >> > > > > > > > > > > > >> > > > > > > > > 1. It only happens when authentication enabled. > > > >> > > > > > > > > 2. There is at lease 2 workar
Re: [PROPOSAL] Release Calcite-based SQL engine as an experimental feature
I forgot to attach links: [1]: https://cwiki.apache.org/confluence/display/IGNITE/IEP-37%3A+New+query+execution+engine [2]: https://github.com/apache/ignite/tree/sql-calcite ср, 29 дек. 2021 г. в 21:00, Alex Plehanov : > Hello, Igniters! > > As you may already know there is the new Ignite SQL engine based on Apache > Calcite currently under development. > > Reasons to move from H2-based engine and motivation for creating the new > one in details described in IEP-37 [1]. > > You can find all related to the new engine source code changes in the > "sql-calcite" branch [2]. > > Calcite-based SQL engine is not production-ready yet and has a lot of > known issues. In the future, the new engine should be fully independent of > "ignite-indexing" and H2, but now it relies on schema management and > indexes implemented in the "ignite-indexing" module and can't work without > the old engine. Despite all of the above mentioned, in the current state, > it has its own parsing, planning and execution flow and is almost as > functional as the H2-based SQL engine. > > Some users are already interested in the Calcite-based engine and asking > about the development status and release dates. Calcite-based SQL engine > will be the only SQL engine in Ignite 3.0. Perhaps even in 2.x we can get > rid of the H2-based engine at some time in the future. There is some syntax > difference between Calcite and H2 (Calcite is closer to SQL standards than > H2) and a totally new execution flow. After the release of this feature, > users can try their queries and determine if any adaptation for them is > required. With the new planning and execution flow, perhaps, some queries > will be executed more effectively, users can redirect such queries to the > new engine. > > I think we can provide an opportunity to users to try the new engine and > release it as an experimental feature with the next Apache Ignite version > (2.13). > > What do you think? >
[PROPOSAL] Release Calcite-based SQL engine as an experimental feature
Hello, Igniters! As you may already know there is the new Ignite SQL engine based on Apache Calcite currently under development. Reasons to move from H2-based engine and motivation for creating the new one in details described in IEP-37 [1]. You can find all related to the new engine source code changes in the "sql-calcite" branch [2]. Calcite-based SQL engine is not production-ready yet and has a lot of known issues. In the future, the new engine should be fully independent of "ignite-indexing" and H2, but now it relies on schema management and indexes implemented in the "ignite-indexing" module and can't work without the old engine. Despite all of the above mentioned, in the current state, it has its own parsing, planning and execution flow and is almost as functional as the H2-based SQL engine. Some users are already interested in the Calcite-based engine and asking about the development status and release dates. Calcite-based SQL engine will be the only SQL engine in Ignite 3.0. Perhaps even in 2.x we can get rid of the H2-based engine at some time in the future. There is some syntax difference between Calcite and H2 (Calcite is closer to SQL standards than H2) and a totally new execution flow. After the release of this feature, users can try their queries and determine if any adaptation for them is required. With the new planning and execution flow, perhaps, some queries will be executed more effectively, users can redirect such queries to the new engine. I think we can provide an opportunity to users to try the new engine and release it as an experimental feature with the next Apache Ignite version (2.13). What do you think?
Re: Apache Ignite 2.12 RELEASE [Time, Scope, Manager]
Hello. Petr, Pavel, It seems that the release profile to build the Nuget package was broken. Could you please help with fixing it? [1] https://ci.ignite.apache.org/buildConfiguration/ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages/6347635 вс, 26 дек. 2021 г. в 16:29, Nikita Amelchev : > > Igniters, > > There are two issues left to release 2.12: > > 1. The log4j dependency update in the REST module. The fix is leaving > only the slf4j facade for third-party libraries and allowing a user to > configure the underlying logging framework yourself. [1] > > 2. Migration zookeeper-ip-finder to the extensions [2] (and then > update log4j dependency) as discussed in the thread [3]. > > Please, join the review. I have a plan to merge it at the nearest time > and prepare RC. > > Also, I suggest including issues [4, 5] that block the snapshot restore > process. > > [1] https://issues.apache.org/jira/browse/IGNITE-13464 > [2] https://issues.apache.org/jira/browse/IGNITE-16182 > [3] https://lists.apache.org/thread/bdt9yoy3so9p26ymox3rxh45vk85toc5 > [4] https://issues.apache.org/jira/browse/IGNITE-16194 > [5] https://issues.apache.org/jira/browse/IGNITE-16177 > > вт, 21 дек. 2021 г. в 13:34, Ivan Daschinsky : > > > > Also, zookeeper ip finder depends on good old log4j 1.x > > > > вт, 21 дек. 2021 г. в 13:32, Ivan Daschinsky : > > > > > As for me, I am +1 for removing ZookeeperIpFinder from ignite-zookeeper. > > > > > > > > > вт, 21 дек. 2021 г. в 13:26, Nikita Amelchev : > > > > > >> Folks, > > >> > > >> What do you think about fixing vulnerability log4j dependencies in > > >> rest-http, zookeeper modules in 2.12? > > >> > > >> The issue is in progress and can be resolved in a few days. [1] > > >> > > >> I suggest including it to the scope. > > >> > > >> [1] https://issues.apache.org/jira/browse/IGNITE-13464 > > >> > > >> пт, 17 дек. 2021 г. в 16:22, Вячеслав Коптилин > >> >: > > >> > > > >> > Hi Nikita, > > >> > > > >> > The proposed timeline looks great. Thank you! > > >> > > > >> > Slava. > > >> > > > >> > пт, 17 дек. 2021 г. в 15:32, Nikita Amelchev : > > >> > > > >> > > Hello, Slava. > > >> > > > > >> > > I am planning the following timeline: > > >> > > > > >> > > Voting Date: December 20, 2021 > > >> > > Release Date: December 27, 2021 > > >> > > > > >> > > чт, 16 дек. 2021 г. в 11:52, Вячеслав Коптилин < > > >> slava.kopti...@gmail.com>: > > >> > > > > > >> > > > Hello Nikita, > > >> > > > > > >> > > > > I have cherry-picked the issue [1] to the 2.12. It updates the > > >> log4j > > >> > > > version to 2.16. > > >> > > > Thanks a lot! > > >> > > > > > >> > > > Could you please share a current timeline for the rest steps > > >> related to > > >> > > the > > >> > > > release? > > >> > > > > > >> > > > Thanks, > > >> > > > S. > > >> > > > > > >> > > > ср, 15 дек. 2021 г. в 21:45, Nikita Amelchev > >> >: > > >> > > > > > >> > > > > I have cherry-picked the issue [1] to the 2.12. It updates the > > >> log4j > > >> > > > > version to 2.16. > > >> > > > > > > >> > > > > Slava, thank you. > > >> > > > > > > >> > > > > [1] https://issues.apache.org/jira/browse/IGNITE-16127 > > >> > > > > > > >> > > > > ср, 15 дек. 2021 г. в 14:14, Вячеслав Коптилин < > > >> > > slava.kopti...@gmail.com>: > > >> > > > > > > > >> > > > > > Hello, > > >> > > > > > > > >> > > > > > Nikita, it seems that we have to add the following ticket > > >> > > > > > https://issues.apache.org/jira/browse/IGNITE-16127 to Apache > > >> Ignite > > >> > > 2.12 > > >> > > > > > release. > > >> > > > > > > > >> > > > > > Thanks, > > >> > > > > > S. > > >> > > > > > > > >> > > > > > > > >> > > > > > вт, 14 дек. 2021 г. в 09:54, Nikita Amelchev < > > >> namelc...@apache.org>: > > >> > > > > > > > >> > > > > > > +1 to move these auth issues to the next release. I will > > >> prepare > > >> > > RC at > > >> > > > > > > the nearest time. > > >> > > > > > > > > >> > > > > > > пн, 13 дек. 2021 г. в 16:13, Pavel Tupitsyn < > > >> ptupit...@apache.org > > >> > > >: > > >> > > > > > > > > > >> > > > > > > > Agree with Nikolay, let's proceed with the release. > > >> > > > > > > > > > >> > > > > > > > On Mon, Dec 13, 2021 at 3:31 PM Nikolay Izhikov < > > >> > > nizhi...@apache.org > > >> > > > > > > > >> > > > > > > wrote: > > >> > > > > > > > > > >> > > > > > > > > Nikita. > > >> > > > > > > > > > > >> > > > > > > > > I don’t think IGNITE-16068 is a release blocker. > > >> > > > > > > > > > > >> > > > > > > > > 1. It only happens when authentication enabled. > > >> > > > > > > > > 2. There is at lease 2 workarounds: > > >> > > > > > > > > a. Use the same file.encoding for all Ignite > > >> nodes. > > >> > > > > > > > > b. Use only latin characters in user login. > > >> > > > > > > > > > > >> > > > > > > > > I propose to postpone this ticket and move on with the > > >> release. > > >> > > > > > > > > > > >> > > > > > > > > > 13 дек. 2021 г., в 15:28, Nikita Amelchev < > > >> > > namelc...@apache.org> > > >> > > > > > > > > написал(а): > > >> >
