[VOTE] Release Apache Ignite 2.12.0 RC1
Dear Community, The release candidate is ready. I have uploaded a release candidate to: https://dist.apache.org/repos/dist/dev/ignite/2.12.0-rc1/ https://dist.apache.org/repos/dist/dev/ignite/packages_2.12.0-rc1/ The following staging can be used for testing: https://repository.apache.org/content/repositories/orgapacheignite-1538 Tag name is 2.12.0-rc1: https://gitbox.apache.org/repos/asf?p=ignite.git;a=commit;h=refs/tags/2.12.0-rc1 RELEASE_NOTES: https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=ignite-2.12 Complete list of resolved issues: 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%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20ORDER%20BY%20priority DEVNOTES: https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=ignite-2.12 Additional checks have been performed (available for users included into the release group on TeamCity). TC [Check RC: Licenses, compile, chksum] https://ci2.ignite.apache.org/buildConfiguration/ignite2_Release_ApacheIgniteReleaseJava8_PrepareVote4CheckRcLicensesChecksum/6253654?showRootCauses=false=true TC [2] Compare w/ Previous Release https://ci2.ignite.apache.org/buildConfiguration/ignite2_Release_ApacheIgniteReleaseJava8_IgniteRelease72CheckFileConsistency/6253662?showRootCauses=false The vote is formal, see voting guidelines https://www.apache.org/foundation/voting.html +1 - to accept Apache Ignite 2.12.0-rc1 0 - don't care either way -1 - DO NOT accept Apache Ignite Ignite 2.12.0-rc1 (explain why) See notes on how to verify release here https://www.apache.org/info/verification.html and https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-P5.VotingonReleaseandReleaseVerification This vote will be open until Mon Jan 10, 2022, 16:00 UTC. The voting time was increased due to the long NY weekend. Please, write me down the thread if you need additional time to check the release. https://www.timeanddate.com/countdown/vote?iso=20220110T16=0=VOTE+on+the+Apache+Ignite+Release+2.12.0+RC1=sanserif -- Best wishes, Amelchev Nikita
Re: Apache Ignite 2.12 RELEASE [Time, Scope, Manager]
Pavel, currently they offers only free 14-day trial, unfortunately чт, 30 дек. 2021 г. в 13:16, Pavel Tupitsyn : > Ivan, > > MyGet is free within some limits. > It was introduced to make release verification easier - no need to unzip > nuggets into a local dir, just install them from MyGet. > > Nikita, > > No, we won't upload NuGet packages to any registry before a successful RC > vote. > Only then we'll push them to nuget.org (as we always do). > > > On Thu, Dec 30, 2021 at 12:38 PM Ivan Daschinsky > wrote: > > > I'm sorry, but I've never understand the purpose of uploading to MyGet. > It > > is not free registry and it is required to pay to use it. > > > > чт, 30 дек. 2021 г. в 12:34, Nikita Amelchev : > > > > > Pavel, thank you. > > > > > > The "[3] Build & Upload Nuget Staging Packages" configuration also > > > pushes packages to the MyGet. > > > Will packages be published to some package registry? > > > > > > чт, 30 дек. 2021 г. в 10:15, Pavel Tupitsyn : > > > > > > > > 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 < > namelc...@apache.org > > > > > > 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 < > ivanda...@gmail.com > > >: > > > >>> > > > > > >>> > > Also, zookeeper ip finder depends on good old log4j 1.x > > > >>> > > > > > >>> > > вт, 21 дек. 2021 г. в 13:32, Ivan Daschinsky < > > ivanda...@gmail.com > > > >: > > > >>> > > > > > >>> > > > As for me, I am +1 for removing ZookeeperIpFinder from > > > ignite-zookeeper. > > > >>> > > > > > > >>> > > > > > > >>> > > > вт, 21 дек. 2021 г. в 13:26, Nikita Amelchev < > > > namelc...@apache.org>: > > > >>> > > > > > > >>> > > >> 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. > > > >>> >
Re: [PROPOSAL] Release Calcite-based SQL engine as an experimental feature
> it would be great to release a new SQL engine in 2.13 as an experimental feature. ++1 On Thu, Dec 30, 2021 at 12:55 PM Alex Plehanov wrote: > Andrey, > > > Is this [1] a full scope of the tickets that MUST be resolved before the > engine could be merged? > Yes, we must resolve at least these tickets before merging. If you see any > other release blockers fill free to attach them to this ticket. > > > I think we have to add instructions to the readme file on how to turn a > new SQL engine on. > Sure, I think it should be the part of documentation ticket. > > > Also, I don't like the module name "ignite-calcite", because Calcite is > an independent project. > Personally, I see no problems here (but it's discussable). We have a lot of > modules where the name is an independent project: "ignite-kafka", > "ignite-spring", "ignite-kubernetes", "ignite-log4j", "ignite-zookeeper", > etc. > > > So, would you mind renaming the module to e.g. "ignite-sql-engine" or > "ignite-sql"? > Module "ignite-indexing" also contains SQL engine, so names like > "ignite-sql-engine" or "ignite-sql" will be ambiguous. > > чт, 30 дек. 2021 г. в 13:54, Andrey Mashenkov >: > > > Alex, > > it would be great to release a new SQL engine in 2.13 as an > > experimental feature. > > > > Is this [1] a full scope of the tickets that MUST be resolved before the > > engine could be merged? > > I think we have to add instructions to the readme file on how to turn a > new > > SQL engine on. > > > > Also, I don't like the module name "ignite-calcite", because Calcite is > an > > independent project. > > and Ignite just uses it. > > So, would you mind renaming the module to e.g. "ignite-sql-engine" or > > "ignite-sql"? > > > > [1] https://issues.apache.org/jira/browse/IGNITE-15436 > > > > On Thu, Dec 30, 2021 at 11:10 AM Zhenya Stanilovsky > > wrote: > > > > > > > > Alex, great ! > > > If someone wants to touch codebase somehow plz use this branch [1] > > > Test passed can be found here [2] [3] > > > > > > [1] https://github.com/apache/ignite/tree/sql-calcite/modules/calcite > > > [2] > > > > > > https://github.com/apache/ignite/tree/sql-calcite/modules/calcite/src/test/java/org/apache/ignite/internal/processors/query/calcite > > > [3] > > > > > > https://github.com/apache/ignite/tree/sql-calcite/modules/calcite/src/test/sql > > > > > > > > > > >> > > > >>>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? > > > >> > > > >> > > > >> > > > >> > > > > > > > > -- > > Best regards, > > Andrey V. Mashenkov > > >
Re: Apache Ignite 2.12 RELEASE [Time, Scope, Manager]
Ivan, MyGet is free within some limits. It was introduced to make release verification easier - no need to unzip nuggets into a local dir, just install them from MyGet. Nikita, No, we won't upload NuGet packages to any registry before a successful RC vote. Only then we'll push them to nuget.org (as we always do). On Thu, Dec 30, 2021 at 12:38 PM Ivan Daschinsky wrote: > I'm sorry, but I've never understand the purpose of uploading to MyGet. It > is not free registry and it is required to pay to use it. > > чт, 30 дек. 2021 г. в 12:34, Nikita Amelchev : > > > Pavel, thank you. > > > > The "[3] Build & Upload Nuget Staging Packages" configuration also > > pushes packages to the MyGet. > > Will packages be published to some package registry? > > > > чт, 30 дек. 2021 г. в 10:15, Pavel Tupitsyn : > > > > > > 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 < > ivanda...@gmail.com > > >: > > >>> > > > > >>> > > > As for me, I am +1 for removing ZookeeperIpFinder from > > ignite-zookeeper. > > >>> > > > > > >>> > > > > > >>> > > > вт, 21 дек. 2021 г. в 13:26, Nikita Amelchev < > > namelc...@apache.org>: > > >>> > > > > > >>> > > >> 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]
Re: [PROPOSAL] Release Calcite-based SQL engine as an experimental feature
Andrey, > Is this [1] a full scope of the tickets that MUST be resolved before the engine could be merged? Yes, we must resolve at least these tickets before merging. If you see any other release blockers fill free to attach them to this ticket. > I think we have to add instructions to the readme file on how to turn a new SQL engine on. Sure, I think it should be the part of documentation ticket. > Also, I don't like the module name "ignite-calcite", because Calcite is an independent project. Personally, I see no problems here (but it's discussable). We have a lot of modules where the name is an independent project: "ignite-kafka", "ignite-spring", "ignite-kubernetes", "ignite-log4j", "ignite-zookeeper", etc. > So, would you mind renaming the module to e.g. "ignite-sql-engine" or "ignite-sql"? Module "ignite-indexing" also contains SQL engine, so names like "ignite-sql-engine" or "ignite-sql" will be ambiguous. чт, 30 дек. 2021 г. в 13:54, Andrey Mashenkov : > Alex, > it would be great to release a new SQL engine in 2.13 as an > experimental feature. > > Is this [1] a full scope of the tickets that MUST be resolved before the > engine could be merged? > I think we have to add instructions to the readme file on how to turn a new > SQL engine on. > > Also, I don't like the module name "ignite-calcite", because Calcite is an > independent project. > and Ignite just uses it. > So, would you mind renaming the module to e.g. "ignite-sql-engine" or > "ignite-sql"? > > [1] https://issues.apache.org/jira/browse/IGNITE-15436 > > On Thu, Dec 30, 2021 at 11:10 AM Zhenya Stanilovsky > wrote: > > > > > Alex, great ! > > If someone wants to touch codebase somehow plz use this branch [1] > > Test passed can be found here [2] [3] > > > > [1] https://github.com/apache/ignite/tree/sql-calcite/modules/calcite > > [2] > > > https://github.com/apache/ignite/tree/sql-calcite/modules/calcite/src/test/java/org/apache/ignite/internal/processors/query/calcite > > [3] > > > https://github.com/apache/ignite/tree/sql-calcite/modules/calcite/src/test/sql > > > > > > > >> > > >>>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? > > >> > > >> > > >> > > >> > > > > -- > Best regards, > Andrey V. Mashenkov >
Re: Apache Ignite 2.12 RELEASE [Time, Scope, Manager]
I'm sorry, but I've never understand the purpose of uploading to MyGet. It is not free registry and it is required to pay to use it. чт, 30 дек. 2021 г. в 12:34, Nikita Amelchev : > Pavel, thank you. > > The "[3] Build & Upload Nuget Staging Packages" configuration also > pushes packages to the MyGet. > Will packages be published to some package registry? > > чт, 30 дек. 2021 г. в 10:15, Pavel Tupitsyn : > > > > 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 < > namelc...@apache.org>: > >>> > > > > >>> > > >> 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. > >>> > > >> > > > > >
Re: Apache Ignite 2.12 RELEASE [Time, Scope, Manager]
Pavel, thank you. The "[3] Build & Upload Nuget Staging Packages" configuration also pushes packages to the MyGet. Will packages be published to some package registry? чт, 30 дек. 2021 г. в 10:15, Pavel Tupitsyn : > > 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, Вячеслав Коптилин >>> > > >> >> > > >> >: >>> > > >> > >>> > > >> > 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 >>> > > >> > > > > >
Re: [PROPOSAL] Release Calcite-based SQL engine as an experimental feature
Alex, it would be great to release a new SQL engine in 2.13 as an experimental feature. Is this [1] a full scope of the tickets that MUST be resolved before the engine could be merged? I think we have to add instructions to the readme file on how to turn a new SQL engine on. Also, I don't like the module name "ignite-calcite", because Calcite is an independent project. and Ignite just uses it. So, would you mind renaming the module to e.g. "ignite-sql-engine" or "ignite-sql"? [1] https://issues.apache.org/jira/browse/IGNITE-15436 On Thu, Dec 30, 2021 at 11:10 AM Zhenya Stanilovsky wrote: > > Alex, great ! > If someone wants to touch codebase somehow plz use this branch [1] > Test passed can be found here [2] [3] > > [1] https://github.com/apache/ignite/tree/sql-calcite/modules/calcite > [2] > https://github.com/apache/ignite/tree/sql-calcite/modules/calcite/src/test/java/org/apache/ignite/internal/processors/query/calcite > [3] > https://github.com/apache/ignite/tree/sql-calcite/modules/calcite/src/test/sql > > > > >> > >>>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? > >> > >> > >> > >> -- Best regards, Andrey V. Mashenkov
Re: [PROPOSAL] Release Calcite-based SQL engine as an experimental feature
Alex, great ! If someone wants to touch codebase somehow plz use this branch [1] Test passed can be found here [2] [3] [1] https://github.com/apache/ignite/tree/sql-calcite/modules/calcite [2] https://github.com/apache/ignite/tree/sql-calcite/modules/calcite/src/test/java/org/apache/ignite/internal/processors/query/calcite [3] https://github.com/apache/ignite/tree/sql-calcite/modules/calcite/src/test/sql > >> >>>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? >> >> >> >>
