Support for Apache Spark 3.1.2
Hello team, We have recently upgraded to use Spark 3.1.2 to utilize Kubernetes support and ability to use spot instances. However, we are not able to integrate Ignite with this version. I understand that a lot of people of raise interest in the same. In general, loosely couple these two projects so benefits of both can be achieved? Considering that Spark releases do not necessary align to Ignite and vice versa, would it make sense? Please suggest. Regards, Abhinav _ This message is for information purposes only, it is not a recommendation, advice, offer or solicitation to buy or sell a product or service nor an official confirmation of any transaction. It is directed at persons who are professionals and is not intended for retail customer use. Intended for recipient only. This message is subject to the terms at: www.barclays.com/emaildisclaimer. For important disclosures, please see: www.barclays.com/salesandtradingdisclaimer regarding market commentary from Barclays Sales and/or Trading, who are active market participants; https://www.investmentbank.barclays.com/disclosures/barclays-global-markets-disclosures.html regarding our standard terms for the Investment Bank of Barclays where we trade with you in principal-to-principal wholesale markets transactions; and in respect of Barclays Research, including disclosures relating to specific issuers, please see http://publicresearch.barclays.com. _ If you are incorporated or operating in Australia, please see https://www.home.barclays/disclosures/importantapacdisclosures.html for important disclosure. _ How we use personal information see our privacy notice https://www.investmentbank.barclays.com/disclosures/personalinformationuse.html _
Re: A new feedback has been added : 10
Hello! Dear developers, I suggest we should have someone responsible for handling bugyard reports and writing about that on developers list. Feedback is hidden behind login and I have no idea what's there, much less if it was fixed. I think we should have a reply to every Bugyard e-mail and maybe three-month long shifts of people responsible for that. Anybody wishing to take this role? Regards, -- Ilya Kasnacheev пн, 20 сент. 2021 г. в 17:10, Bugyard : > A new feedback has been added, go to bugyard.io to see all the details... > > https://bugyard.io > > A new feedback has been added > > "Looks like [Running Ignite with Java 11 or later] link is broken." by > tim239 > > View feedback > https://app.bugyard.io/web/app/rycqZJDyY/f/61488444507c91001448c81c
Re: Request for contributor permission
Hello! I have added you to Contributors role, you may assign tickets to yourself. Please make sure to read https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute Regards, -- Ilya Kasnacheev вт, 21 сент. 2021 г. в 17:54, Andrian Boşcanean : > Hello Ignite Community! > > My name is Andrian. I want to contribute to Apache Ignite and want to > start with this issue - IGNITE-15547, my JIRA username andrian.boscanean. > Any help on this will be appreciated. > > Thanks! > > On 2021/09/21 09:40:01, Andrian Boscanean > wrote: > > Dear all, > > > > Could I get contributors permission. > > > > Best regards, > > Andrian Boscanean > > >
Re: [DISCUSSION] Separate Jira project and Confluence space for Ignite 3
Dmitry, Thanks! Sure, this is not super urgent. Please let us know when this is ready. And feel free to ask me any questions if you have any. -Val On Tue, Sep 21, 2021 at 5:13 PM Dmitry Pavlov wrote: > Ok, if nobody minds, I'll create spaces a bit later. > > I hope it is not too urgent. > > Sincerely, > Dmitriy Pavlov > > On 2021/09/21 10:37:42, Valentin Kulichenko > wrote: > > Hi Dmitry, > > > > According to Infra, this has to be done through > http://selfserve.apache.org/, > > but only PMC chairs have access. > > > > Could you please assist with the creation of the Jira project and > > Confluence space? > > > > -Val > > > > On Tue, Sep 21, 2021 at 10:46 AM Valentin Kulichenko < > > valentin.kuliche...@gmail.com> wrote: > > > > > Infra requests created: > > > > > >- https://issues.apache.org/jira/browse/INFRA-22349 > > >- https://issues.apache.org/jira/browse/INFRA-22350 > > > > > > -Val > > > > > > On Mon, Sep 20, 2021 at 10:50 AM Petr Ivanov > wrote: > > > > > >> +1 > > >> > > >> Since we've agreed that there are two projects (that are Ignite2 and > > >> Ignite3), separate development environments seem to be logical and > natural > > >> course of things. > > >> > > >> > On 18 Sep 2021, at 12:42, Alexander Polovtcev < > alexpolovt...@gmail.com> > > >> wrote: > > >> > > > >> > +1 > > >> > This is a welcome proposal, because we already have some pending > Ignite > > >> 3 > > >> > specific documents, and it is not clear where to put them at the > moment. > > >> > > > >> > On Sat, Sep 18, 2021 at 4:22 AM Valentin Kulichenko < > > >> > valentin.kuliche...@gmail.com> wrote: > > >> > > > >> >> Igniters, > > >> >> > > >> >> I think it's clear to all of us that Ignite 2.x and 3.x will > coexist > > >> for a > > >> >> while. They are developed in separate Git repos, but we still > > >> accumulate > > >> >> the tickets for both versions in the same Jira project, which > seems to > > >> >> complicate the ticket management. > > >> >> > > >> >> For example, we use the "ignite-3" label for 3.x tickets, but this > > >> approach > > >> >> is fragile. If someone forgets to add the label to a new ticket, > it's > > >> >> likely to be lost. We need a better separation. > > >> >> > > >> >> All the above is true for Wiki as well - we use a single Confluence > > >> space. > > >> >> > > >> >> I suggest creating a new Jira project and a new Confluence space > for > > >> Ignite > > >> >> 3 and moving all the relevant tickets and pages there. > > >> >> > > >> >> Any thoughts or objections? > > >> >> > > >> >> -Val > > >> >> > > >> > > > >> > > > >> > -- > > >> > With regards, > > >> > Aleksandr Polovtcev > > >> > > >> > > >
Re: Request for contributor permission
Hello Ignite Community! My name is Andrian. I want to contribute to Apache Ignite and want to start with this issue - IGNITE-15547, my JIRA username andrian.boscanean. Any help on this will be appreciated. Thanks! On 2021/09/21 09:40:01, Andrian Boscanean wrote: > Dear all, > > Could I get contributors permission. > > Best regards, > Andrian Boscanean >
Re: [DISCUSSION] Separate Jira project and Confluence space for Ignite 3
Ok, if nobody minds, I'll create spaces a bit later. I hope it is not too urgent. Sincerely, Dmitriy Pavlov On 2021/09/21 10:37:42, Valentin Kulichenko wrote: > Hi Dmitry, > > According to Infra, this has to be done through http://selfserve.apache.org/, > but only PMC chairs have access. > > Could you please assist with the creation of the Jira project and > Confluence space? > > -Val > > On Tue, Sep 21, 2021 at 10:46 AM Valentin Kulichenko < > valentin.kuliche...@gmail.com> wrote: > > > Infra requests created: > > > >- https://issues.apache.org/jira/browse/INFRA-22349 > >- https://issues.apache.org/jira/browse/INFRA-22350 > > > > -Val > > > > On Mon, Sep 20, 2021 at 10:50 AM Petr Ivanov wrote: > > > >> +1 > >> > >> Since we've agreed that there are two projects (that are Ignite2 and > >> Ignite3), separate development environments seem to be logical and natural > >> course of things. > >> > >> > On 18 Sep 2021, at 12:42, Alexander Polovtcev > >> wrote: > >> > > >> > +1 > >> > This is a welcome proposal, because we already have some pending Ignite > >> 3 > >> > specific documents, and it is not clear where to put them at the moment. > >> > > >> > On Sat, Sep 18, 2021 at 4:22 AM Valentin Kulichenko < > >> > valentin.kuliche...@gmail.com> wrote: > >> > > >> >> Igniters, > >> >> > >> >> I think it's clear to all of us that Ignite 2.x and 3.x will coexist > >> for a > >> >> while. They are developed in separate Git repos, but we still > >> accumulate > >> >> the tickets for both versions in the same Jira project, which seems to > >> >> complicate the ticket management. > >> >> > >> >> For example, we use the "ignite-3" label for 3.x tickets, but this > >> approach > >> >> is fragile. If someone forgets to add the label to a new ticket, it's > >> >> likely to be lost. We need a better separation. > >> >> > >> >> All the above is true for Wiki as well - we use a single Confluence > >> space. > >> >> > >> >> I suggest creating a new Jira project and a new Confluence space for > >> Ignite > >> >> 3 and moving all the relevant tickets and pages there. > >> >> > >> >> Any thoughts or objections? > >> >> > >> >> -Val > >> >> > >> > > >> > > >> > -- > >> > With regards, > >> > Aleksandr Polovtcev > >> > >> >
Request for contributor permission
Dear all, Could I get contributors permission. Best regards, Andrian Boscanean
Re: [DISCUSSION] Separate Jira project and Confluence space for Ignite 3
Hi Dmitry, According to Infra, this has to be done through http://selfserve.apache.org/, but only PMC chairs have access. Could you please assist with the creation of the Jira project and Confluence space? -Val On Tue, Sep 21, 2021 at 10:46 AM Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Infra requests created: > >- https://issues.apache.org/jira/browse/INFRA-22349 >- https://issues.apache.org/jira/browse/INFRA-22350 > > -Val > > On Mon, Sep 20, 2021 at 10:50 AM Petr Ivanov wrote: > >> +1 >> >> Since we've agreed that there are two projects (that are Ignite2 and >> Ignite3), separate development environments seem to be logical and natural >> course of things. >> >> > On 18 Sep 2021, at 12:42, Alexander Polovtcev >> wrote: >> > >> > +1 >> > This is a welcome proposal, because we already have some pending Ignite >> 3 >> > specific documents, and it is not clear where to put them at the moment. >> > >> > On Sat, Sep 18, 2021 at 4:22 AM Valentin Kulichenko < >> > valentin.kuliche...@gmail.com> wrote: >> > >> >> Igniters, >> >> >> >> I think it's clear to all of us that Ignite 2.x and 3.x will coexist >> for a >> >> while. They are developed in separate Git repos, but we still >> accumulate >> >> the tickets for both versions in the same Jira project, which seems to >> >> complicate the ticket management. >> >> >> >> For example, we use the "ignite-3" label for 3.x tickets, but this >> approach >> >> is fragile. If someone forgets to add the label to a new ticket, it's >> >> likely to be lost. We need a better separation. >> >> >> >> All the above is true for Wiki as well - we use a single Confluence >> space. >> >> >> >> I suggest creating a new Jira project and a new Confluence space for >> Ignite >> >> 3 and moving all the relevant tickets and pages there. >> >> >> >> Any thoughts or objections? >> >> >> >> -Val >> >> >> > >> > >> > -- >> > With regards, >> > Aleksandr Polovtcev >> >>
Re: [RESULT][VOTE] Release Apache Ignite 2.11.0 RC2
Maxim, I'll prepare a dedicated blog post about Ignite.NET changes later this week. Thanks for driving the release! On Mon, Sep 20, 2021 at 11:20 PM Maxim Muzafarov wrote: > Denis, > > The post is added: > https://blogs.apache.org/ignite/entry/apache-ignite-2-11-stabilization > > I've fixed the image according to your suggestions. > > On Mon, 20 Sept 2021 at 21:35, Denis Magda wrote: > > > > Maxim, thanks for driving the release and preparing the announcement > > article! > > > > A few questions: > > > >- Should "dev" be replaced with "2.11" on the picture of the cellular > >clusters deployment section? > >- Will the article be published on our blogs.apache.org page? > > > > - > > Denis > > > > > > On Sat, Sep 18, 2021 at 9:36 PM Maxim Muzafarov > wrote: > > > > > Pavel, > > > > > > > > > I've prepared a draft blog post [1] for the 2.11 release announcement > > > message, however, this post doesn't include changes related to the > > > .NET part of the Apache Ignite. Will you prepare a dedicated post > > > related to the .NET changes or I should include them in this one? > > > > > > Folks, > > > all the comments are welcome. > > > > > > > > > [1] > > > > https://github.com/Mmuzaf/mmuzaf.github.io/blob/main/_post/Release_Newsletter_211.md > > > > > > > > > On Thu, 16 Sept 2021 at 17:21, Maxim Muzafarov > wrote: > > > > > > > > Hello, Igniters! > > > > > > > > Apache Ignite 2.11.0 release (RC2) has been accepted. > > > > > > > > 5 - "+1" votes received. > > > > 1 - "+0,5" vote received. > > > > > > > > Here are the votes received: > > > > > > > > - Pavel Tupitsyn (binding) > > > > - Alex Plehanov (binding) > > > > - Nikolay Izhikov (binding) > > > > - Ilya Kasnacheev > > > > - Ivan Daschinsky > > > > - Zhenya Stanilovsky > > > > > > > > > > > > Here is the link to the voting thread - > > > > > > > > https://lists.apache.org/thread.html/rab233aa7d737b84b678fb74c81a867e3aad270471a2aac85a4d35cb8%40%3Cdev.ignite.apache.org%3E > > > > > > > > Thank you! > > > >
Re: [DISCUSSION] Separate Jira project and Confluence space for Ignite 3
Infra requests created: - https://issues.apache.org/jira/browse/INFRA-22349 - https://issues.apache.org/jira/browse/INFRA-22350 -Val On Mon, Sep 20, 2021 at 10:50 AM Petr Ivanov wrote: > +1 > > Since we've agreed that there are two projects (that are Ignite2 and > Ignite3), separate development environments seem to be logical and natural > course of things. > > > On 18 Sep 2021, at 12:42, Alexander Polovtcev > wrote: > > > > +1 > > This is a welcome proposal, because we already have some pending Ignite 3 > > specific documents, and it is not clear where to put them at the moment. > > > > On Sat, Sep 18, 2021 at 4:22 AM Valentin Kulichenko < > > valentin.kuliche...@gmail.com> wrote: > > > >> Igniters, > >> > >> I think it's clear to all of us that Ignite 2.x and 3.x will coexist > for a > >> while. They are developed in separate Git repos, but we still accumulate > >> the tickets for both versions in the same Jira project, which seems to > >> complicate the ticket management. > >> > >> For example, we use the "ignite-3" label for 3.x tickets, but this > approach > >> is fragile. If someone forgets to add the label to a new ticket, it's > >> likely to be lost. We need a better separation. > >> > >> All the above is true for Wiki as well - we use a single Confluence > space. > >> > >> I suggest creating a new Jira project and a new Confluence space for > Ignite > >> 3 and moving all the relevant tickets and pages there. > >> > >> Any thoughts or objections? > >> > >> -Val > >> > > > > > > -- > > With regards, > > Aleksandr Polovtcev > >
