Re: [ANNOUNCE] Welcome Vladislav Pyatkov as a new committer
Congrats, Vlad! 2021-12-22 20:48 GMT+03:00, Ivan Daschinsky : > Vlad, congrats! You have definitely deserved it! > > ср, 22 дек. 2021 г. в 20:40, Andrey Mashenkov : > >> Congrats, Vlad! >> >> ср, 22 дек. 2021 г., 20:23 Valentin Kulichenko < >> valentin.kuliche...@gmail.com>: >> >> > The Apache Ignite Project Management Committee (PMC) has invited >> Vladislav >> > Pyatkov to become a new committer and are happy to announce that he has >> > accepted. >> > >> > Vladislav is a veteran of the Apache Ignite project. He joined the >> > community in 2016. >> > He participated in the development of Ignite 1.x, 2.x and he is >> > actively >> > working on a new Apache Ignite 3.0 release. >> > >> > Being a committer enables easier contribution to the project since >> > there >> > is no need to go via the patch submission process. This should enable >> > better productivity. >> > >> > Please join me in welcoming Vlad, and congratulating him on the new >> > role >> > in the Apache Ignite Community. >> > >> > -Val >> > >> > > > -- > Sincerely yours, Ivan Daschinskiy > -- Best regards, Ivan Pavlukhin
Re: [ANNOUNCE] Welcome Vladislav Pyatkov as a new committer
Vlad, congrats! You have definitely deserved it! ср, 22 дек. 2021 г. в 20:40, Andrey Mashenkov : > Congrats, Vlad! > > ср, 22 дек. 2021 г., 20:23 Valentin Kulichenko < > valentin.kuliche...@gmail.com>: > > > The Apache Ignite Project Management Committee (PMC) has invited > Vladislav > > Pyatkov to become a new committer and are happy to announce that he has > > accepted. > > > > Vladislav is a veteran of the Apache Ignite project. He joined the > > community in 2016. > > He participated in the development of Ignite 1.x, 2.x and he is actively > > working on a new Apache Ignite 3.0 release. > > > > Being a committer enables easier contribution to the project since there > > is no need to go via the patch submission process. This should enable > > better productivity. > > > > Please join me in welcoming Vlad, and congratulating him on the new role > > in the Apache Ignite Community. > > > > -Val > > > -- Sincerely yours, Ivan Daschinskiy
Re: [ANNOUNCE] Welcome Vladislav Pyatkov as a new committer
Congrats, Vlad! ср, 22 дек. 2021 г., 20:23 Valentin Kulichenko < valentin.kuliche...@gmail.com>: > The Apache Ignite Project Management Committee (PMC) has invited Vladislav > Pyatkov to become a new committer and are happy to announce that he has > accepted. > > Vladislav is a veteran of the Apache Ignite project. He joined the > community in 2016. > He participated in the development of Ignite 1.x, 2.x and he is actively > working on a new Apache Ignite 3.0 release. > > Being a committer enables easier contribution to the project since there > is no need to go via the patch submission process. This should enable > better productivity. > > Please join me in welcoming Vlad, and congratulating him on the new role > in the Apache Ignite Community. > > -Val >
[ANNOUNCE] Welcome Vladislav Pyatkov as a new committer
The Apache Ignite Project Management Committee (PMC) has invited Vladislav Pyatkov to become a new committer and are happy to announce that he has accepted. Vladislav is a veteran of the Apache Ignite project. He joined the community in 2016. He participated in the development of Ignite 1.x, 2.x and he is actively working on a new Apache Ignite 3.0 release. Being a committer enables easier contribution to the project since there is no need to go via the patch submission process. This should enable better productivity. Please join me in welcoming Vlad, and congratulating him on the new role in the Apache Ignite Community. -Val
Re: [RESULT] [VOTE] Release Apache Ignite 2.11.1 RC2
Erlan, thanks, I've reviewed and merged your changes. - Denis On Wed, Dec 22, 2021 at 10:24 AM Erlan Aytpaev wrote: > I've just created a new PR > https://github.com/apache/ignite-website/pull/96. > Please review and merge it. > Also, there is another PR https://github.com/apache/ignite-website/pull/95 > . > It will fix an incorrect email address on the download page. > > On Wed, Dec 22, 2021 at 8:52 PM Denis Magda wrote: > > > I thought that Erlan and Maxim would fix it. I've pinged Erlan. I'm in > the > > process of changing laptops, thus, can't do it myself. > > > > On Wed, Dec 22, 2021 at 9:08 AM Ilya Kasnacheev < > ilya.kasnach...@gmail.com > > > > > wrote: > > > > > Hello! > > > > > > Downloads page does not seem to have correct release date for releases > > > older than 2.11. Can this be fixed? > > > > > > Regards, > > > -- > > > Ilya Kasnacheev > > > > > > > > > вт, 21 дек. 2021 г. в 14:47, Denis Magda : > > > > > > > Hi Maxim, > > > > > > > > Just a reminder that since the release of the new website, we need to > > > > update the download.pug [1] file in case of a release and then > generate > > > the > > > > HTML version following this updated instruction. If you have any > > > questions, > > > > please reach out to Erlan (CC-ed). > > > > > > > > [1] > > > https://github.com/apache/ignite-website/blob/master/_src/download.pug > > > > [2] > > > https://cwiki.apache.org/confluence/display/IGNITE/Website+Development > > > > > > > > On Tue, Dec 21, 2021 at 4:36 AM Maxim Muzafarov > > > wrote: > > > > > > > > > Hello, Igniters! > > > > > > > > > > > > > > > Thanks to everyone. The vote is closed. > > > > > The emergency Apache Ignite 2.11.1 release (RC2) has been accepted. > > > > > I will continue on with the release. > > > > > > > > > > 5 - "+1" votes received and no "0", "-1" votes. > > > > > > > > > > > > > > > Here are the votes received: > > > > > > > > > > - Ilya Kasnacheev (binding) > > > > > - Pavel Tupitsyn (binding) > > > > > - Ivan Daschinsky > > > > > - Nikolay Izhikov (binding) > > > > > - Vyacheslav Koptilin > > > > > - Alex Plehanov (binding) > > > > > - Valentin Kulichenko (binding) > > > > > > > > > > > > > > > Here is the link to the voting thread: > > > > > https://lists.apache.org/thread/2pwc0fv0pczhnxbyfkdhl1m3yvh8vrpb > > > > > > > > > > Thank you! > > > > > > > > > > > > > > >
Re: [RESULT] [VOTE] Release Apache Ignite 2.11.1 RC2
I've just created a new PR https://github.com/apache/ignite-website/pull/96. Please review and merge it. Also, there is another PR https://github.com/apache/ignite-website/pull/95. It will fix an incorrect email address on the download page. On Wed, Dec 22, 2021 at 8:52 PM Denis Magda wrote: > I thought that Erlan and Maxim would fix it. I've pinged Erlan. I'm in the > process of changing laptops, thus, can't do it myself. > > On Wed, Dec 22, 2021 at 9:08 AM Ilya Kasnacheev > > wrote: > > > Hello! > > > > Downloads page does not seem to have correct release date for releases > > older than 2.11. Can this be fixed? > > > > Regards, > > -- > > Ilya Kasnacheev > > > > > > вт, 21 дек. 2021 г. в 14:47, Denis Magda : > > > > > Hi Maxim, > > > > > > Just a reminder that since the release of the new website, we need to > > > update the download.pug [1] file in case of a release and then generate > > the > > > HTML version following this updated instruction. If you have any > > questions, > > > please reach out to Erlan (CC-ed). > > > > > > [1] > > https://github.com/apache/ignite-website/blob/master/_src/download.pug > > > [2] > > https://cwiki.apache.org/confluence/display/IGNITE/Website+Development > > > > > > On Tue, Dec 21, 2021 at 4:36 AM Maxim Muzafarov > > wrote: > > > > > > > Hello, Igniters! > > > > > > > > > > > > Thanks to everyone. The vote is closed. > > > > The emergency Apache Ignite 2.11.1 release (RC2) has been accepted. > > > > I will continue on with the release. > > > > > > > > 5 - "+1" votes received and no "0", "-1" votes. > > > > > > > > > > > > Here are the votes received: > > > > > > > > - Ilya Kasnacheev (binding) > > > > - Pavel Tupitsyn (binding) > > > > - Ivan Daschinsky > > > > - Nikolay Izhikov (binding) > > > > - Vyacheslav Koptilin > > > > - Alex Plehanov (binding) > > > > - Valentin Kulichenko (binding) > > > > > > > > > > > > Here is the link to the voting thread: > > > > https://lists.apache.org/thread/2pwc0fv0pczhnxbyfkdhl1m3yvh8vrpb > > > > > > > > Thank you! > > > > > > > > > >
Re: [COMMUNITY] Apache Ignite Community Recap and Celebration of Project Evangelists
Excellent 2021 recap! Thanks Kseniya for sharing, driving and helping with so many activities. Can't wait to see the non-code contributions service to track responses on the user lists and other forums. -- Denis On Wed, Dec 22, 2021 at 8:50 AM Kseniya Romanova wrote: > Hi, Igniters! > > As 2021 comes to a close, let's review and celebrate the amazing > community-driven contributions that made Apache Ignite better throughout > the year: > > — The community produced 2 releases 2.10 and 2.11 (2.12 is on its way) > which introduced: > ‒ Transparent Data Encryption (TDE) technology - the Cache Key Rotation > machinery. From now on the Apache Ignite fully satisfies the PCI DSS[1], > which requires the protection of stored data at rest; > ‒ Significant improvements to Ignite thin clients: Added async API, > Kubernetes discovery, extended transaction, cluster and SQL API for various > platforms, added Continuous Query support, partition awareness, and more; > ‒ Change Data Capture (CDC) support, which allows users to build their > deployments on a new type of architecture - asynchronous data replication > between clusters; > ‒ IndexQuery API, which enables building fast index queries over > build-in Ignite indexes. Unlike SQL, it works without the overhead for > queries parsing and planning > > — Ignite 3.0 Alphas were released [2][3] > — We welcomed 10 new committers and 1 PMC member > > Check and celebrate the most active code contributors here: > ‒ Core and Documentation[4] > ‒ Extensions[5] > ‒ Ignite website[6] > > — Downloads for 2021 exceeded downloads for 2020 by 65%, with hundreds of > thousands of downloads per month. > — The Apache Software Foundation (ASF) ranked Ignite second on the Top 5 > Big Data user lists, third on the Top 5 Big Data dev lists, second on the > Top 5 user lists, and third on the Top 5 repos by size [7][8] > — In DB-Engines Ranking[9], Apache Ignite gained nine points (December > 2021 versus December 2020). > — The Apache Ignite website was updated and improved [10]. > — The community organized 13 Ignite meetups[11]. > — Ignite Summit[12] was hosted first in May and then in November—with 33 > speakers, 8 pre-conference training, and 700 attendees. > — Fifty-eight developers contributed to Project Awareness by creating > blogs, tutorials, and demos and by presenting at online and offline events > worldwide. > — The Recognition service to track non-code Project Awareness > contributions was launched[13]. I’ve recorded a video about the service for > you[14] > > That’s what we as a community did in 2021. Impressive, isn’t it? > > Now, I’ll list 2021’s 10 most active non-code contributors, all of whom > contributed to spreading the word about Ignite: > > Val Kulichenko > Denis Magda > Alexander Kozhenkov > Stephen Darlington > Pavel Tupitsyn > Anton Vinogradov > Courtney Robinson > Maxim Muzafarov > Nikolay Izhikov > Semyon Danilov > > We are all proud of you! You did an outstanding job. My team and I want > others to recognize your contributions! So, we created badges[15] that you > can add to your LinkedIn profile (or to any other profile) to emphasize > your role! Please check your emails. > > Have a Merry Christmas, Happy New Year, and stay awesome! > Next year, we will rock again together! > > Cheers, > Kseniya > Apache Ignite PMC, > Director of Community Relations at GridGain > > [1] > https://en.wikipedia.org/wiki/Payment_Card_Industry_Data_Security_Standard > [2]https://github.com/apache/ignite-3/ > [3]Ignite 3.0 Alpha 3 Community Gathering recording > https://youtu.be/XanOleiBLlU > [4]Ignite Core & Docs top-contributors 2021 > https://github.com/apache/ignite/graphs/contributors?from=2021-01-03=2021-12-22=c > [5]Ignite Extensions top-contributors 2021 > https://github.com/apache/ignite-extensions/graphs/contributors?from=2021-01-01=2021-12-22=c > [6]Ignite website top-contributors 2021 > https://github.com/apache/ignite-website/graphs/contributors?from=2021-01-01=2021-12-22=c > [7] https://www.apache.org/foundation/docs/FY2021AnnualReport.pdf > [8] > https://blogs.apache.org/ignite/entry/apache-ignite-momentum-highlights-from > [9] https://db-engines.com/en/ranking > [10] https://ignite.apache.org/ > [11] https://ignite.apache.org/events.html#meetups > [12] https://ignite-summit.org/ > [13] https://recognition.gridgain.com/main?date=this-year > [14] https://youtu.be/AmO4dNdZHb8 > [15] > https://www.credly.com/org/gridgain/badge/ignite-project-awareness-top-contributor-2021 > >
Re: [RESULT] [VOTE] Release Apache Ignite 2.11.1 RC2
I thought that Erlan and Maxim would fix it. I've pinged Erlan. I'm in the process of changing laptops, thus, can't do it myself. On Wed, Dec 22, 2021 at 9:08 AM Ilya Kasnacheev wrote: > Hello! > > Downloads page does not seem to have correct release date for releases > older than 2.11. Can this be fixed? > > Regards, > -- > Ilya Kasnacheev > > > вт, 21 дек. 2021 г. в 14:47, Denis Magda : > > > Hi Maxim, > > > > Just a reminder that since the release of the new website, we need to > > update the download.pug [1] file in case of a release and then generate > the > > HTML version following this updated instruction. If you have any > questions, > > please reach out to Erlan (CC-ed). > > > > [1] > https://github.com/apache/ignite-website/blob/master/_src/download.pug > > [2] > https://cwiki.apache.org/confluence/display/IGNITE/Website+Development > > > > On Tue, Dec 21, 2021 at 4:36 AM Maxim Muzafarov > wrote: > > > > > Hello, Igniters! > > > > > > > > > Thanks to everyone. The vote is closed. > > > The emergency Apache Ignite 2.11.1 release (RC2) has been accepted. > > > I will continue on with the release. > > > > > > 5 - "+1" votes received and no "0", "-1" votes. > > > > > > > > > Here are the votes received: > > > > > > - Ilya Kasnacheev (binding) > > > - Pavel Tupitsyn (binding) > > > - Ivan Daschinsky > > > - Nikolay Izhikov (binding) > > > - Vyacheslav Koptilin > > > - Alex Plehanov (binding) > > > - Valentin Kulichenko (binding) > > > > > > > > > Here is the link to the voting thread: > > > https://lists.apache.org/thread/2pwc0fv0pczhnxbyfkdhl1m3yvh8vrpb > > > > > > Thank you! > > > > > >
Re: [RESULT] [VOTE] Release Apache Ignite 2.11.1 RC2
Hello! Downloads page does not seem to have correct release date for releases older than 2.11. Can this be fixed? Regards, -- Ilya Kasnacheev вт, 21 дек. 2021 г. в 14:47, Denis Magda : > Hi Maxim, > > Just a reminder that since the release of the new website, we need to > update the download.pug [1] file in case of a release and then generate the > HTML version following this updated instruction. If you have any questions, > please reach out to Erlan (CC-ed). > > [1] https://github.com/apache/ignite-website/blob/master/_src/download.pug > [2] https://cwiki.apache.org/confluence/display/IGNITE/Website+Development > > On Tue, Dec 21, 2021 at 4:36 AM Maxim Muzafarov wrote: > > > Hello, Igniters! > > > > > > Thanks to everyone. The vote is closed. > > The emergency Apache Ignite 2.11.1 release (RC2) has been accepted. > > I will continue on with the release. > > > > 5 - "+1" votes received and no "0", "-1" votes. > > > > > > Here are the votes received: > > > > - Ilya Kasnacheev (binding) > > - Pavel Tupitsyn (binding) > > - Ivan Daschinsky > > - Nikolay Izhikov (binding) > > - Vyacheslav Koptilin > > - Alex Plehanov (binding) > > - Valentin Kulichenko (binding) > > > > > > Here is the link to the voting thread: > > https://lists.apache.org/thread/2pwc0fv0pczhnxbyfkdhl1m3yvh8vrpb > > > > Thank you! > > >
[COMMUNITY] Apache Ignite Community Recap and Celebration of Project Evangelists
Hi, Igniters! As 2021 comes to a close, let's review and celebrate the amazing community-driven contributions that made Apache Ignite better throughout the year: — The community produced 2 releases 2.10 and 2.11 (2.12 is on its way) which introduced: ‒ Transparent Data Encryption (TDE) technology - the Cache Key Rotation machinery. From now on the Apache Ignite fully satisfies the PCI DSS[1], which requires the protection of stored data at rest; ‒ Significant improvements to Ignite thin clients: Added async API, Kubernetes discovery, extended transaction, cluster and SQL API for various platforms, added Continuous Query support, partition awareness, and more; ‒ Change Data Capture (CDC) support, which allows users to build their deployments on a new type of architecture - asynchronous data replication between clusters; ‒ IndexQuery API, which enables building fast index queries over build-in Ignite indexes. Unlike SQL, it works without the overhead for queries parsing and planning — Ignite 3.0 Alphas were released [2][3] — We welcomed 10 new committers and 1 PMC member Check and celebrate the most active code contributors here: ‒ Core and Documentation[4] ‒ Extensions[5] ‒ Ignite website[6] — Downloads for 2021 exceeded downloads for 2020 by 65%, with hundreds of thousands of downloads per month. — The Apache Software Foundation (ASF) ranked Ignite second on the Top 5 Big Data user lists, third on the Top 5 Big Data dev lists, second on the Top 5 user lists, and third on the Top 5 repos by size [7][8] — In DB-Engines Ranking[9], Apache Ignite gained nine points (December 2021 versus December 2020). — The Apache Ignite website was updated and improved [10]. — The community organized 13 Ignite meetups[11]. — Ignite Summit[12] was hosted first in May and then in November—with 33 speakers, 8 pre-conference training, and 700 attendees. — Fifty-eight developers contributed to Project Awareness by creating blogs, tutorials, and demos and by presenting at online and offline events worldwide. — The Recognition service to track non-code Project Awareness contributions was launched[13]. I’ve recorded a video about the service for you[14] That’s what we as a community did in 2021. Impressive, isn’t it? Now, I’ll list 2021’s 10 most active non-code contributors, all of whom contributed to spreading the word about Ignite: Val Kulichenko Denis Magda Alexander Kozhenkov Stephen Darlington Pavel Tupitsyn Anton Vinogradov Courtney Robinson Maxim Muzafarov Nikolay Izhikov Semyon Danilov We are all proud of you! You did an outstanding job. My team and I want others to recognize your contributions! So, we created badges[15] that you can add to your LinkedIn profile (or to any other profile) to emphasize your role! Please check your emails. Have a Merry Christmas, Happy New Year, and stay awesome! Next year, we will rock again together! Cheers, Kseniya Apache Ignite PMC, Director of Community Relations at GridGain [1] https://en.wikipedia.org/wiki/Payment_Card_Industry_Data_Security_Standard [2]https://github.com/apache/ignite-3/ [3]Ignite 3.0 Alpha 3 Community Gathering recording https://youtu.be/XanOleiBLlU [4]Ignite Core & Docs top-contributors 2021 https://github.com/apache/ignite/graphs/contributors?from=2021-01-03=2021-12-22=c [5]Ignite Extensions top-contributors 2021 https://github.com/apache/ignite-extensions/graphs/contributors?from=2021-01-01=2021-12-22=c [6]Ignite website top-contributors 2021 https://github.com/apache/ignite-website/graphs/contributors?from=2021-01-01=2021-12-22=c [7] https://www.apache.org/foundation/docs/FY2021AnnualReport.pdf [8] https://blogs.apache.org/ignite/entry/apache-ignite-momentum-highlights-from [9] https://db-engines.com/en/ranking [10] https://ignite.apache.org/ [11] https://ignite.apache.org/events.html#meetups [12] https://ignite-summit.org/ [13] https://recognition.gridgain.com/main?date=this-year [14] https://youtu.be/AmO4dNdZHb8 [15] https://www.credly.com/org/gridgain/badge/ignite-project-awareness-top-contributor-2021
Re: Move the Zookeeper IP-finder to the ignite-extensions
Let's explain more thoroughly Ignite module ignite-zookeeper contains 2 packages 1. org.apache.ignite.spi.discovery.tcp.ipfinder.zk; It contains one class, TcpDiscoveryZookeeperIpFinder, that is just implementation of TcpDiscoveryIpFinder, it uses Apache Curator ServiceDiscovery recipe to register and retrieve IP addresses of other nodes and use these addresses in TcpDiscovery process. It is literally few hundred lines of code with comments and imports. 2. org.apache.ignite.spi.discovery.zk It contains full blown implementation of DiscoverySpi. Quite complex and a lot of code. These two packages have nothing common except substring "zookeeper". I don't have any idea why they are present in one package. ср, 22 дек. 2021 г. в 14:00, Ivan Daschinsky : > I am +1 for removing ZookeeperIpFinder from ignite-zookeeper module. It is > not needed here. > > ср, 22 дек. 2021 г. в 14:00, Ivan Daschinsky : > >> >> a lot of code in core code base is dedicated for enabling it. >> It is simply not true. ZookeeperDiscovery has nothing common with >> ZookeeperIpFinder. >> >> The last one is simply one class and similar to others IP finders. >> >> ср, 22 дек. 2021 г. в 13:25, Ilya Kasnacheev : >> >>> Hello! >>> >>> I think it might not be a good idea, since Zookeeper IP Finder is not >>> stand-alone - a lot of code in core code base is dedicated for enabling >>> it. >>> This code may break unnoticed if Zookeeper IP Finder is not built/tested >>> on >>> every commit. >>> >>> Regards, >>> -- >>> Ilya Kasnacheev >>> >>> >>> ср, 22 дек. 2021 г. в 12:09, Sergei Ryzhov : >>> >>> > Hi, igniters, >>> > >>> > I've created an issue [1] to move the zookeeper IP-finder to the >>> > ignite-extensions. The motivation is the same as with migration of >>> > cloud-based IP-finders - to remove integration dependency of the >>> > release cycle on Ignite releases. Also, the log4j dependency with >>> > vulnerabilities (needed for Apache Curator) will be removed from the >>> Ignite >>> > release. >>> > >>> > Any objections? >>> > >>> > [1] https://issues.apache.org/jira/browse/IGNITE-16182 >>> > -- >>> > Best regards, >>> > Sergei Ryzhov >>> > >>> >> >> >> -- >> Sincerely yours, Ivan Daschinskiy >> > > > -- > Sincerely yours, Ivan Daschinskiy > -- Sincerely yours, Ivan Daschinskiy
Re: Move the Zookeeper IP-finder to the ignite-extensions
I am +1 for removing ZookeeperIpFinder from ignite-zookeeper module. It is not needed here. ср, 22 дек. 2021 г. в 14:00, Ivan Daschinsky : > >> a lot of code in core code base is dedicated for enabling it. > It is simply not true. ZookeeperDiscovery has nothing common with > ZookeeperIpFinder. > > The last one is simply one class and similar to others IP finders. > > ср, 22 дек. 2021 г. в 13:25, Ilya Kasnacheev : > >> Hello! >> >> I think it might not be a good idea, since Zookeeper IP Finder is not >> stand-alone - a lot of code in core code base is dedicated for enabling >> it. >> This code may break unnoticed if Zookeeper IP Finder is not built/tested >> on >> every commit. >> >> Regards, >> -- >> Ilya Kasnacheev >> >> >> ср, 22 дек. 2021 г. в 12:09, Sergei Ryzhov : >> >> > Hi, igniters, >> > >> > I've created an issue [1] to move the zookeeper IP-finder to the >> > ignite-extensions. The motivation is the same as with migration of >> > cloud-based IP-finders - to remove integration dependency of the >> > release cycle on Ignite releases. Also, the log4j dependency with >> > vulnerabilities (needed for Apache Curator) will be removed from the >> Ignite >> > release. >> > >> > Any objections? >> > >> > [1] https://issues.apache.org/jira/browse/IGNITE-16182 >> > -- >> > Best regards, >> > Sergei Ryzhov >> > >> > > > -- > Sincerely yours, Ivan Daschinskiy > -- Sincerely yours, Ivan Daschinskiy
Re: Move the Zookeeper IP-finder to the ignite-extensions
>> a lot of code in core code base is dedicated for enabling it. It is simply not true. ZookeeperDiscovery has nothing common with ZookeeperIpFinder. The last one is simply one class and similar to others IP finders. ср, 22 дек. 2021 г. в 13:25, Ilya Kasnacheev : > Hello! > > I think it might not be a good idea, since Zookeeper IP Finder is not > stand-alone - a lot of code in core code base is dedicated for enabling it. > This code may break unnoticed if Zookeeper IP Finder is not built/tested on > every commit. > > Regards, > -- > Ilya Kasnacheev > > > ср, 22 дек. 2021 г. в 12:09, Sergei Ryzhov : > > > Hi, igniters, > > > > I've created an issue [1] to move the zookeeper IP-finder to the > > ignite-extensions. The motivation is the same as with migration of > > cloud-based IP-finders - to remove integration dependency of the > > release cycle on Ignite releases. Also, the log4j dependency with > > vulnerabilities (needed for Apache Curator) will be removed from the > Ignite > > release. > > > > Any objections? > > > > [1] https://issues.apache.org/jira/browse/IGNITE-16182 > > -- > > Best regards, > > Sergei Ryzhov > > > -- Sincerely yours, Ivan Daschinskiy
Re: Move the Zookeeper IP-finder to the ignite-extensions
Hello! I think it might not be a good idea, since Zookeeper IP Finder is not stand-alone - a lot of code in core code base is dedicated for enabling it. This code may break unnoticed if Zookeeper IP Finder is not built/tested on every commit. Regards, -- Ilya Kasnacheev ср, 22 дек. 2021 г. в 12:09, Sergei Ryzhov : > Hi, igniters, > > I've created an issue [1] to move the zookeeper IP-finder to the > ignite-extensions. The motivation is the same as with migration of > cloud-based IP-finders - to remove integration dependency of the > release cycle on Ignite releases. Also, the log4j dependency with > vulnerabilities (needed for Apache Curator) will be removed from the Ignite > release. > > Any objections? > > [1] https://issues.apache.org/jira/browse/IGNITE-16182 > -- > Best regards, > Sergei Ryzhov >
Re: Move the Zookeeper IP-finder to the ignite-extensions
Sergei, Please make sure this will not break the Ducktests. AFAIK, we have zookeeper tests there. On Wed, Dec 22, 2021 at 12:09 PM Sergei Ryzhov wrote: > Hi, igniters, > > I've created an issue [1] to move the zookeeper IP-finder to the > ignite-extensions. The motivation is the same as with migration of > cloud-based IP-finders - to remove integration dependency of the > release cycle on Ignite releases. Also, the log4j dependency with > vulnerabilities (needed for Apache Curator) will be removed from the Ignite > release. > > Any objections? > > [1] https://issues.apache.org/jira/browse/IGNITE-16182 > -- > Best regards, > Sergei Ryzhov >
Move the Zookeeper IP-finder to the ignite-extensions
Hi, igniters, I've created an issue [1] to move the zookeeper IP-finder to the ignite-extensions. The motivation is the same as with migration of cloud-based IP-finders - to remove integration dependency of the release cycle on Ignite releases. Also, the log4j dependency with vulnerabilities (needed for Apache Curator) will be removed from the Ignite release. Any objections? [1] https://issues.apache.org/jira/browse/IGNITE-16182 -- Best regards, Sergei Ryzhov
