Re: [VOTE] Apache Ignite PMC Chair
+1 for Pavel Tupitsyn (binding) On Mon, Oct 28, 2019 at 9:38 PM Kumar, Sushil (CWM-NR) < sushil.ku...@rbccm.com> wrote: > + 1 Dmitry Pavlov > > On Mon, Oct 28, 2019 at 9:07 PM Denis Magda wrote: > > > > > > +1 for Nikolay Izhikov (binding) > > > > > > - > > > Denis > > > > > > > > > On Mon, Oct 28, 2019 at 11:06 AM Denis Magda > wrote: > > > > > > > Ignite community, > > > > > > > > Please cast a vote for one of the following candidates: > > > > > > > >- Alexey Goncharuk > > > >- Dmitry Pavlov > > > >- Nikolay Izhikov > > > >- Pavel Tupitsyn > > > > > > > > Everybody is encouraged to take part in the vote, however, > > > > remember that only the binding votes of PMC members result in the > > > > Chair election. The candidates can vote for themselves. The vote > > > > will end on November 1st, > > > > 11:00 AM Pacific Time. More details about the next steps are here: > > > > https://www.apache.org/dev/pmc.html#newchair > > > > > > > > - > > > > Denis > > > > > > > > -- > Best regards, > Ivan Pavlukhin > > > This E-Mail (including any attachments) may contain privileged or > confidential information. It is intended only for the addressee(s) > indicated above. > > The sender does not waive any of its rights, privileges or other > protections respecting this information. > > Any distribution, copying or other use of this E-Mail or the information > it contains, by other than an intended recipient, is not sanctioned and is > prohibited. > > If you received this E-Mail in error, please delete it and advise the > sender (by return E-Mail or otherwise) immediately. > > This E-Mail (including any attachments) has been scanned for viruses. > > It is believed to be free of any virus or other defect that might affect > any computer system into which it is received and opened. > > However, it is the responsibility of the recipient to ensure that it is > virus free. > > The sender accepts no responsibility for any loss or damage arising in any > way from its use. > > E-Mail received by or sent from RBC Capital Markets is subject to review > by Supervisory personnel. > > Such communications are retained and may be produced to regulatory > authorities or others with legal rights to the information. > > IRS CIRCULAR 230 NOTICE: TO COMPLY WITH U.S. TREASURY REGULATIONS, WE > ADVISE YOU THAT ANY U.S. FEDERAL TAX ADVICE INCLUDED IN THIS COMMUNICATION > IS NOT INTENDED OR WRITTEN TO BE USED, AND CANNOT BE USED, TO AVOID ANY > U.S. FEDERAL TAX PENALTIES OR TO PROMOTE, MARKET, OR RECOMMEND TO ANOTHER > PARTY ANY TRANSACTION OR MATTER. >
Re: [DISCUSS] Proposal for Ignite Extensions as a separate Bahir module or Incubator project
Folks, Just another one name candidate "ignite-integrations" Or are there not only integrations? вт, 29 окт. 2019 г. в 03:31, Saikat Maitra : > > Hi Denis, > > I meant we can create dedicated repository for individual extensions and we > can create submodules inside each specific repository for individual > extensions versions. > > Regards, > Saikat > > > On Mon, Oct 28, 2019 at 7:14 PM Saikat Maitra > wrote: > > > Hi Denis, > > > > Yes, dedicated repository is also a good idea and we can create submodules > > inside each specific repository for individual extensions. > > > > Regards, > > Saikat > > > > > > > > On Mon, Oct 28, 2019 at 2:34 PM Denis Magda wrote: > > > >> Folks, > >> > >> What do you think about having a dedicated repository for each extension > >> instead of a single one? It sounds complicated but might be worthwhile for > >> cases when an integration requires to support several versions. Take Spark > >> or Hibernate as an example, we already provide different versions of > >> Ignite > >> packages for various Spark/Hibernate versions. It will be easier to handle > >> if Spark or Hibernate had their own repos. > >> > >> - > >> Denis > >> > >> > >> On Sat, Oct 26, 2019 at 10:06 PM Saikat Maitra > >> wrote: > >> > >> > Hello Alexey, > >> > > >> > Thank you for your email. Yes, I am also aligned for ignite-extensions. > >> > > >> > If others are also ok we can create the new repository with name > >> > ignite-extensions. > >> > > >> > Regards, > >> > Saikat > >> > > >> > On Sat, Oct 26, 2019 at 3:11 AM Alexey Zinoviev >> > > >> > wrote: > >> > > >> > > Vote for ignite-extensions (it's more widely than ignite-connectors) > >> > > > >> > > сб, 26 окт. 2019 г. в 05:52, Saikat Maitra : > >> > > > >> > > > Hello Denis, Dmitriy > >> > > > > >> > > > Thank you for your reply. I am thinking when a new repo is created > >> that > >> > > > will not mean that the project will undergo Incubator process , Is > >> > > > this correct? > >> > > > > >> > > > We actually want to just take few of our integrations and release > >> them > >> > > > separately as part of this new git repository. We will continue to > >> keep > >> > > the > >> > > > release group name and artifact name same. > >> > > > > >> > > > I will definitely help drive the initiative to migrate our > >> integrations > >> > > > into this new Ignite Extension repo. > >> > > > > >> > > > I seek help from our community to propose new name for Ignite > >> Extension > >> > > > repository. > >> > > > > >> > > > Some ideas, I have are as follows: > >> > > > > >> > > > > >> > > >- ignite-extensions > >> > > >- ignite-sidecar > >> > > >- ignite-ext > >> > > >- ignite-connectors > >> > > > > >> > > > > >> > > > Regards, > >> > > > Saikat > >> > > > > >> > > > On Fri, Oct 25, 2019 at 4:06 PM Dmitriy Pavlov > >> > > wrote: > >> > > > > >> > > > > Hi Denis, > >> > > > > > >> > > > > any PMC member can create repository here > >> > > > > https://selfserve.apache.org/ > >> > > > > > >> > > > > We just need to select repo names in advance. > >> > > > > > >> > > > > Sincerely, > >> > > > > Dmitriy Pavlov > >> > > > > > >> > > > > пт, 25 окт. 2019 г. в 23:57, Denis Magda : > >> > > > > > >> > > > > > Saikat, sounds great. > >> > > > > > > >> > > > > > As long as you're already driving this initiative, could you > >> please > >> > > > check > >> > > > > > with ASF Infra how to put this approach in place? Will we be > >> able > >> > to > >> > > > > create > >> > > > > > several additional repositories for extensions and release them > >> as > >> > > part > >> > > > > of > >> > > > > > the Ignite project? > >> > > > > > > >> > > > > > > >> > > > > > - > >> > > > > > Denis > >> > > > > > > >> > > > > > > >> > > > > > On Thu, Oct 24, 2019 at 7:18 PM Saikat Maitra < > >> > > saikat.mai...@gmail.com > >> > > > > > >> > > > > > wrote: > >> > > > > > > >> > > > > > > Hi Denis, > >> > > > > > > > >> > > > > > > Yes, I see it now as I think more about it, I like option - > >> 0. I > >> > am > >> > > > > > > thinking from a new member and a contributor perspective for > >> > Ignite > >> > > > > > > project, I would very much like my PR and proposal to be > >> accepted > >> > > > > within > >> > > > > > > Ignite community. > >> > > > > > > > >> > > > > > > Regards, > >> > > > > > > Saikat > >> > > > > > > > >> > > > > > > > >> > > > > > > > >> > > > > > > > >> > > > > > > > >> > > > > > > On Thu, Oct 24, 2019 at 1:56 PM Denis Magda < > >> dma...@apache.org> > >> > > > wrote: > >> > > > > > > > >> > > > > > > > Exactly, Dmitry found the right word for the reason why > >> > option-0 > >> > > > > might > >> > > > > > be > >> > > > > > > > the best one - to avoid the Ignite community *split*. All > >> those > >> > > who > >> > > > > > will > >> > > > > > > be > >> > > > > > > > contributing to integrations and extensions need to be able > >> to > >> > > > earn a > >> > > > > > > > status of an Ignite committer and PMC members. Otherwise, > >> I'm > >> >
Re: [DISCUSS] Proposal for Ignite Extensions as a separate Bahir module or Incubator project
Hi Denis, I meant we can create dedicated repository for individual extensions and we can create submodules inside each specific repository for individual extensions versions. Regards, Saikat On Mon, Oct 28, 2019 at 7:14 PM Saikat Maitra wrote: > Hi Denis, > > Yes, dedicated repository is also a good idea and we can create submodules > inside each specific repository for individual extensions. > > Regards, > Saikat > > > > On Mon, Oct 28, 2019 at 2:34 PM Denis Magda wrote: > >> Folks, >> >> What do you think about having a dedicated repository for each extension >> instead of a single one? It sounds complicated but might be worthwhile for >> cases when an integration requires to support several versions. Take Spark >> or Hibernate as an example, we already provide different versions of >> Ignite >> packages for various Spark/Hibernate versions. It will be easier to handle >> if Spark or Hibernate had their own repos. >> >> - >> Denis >> >> >> On Sat, Oct 26, 2019 at 10:06 PM Saikat Maitra >> wrote: >> >> > Hello Alexey, >> > >> > Thank you for your email. Yes, I am also aligned for ignite-extensions. >> > >> > If others are also ok we can create the new repository with name >> > ignite-extensions. >> > >> > Regards, >> > Saikat >> > >> > On Sat, Oct 26, 2019 at 3:11 AM Alexey Zinoviev > > >> > wrote: >> > >> > > Vote for ignite-extensions (it's more widely than ignite-connectors) >> > > >> > > сб, 26 окт. 2019 г. в 05:52, Saikat Maitra : >> > > >> > > > Hello Denis, Dmitriy >> > > > >> > > > Thank you for your reply. I am thinking when a new repo is created >> that >> > > > will not mean that the project will undergo Incubator process , Is >> > > > this correct? >> > > > >> > > > We actually want to just take few of our integrations and release >> them >> > > > separately as part of this new git repository. We will continue to >> keep >> > > the >> > > > release group name and artifact name same. >> > > > >> > > > I will definitely help drive the initiative to migrate our >> integrations >> > > > into this new Ignite Extension repo. >> > > > >> > > > I seek help from our community to propose new name for Ignite >> Extension >> > > > repository. >> > > > >> > > > Some ideas, I have are as follows: >> > > > >> > > > >> > > >- ignite-extensions >> > > >- ignite-sidecar >> > > >- ignite-ext >> > > >- ignite-connectors >> > > > >> > > > >> > > > Regards, >> > > > Saikat >> > > > >> > > > On Fri, Oct 25, 2019 at 4:06 PM Dmitriy Pavlov >> > > wrote: >> > > > >> > > > > Hi Denis, >> > > > > >> > > > > any PMC member can create repository here >> > > > > https://selfserve.apache.org/ >> > > > > >> > > > > We just need to select repo names in advance. >> > > > > >> > > > > Sincerely, >> > > > > Dmitriy Pavlov >> > > > > >> > > > > пт, 25 окт. 2019 г. в 23:57, Denis Magda : >> > > > > >> > > > > > Saikat, sounds great. >> > > > > > >> > > > > > As long as you're already driving this initiative, could you >> please >> > > > check >> > > > > > with ASF Infra how to put this approach in place? Will we be >> able >> > to >> > > > > create >> > > > > > several additional repositories for extensions and release them >> as >> > > part >> > > > > of >> > > > > > the Ignite project? >> > > > > > >> > > > > > >> > > > > > - >> > > > > > Denis >> > > > > > >> > > > > > >> > > > > > On Thu, Oct 24, 2019 at 7:18 PM Saikat Maitra < >> > > saikat.mai...@gmail.com >> > > > > >> > > > > > wrote: >> > > > > > >> > > > > > > Hi Denis, >> > > > > > > >> > > > > > > Yes, I see it now as I think more about it, I like option - >> 0. I >> > am >> > > > > > > thinking from a new member and a contributor perspective for >> > Ignite >> > > > > > > project, I would very much like my PR and proposal to be >> accepted >> > > > > within >> > > > > > > Ignite community. >> > > > > > > >> > > > > > > Regards, >> > > > > > > Saikat >> > > > > > > >> > > > > > > >> > > > > > > >> > > > > > > >> > > > > > > >> > > > > > > On Thu, Oct 24, 2019 at 1:56 PM Denis Magda < >> dma...@apache.org> >> > > > wrote: >> > > > > > > >> > > > > > > > Exactly, Dmitry found the right word for the reason why >> > option-0 >> > > > > might >> > > > > > be >> > > > > > > > the best one - to avoid the Ignite community *split*. All >> those >> > > who >> > > > > > will >> > > > > > > be >> > > > > > > > contributing to integrations and extensions need to be able >> to >> > > > earn a >> > > > > > > > status of an Ignite committer and PMC members. Otherwise, >> I'm >> > not >> > > > > sure >> > > > > > if >> > > > > > > > Emmanouil and others to come will be fully involved in the >> > Ignite >> > > > > > > > community. >> > > > > > > > >> > > > > > > > Saikat, Emmanouil, what do you think if to look from this >> > > > > perspective? >> > > > > > > > >> > > > > > > > - >> > > > > > > > Denis >> > > > > > > > >> > > > > > > > >> > > > > > > > On Thu, Oct 24, 2019 at 12:04 AM Dmitriy Pavlov < >> > > > dpav...@apache.org> >> > > > > > > > wrote: >> > >
Re: [DISCUSS] Proposal for Ignite Extensions as a separate Bahir module or Incubator project
Hi Denis, Yes, dedicated repository is also a good idea and we can create submodules inside each specific repository for individual extensions. Regards, Saikat On Mon, Oct 28, 2019 at 2:34 PM Denis Magda wrote: > Folks, > > What do you think about having a dedicated repository for each extension > instead of a single one? It sounds complicated but might be worthwhile for > cases when an integration requires to support several versions. Take Spark > or Hibernate as an example, we already provide different versions of Ignite > packages for various Spark/Hibernate versions. It will be easier to handle > if Spark or Hibernate had their own repos. > > - > Denis > > > On Sat, Oct 26, 2019 at 10:06 PM Saikat Maitra > wrote: > > > Hello Alexey, > > > > Thank you for your email. Yes, I am also aligned for ignite-extensions. > > > > If others are also ok we can create the new repository with name > > ignite-extensions. > > > > Regards, > > Saikat > > > > On Sat, Oct 26, 2019 at 3:11 AM Alexey Zinoviev > > wrote: > > > > > Vote for ignite-extensions (it's more widely than ignite-connectors) > > > > > > сб, 26 окт. 2019 г. в 05:52, Saikat Maitra : > > > > > > > Hello Denis, Dmitriy > > > > > > > > Thank you for your reply. I am thinking when a new repo is created > that > > > > will not mean that the project will undergo Incubator process , Is > > > > this correct? > > > > > > > > We actually want to just take few of our integrations and release > them > > > > separately as part of this new git repository. We will continue to > keep > > > the > > > > release group name and artifact name same. > > > > > > > > I will definitely help drive the initiative to migrate our > integrations > > > > into this new Ignite Extension repo. > > > > > > > > I seek help from our community to propose new name for Ignite > Extension > > > > repository. > > > > > > > > Some ideas, I have are as follows: > > > > > > > > > > > >- ignite-extensions > > > >- ignite-sidecar > > > >- ignite-ext > > > >- ignite-connectors > > > > > > > > > > > > Regards, > > > > Saikat > > > > > > > > On Fri, Oct 25, 2019 at 4:06 PM Dmitriy Pavlov > > > wrote: > > > > > > > > > Hi Denis, > > > > > > > > > > any PMC member can create repository here > > > > > https://selfserve.apache.org/ > > > > > > > > > > We just need to select repo names in advance. > > > > > > > > > > Sincerely, > > > > > Dmitriy Pavlov > > > > > > > > > > пт, 25 окт. 2019 г. в 23:57, Denis Magda : > > > > > > > > > > > Saikat, sounds great. > > > > > > > > > > > > As long as you're already driving this initiative, could you > please > > > > check > > > > > > with ASF Infra how to put this approach in place? Will we be able > > to > > > > > create > > > > > > several additional repositories for extensions and release them > as > > > part > > > > > of > > > > > > the Ignite project? > > > > > > > > > > > > > > > > > > - > > > > > > Denis > > > > > > > > > > > > > > > > > > On Thu, Oct 24, 2019 at 7:18 PM Saikat Maitra < > > > saikat.mai...@gmail.com > > > > > > > > > > > wrote: > > > > > > > > > > > > > Hi Denis, > > > > > > > > > > > > > > Yes, I see it now as I think more about it, I like option - 0. > I > > am > > > > > > > thinking from a new member and a contributor perspective for > > Ignite > > > > > > > project, I would very much like my PR and proposal to be > accepted > > > > > within > > > > > > > Ignite community. > > > > > > > > > > > > > > Regards, > > > > > > > Saikat > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Thu, Oct 24, 2019 at 1:56 PM Denis Magda > > > > > wrote: > > > > > > > > > > > > > > > Exactly, Dmitry found the right word for the reason why > > option-0 > > > > > might > > > > > > be > > > > > > > > the best one - to avoid the Ignite community *split*. All > those > > > who > > > > > > will > > > > > > > be > > > > > > > > contributing to integrations and extensions need to be able > to > > > > earn a > > > > > > > > status of an Ignite committer and PMC members. Otherwise, I'm > > not > > > > > sure > > > > > > if > > > > > > > > Emmanouil and others to come will be fully involved in the > > Ignite > > > > > > > > community. > > > > > > > > > > > > > > > > Saikat, Emmanouil, what do you think if to look from this > > > > > perspective? > > > > > > > > > > > > > > > > - > > > > > > > > Denis > > > > > > > > > > > > > > > > > > > > > > > > On Thu, Oct 24, 2019 at 12:04 AM Dmitriy Pavlov < > > > > dpav...@apache.org> > > > > > > > > wrote: > > > > > > > > > > > > > > > > > Hah, IMHO, it is a story of how pushing others to place > their > > > > > > > > contribution > > > > > > > > > outside ASF could lead projects to split their communities. > > > > > > > > > > > > > > > > > > I believe, the Ignite community is more open and flexible > in > > > that > > > > > > > regard. > > > > > > > > > So Option-0. is also OK from my perspective. > > > > > > > > > > > > > > > > > > чт, 24 окт. 2019 г. в 04:01,
Re: [DISCUSS] PMC Chair rotation time
Anyone can vote to express an opinion, however, the binding votes of PMC members will be counted towards the election. - Denis On Mon, Oct 28, 2019 at 12:53 PM Petr Ivanov wrote: > Anyone can vote or only other PMCs? > > > > On 28 Oct 2019, at 20:58, Denis Magda wrote: > > > > Ignites, overall, here is a list of candidates who confirmed their > > participation in the vote. The others are either rejected or not > responded > > publicly/privately. > > > > - Alexey Goncharuk > > - Dmitry Pavlov > > - Nikolay Izhikov > > - Pavel Tupitsyn > > > > As proposed in this discussion, let's bring up the PMC rotation topic > once > > a year to see if the community is willing to give another candidate to > take > > the role. But the rotation shouldn't be obligatory if a current PMC is > > ready to carry on and the community doesn't see a need for the rotation. > > > > > > - > > Denis > > > > > > On Sat, Oct 26, 2019 at 2:22 AM Alexey Goncharuk < > alexey.goncha...@gmail.com> > > wrote: > > > >> Thanks folks, I'm in. > >> > >> пт, 25 окт. 2019 г. в 23:44, Nikolay Izhikov : > >> > >>> I'm in. > >>> > >>> В Чт, 24/10/2019 в 11:48 -0700, Denis Magda пишет: > Igniters, > > Below is a list of proposed candidates. Let's give the candidates time > until Monday to either confirm or reject their candidacy. Those who > >>> confirm > will be sent for the vote. If we don't hear back from someone by that > >>> time, > then the silence will be treated as a rejection. Keep in mind that > even > though everyone is free to cast a vote, the votes of PMC members are > counted for the Chair election: > > - Nikolay Izhikov > - Alexey Goncharuk > - Dmitry Pavlov (confirmed) > - Pavel Tupitsyn > - Roman Shtykh > - Vladimir Ozerov (thinking) > - Yakov Zhdanov > - Andrey Gura > - Anton Vinogradov (rejected) > - Denis Magda (rejected) > > On a side note. > > Vova, it's nice to hear back from you, look forward to your return to > >> the > community. I know that you're a man of honor but, please, ensure that > a > demarcation zone is set between what you do for the community and for > >>> your > current employer. We know that Ignite is competing but not > >> complementing > technology to Hazelcast and, as Ignite PMC, need to ensure that the > >>> vendor > doesn't exploit your involvement in the project anyhow harmful for > >>> Ignite. > Again, no any concerns about you, we trust you, just as advice, > discuss > >>> and > set the rules with the employer from the get-go. > > Finally, the reason why the Chair rotation was proposed and why I'm > excluding my candidacy from the list. The community is grown-up, we > >> have > excellent candidates who can serve the community as the Chair and they > >>> need > to be given a chance to drive and influence even bigger changes [1]. > As > >>> for > me, nothing changes, I'll be contributing to the community growth > >>> similarly > if not bigger. > > [1] > > >>> > >> > http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-in-2019-Status-and-Directions-td44147.html > > - > Denis > > > On Thu, Oct 24, 2019 at 6:18 AM Dmitriy Pavlov > >>> wrote: > > > Alexey Zinoviev, Igniters, sorry for topic high-jacking / side reply, > >>> but I > > have to stress one thing. > > > > Both Committers and PMC groups are not a sort of clubs, it is just > >>> roles. > > One can accept patches, another can reject a patch using veto and > > suggest/vote for new committers. > > > > There is nothing special in being PMC; and, actually, noting happens > >>> on a > > private list now. Just a couple of requests related to Apache Con. > >>> This is > > sign of a healthy community, when everything is discussed on dev > >> list, > >>> in > > public. Once private list becomes too active it is a negative thing, > >>> it is > > a sign of a disagreement. This is not a case of Ignite nowadays. > > > > Please consider both of these roles in community as recognition of > >>> merit > > and sign of trust, but not invitation into closed/private club. > > > > A bit of info related to PMC and VP: > > https://www.apache.org/foundation/governance/pmcs.html#legal > > > > Sincerely, > > Dmitriy Pavlov > > > > чт, 24 окт. 2019 г. в 13:18, Ivan Pavlukhin : > > > >> Hi Vova, > >> > >> Glad to hear from you. I hope that we will hear from you soon about > >> Hazelnite (Igncast?) independently whether you become Ignite PMC > >>> Chair > >> or not. > >> > >> чт, 24 окт. 2019 г. в 11:49, Anton Vinogradov : > >>> > >>> Vova, > >>> +1 to your candidacy. > >>> Just say yes. > >>> > >>> As for me, huge thanks for the proposal but being PMC Member > >>>
Re: [DISCUSS] PMC Chair rotation time
Anyone can vote or only other PMCs? > On 28 Oct 2019, at 20:58, Denis Magda wrote: > > Ignites, overall, here is a list of candidates who confirmed their > participation in the vote. The others are either rejected or not responded > publicly/privately. > > - Alexey Goncharuk > - Dmitry Pavlov > - Nikolay Izhikov > - Pavel Tupitsyn > > As proposed in this discussion, let's bring up the PMC rotation topic once > a year to see if the community is willing to give another candidate to take > the role. But the rotation shouldn't be obligatory if a current PMC is > ready to carry on and the community doesn't see a need for the rotation. > > > - > Denis > > > On Sat, Oct 26, 2019 at 2:22 AM Alexey Goncharuk > wrote: > >> Thanks folks, I'm in. >> >> пт, 25 окт. 2019 г. в 23:44, Nikolay Izhikov : >> >>> I'm in. >>> >>> В Чт, 24/10/2019 в 11:48 -0700, Denis Magda пишет: Igniters, Below is a list of proposed candidates. Let's give the candidates time until Monday to either confirm or reject their candidacy. Those who >>> confirm will be sent for the vote. If we don't hear back from someone by that >>> time, then the silence will be treated as a rejection. Keep in mind that even though everyone is free to cast a vote, the votes of PMC members are counted for the Chair election: - Nikolay Izhikov - Alexey Goncharuk - Dmitry Pavlov (confirmed) - Pavel Tupitsyn - Roman Shtykh - Vladimir Ozerov (thinking) - Yakov Zhdanov - Andrey Gura - Anton Vinogradov (rejected) - Denis Magda (rejected) On a side note. Vova, it's nice to hear back from you, look forward to your return to >> the community. I know that you're a man of honor but, please, ensure that a demarcation zone is set between what you do for the community and for >>> your current employer. We know that Ignite is competing but not >> complementing technology to Hazelcast and, as Ignite PMC, need to ensure that the >>> vendor doesn't exploit your involvement in the project anyhow harmful for >>> Ignite. Again, no any concerns about you, we trust you, just as advice, discuss >>> and set the rules with the employer from the get-go. Finally, the reason why the Chair rotation was proposed and why I'm excluding my candidacy from the list. The community is grown-up, we >> have excellent candidates who can serve the community as the Chair and they >>> need to be given a chance to drive and influence even bigger changes [1]. As >>> for me, nothing changes, I'll be contributing to the community growth >>> similarly if not bigger. [1] >>> >> http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-in-2019-Status-and-Directions-td44147.html - Denis On Thu, Oct 24, 2019 at 6:18 AM Dmitriy Pavlov >>> wrote: > Alexey Zinoviev, Igniters, sorry for topic high-jacking / side reply, >>> but I > have to stress one thing. > > Both Committers and PMC groups are not a sort of clubs, it is just >>> roles. > One can accept patches, another can reject a patch using veto and > suggest/vote for new committers. > > There is nothing special in being PMC; and, actually, noting happens >>> on a > private list now. Just a couple of requests related to Apache Con. >>> This is > sign of a healthy community, when everything is discussed on dev >> list, >>> in > public. Once private list becomes too active it is a negative thing, >>> it is > a sign of a disagreement. This is not a case of Ignite nowadays. > > Please consider both of these roles in community as recognition of >>> merit > and sign of trust, but not invitation into closed/private club. > > A bit of info related to PMC and VP: > https://www.apache.org/foundation/governance/pmcs.html#legal > > Sincerely, > Dmitriy Pavlov > > чт, 24 окт. 2019 г. в 13:18, Ivan Pavlukhin : > >> Hi Vova, >> >> Glad to hear from you. I hope that we will hear from you soon about >> Hazelnite (Igncast?) independently whether you become Ignite PMC >>> Chair >> or not. >> >> чт, 24 окт. 2019 г. в 11:49, Anton Vinogradov : >>> >>> Vova, >>> +1 to your candidacy. >>> Just say yes. >>> >>> As for me, huge thanks for the proposal but being PMC Member >>> currently >>> enough for me :) >>> >>> On Thu, Oct 24, 2019 at 11:21 AM Dmitriy Pavlov < >>> dpav...@apache.org> >> >> wrote: >>> Vova, I will vote for your candidacy as well. Your candidacy >>> came for >> >> 2nd time (I've checked previous thread). This is a good sign that we should think about you serving as >>> Chair. чт, 24 окт. 2019 г. в 11:16, Vladimir Ozerov < >> ppoze...@gmail.com
[jira] [Created] (IGNITE-12334) Throttle getAll operations on the grid
ABHISHEK SHUBH GUPTA created IGNITE-12334: - Summary: Throttle getAll operations on the grid Key: IGNITE-12334 URL: https://issues.apache.org/jira/browse/IGNITE-12334 Project: Ignite Issue Type: Improvement Affects Versions: 2.7.5 Reporter: ABHISHEK SHUBH GUPTA Per [this thread|http://apache-ignite-users.70518.x6.nabble.com/Throttling-getAll-tt29956.html], in a situation where a large number of keys are requested using getAll and/or the value objects are large, there is a worry about GC issues/humongous objects/OOM on the grid. It would, therefore, be beneficial to the stability of the product if there was throttling available on the ignition nodes when clients do large getAll operations. The throttling could perhaps be based on the number of keys passed on to getAll. If it exceeds threshold it could reject the request or optionally, auto-create multiple smaller batches. -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: [DISCUSS] Proposal for Ignite Extensions as a separate Bahir module or Incubator project
Folks, What do you think about having a dedicated repository for each extension instead of a single one? It sounds complicated but might be worthwhile for cases when an integration requires to support several versions. Take Spark or Hibernate as an example, we already provide different versions of Ignite packages for various Spark/Hibernate versions. It will be easier to handle if Spark or Hibernate had their own repos. - Denis On Sat, Oct 26, 2019 at 10:06 PM Saikat Maitra wrote: > Hello Alexey, > > Thank you for your email. Yes, I am also aligned for ignite-extensions. > > If others are also ok we can create the new repository with name > ignite-extensions. > > Regards, > Saikat > > On Sat, Oct 26, 2019 at 3:11 AM Alexey Zinoviev > wrote: > > > Vote for ignite-extensions (it's more widely than ignite-connectors) > > > > сб, 26 окт. 2019 г. в 05:52, Saikat Maitra : > > > > > Hello Denis, Dmitriy > > > > > > Thank you for your reply. I am thinking when a new repo is created that > > > will not mean that the project will undergo Incubator process , Is > > > this correct? > > > > > > We actually want to just take few of our integrations and release them > > > separately as part of this new git repository. We will continue to keep > > the > > > release group name and artifact name same. > > > > > > I will definitely help drive the initiative to migrate our integrations > > > into this new Ignite Extension repo. > > > > > > I seek help from our community to propose new name for Ignite Extension > > > repository. > > > > > > Some ideas, I have are as follows: > > > > > > > > >- ignite-extensions > > >- ignite-sidecar > > >- ignite-ext > > >- ignite-connectors > > > > > > > > > Regards, > > > Saikat > > > > > > On Fri, Oct 25, 2019 at 4:06 PM Dmitriy Pavlov > > wrote: > > > > > > > Hi Denis, > > > > > > > > any PMC member can create repository here > > > > https://selfserve.apache.org/ > > > > > > > > We just need to select repo names in advance. > > > > > > > > Sincerely, > > > > Dmitriy Pavlov > > > > > > > > пт, 25 окт. 2019 г. в 23:57, Denis Magda : > > > > > > > > > Saikat, sounds great. > > > > > > > > > > As long as you're already driving this initiative, could you please > > > check > > > > > with ASF Infra how to put this approach in place? Will we be able > to > > > > create > > > > > several additional repositories for extensions and release them as > > part > > > > of > > > > > the Ignite project? > > > > > > > > > > > > > > > - > > > > > Denis > > > > > > > > > > > > > > > On Thu, Oct 24, 2019 at 7:18 PM Saikat Maitra < > > saikat.mai...@gmail.com > > > > > > > > > wrote: > > > > > > > > > > > Hi Denis, > > > > > > > > > > > > Yes, I see it now as I think more about it, I like option - 0. I > am > > > > > > thinking from a new member and a contributor perspective for > Ignite > > > > > > project, I would very much like my PR and proposal to be accepted > > > > within > > > > > > Ignite community. > > > > > > > > > > > > Regards, > > > > > > Saikat > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Thu, Oct 24, 2019 at 1:56 PM Denis Magda > > > wrote: > > > > > > > > > > > > > Exactly, Dmitry found the right word for the reason why > option-0 > > > > might > > > > > be > > > > > > > the best one - to avoid the Ignite community *split*. All those > > who > > > > > will > > > > > > be > > > > > > > contributing to integrations and extensions need to be able to > > > earn a > > > > > > > status of an Ignite committer and PMC members. Otherwise, I'm > not > > > > sure > > > > > if > > > > > > > Emmanouil and others to come will be fully involved in the > Ignite > > > > > > > community. > > > > > > > > > > > > > > Saikat, Emmanouil, what do you think if to look from this > > > > perspective? > > > > > > > > > > > > > > - > > > > > > > Denis > > > > > > > > > > > > > > > > > > > > > On Thu, Oct 24, 2019 at 12:04 AM Dmitriy Pavlov < > > > dpav...@apache.org> > > > > > > > wrote: > > > > > > > > > > > > > > > Hah, IMHO, it is a story of how pushing others to place their > > > > > > > contribution > > > > > > > > outside ASF could lead projects to split their communities. > > > > > > > > > > > > > > > > I believe, the Ignite community is more open and flexible in > > that > > > > > > regard. > > > > > > > > So Option-0. is also OK from my perspective. > > > > > > > > > > > > > > > > чт, 24 окт. 2019 г. в 04:01, Saikat Maitra < > > > > saikat.mai...@gmail.com > > > > > >: > > > > > > > > > > > > > > > > > Hi, > > > > > > > > > > > > > > > > > > I looked into the way Apache Bahir manages their extensions > > for > > > > > Spark > > > > > > > and > > > > > > > > > Flink and it looks like they are much independent in terms > of > > > > > > managing > > > > > > > > > their releases. They also have separate git repos for > apache > > > > bahir > > > > > > and > > > > > > > > > apache bahir-flink. > > > > > > > > > > > > > > > > > > Releases : > > > > > > > > >
RE: [VOTE] Apache Ignite PMC Chair
+ 1 Dmitry Pavlov > On Mon, Oct 28, 2019 at 9:07 PM Denis Magda wrote: > > > > +1 for Nikolay Izhikov (binding) > > > > - > > Denis > > > > > > On Mon, Oct 28, 2019 at 11:06 AM Denis Magda wrote: > > > > > Ignite community, > > > > > > Please cast a vote for one of the following candidates: > > > > > >- Alexey Goncharuk > > >- Dmitry Pavlov > > >- Nikolay Izhikov > > >- Pavel Tupitsyn > > > > > > Everybody is encouraged to take part in the vote, however, > > > remember that only the binding votes of PMC members result in the > > > Chair election. The candidates can vote for themselves. The vote > > > will end on November 1st, > > > 11:00 AM Pacific Time. More details about the next steps are here: > > > https://www.apache.org/dev/pmc.html#newchair > > > > > > - > > > Denis > > > -- Best regards, Ivan Pavlukhin This E-Mail (including any attachments) may contain privileged or confidential information. It is intended only for the addressee(s) indicated above. The sender does not waive any of its rights, privileges or other protections respecting this information. Any distribution, copying or other use of this E-Mail or the information it contains, by other than an intended recipient, is not sanctioned and is prohibited. If you received this E-Mail in error, please delete it and advise the sender (by return E-Mail or otherwise) immediately. This E-Mail (including any attachments) has been scanned for viruses. It is believed to be free of any virus or other defect that might affect any computer system into which it is received and opened. However, it is the responsibility of the recipient to ensure that it is virus free. The sender accepts no responsibility for any loss or damage arising in any way from its use. E-Mail received by or sent from RBC Capital Markets is subject to review by Supervisory personnel. Such communications are retained and may be produced to regulatory authorities or others with legal rights to the information. IRS CIRCULAR 230 NOTICE: TO COMPLY WITH U.S. TREASURY REGULATIONS, WE ADVISE YOU THAT ANY U.S. FEDERAL TAX ADVICE INCLUDED IN THIS COMMUNICATION IS NOT INTENDED OR WRITTEN TO BE USED, AND CANNOT BE USED, TO AVOID ANY U.S. FEDERAL TAX PENALTIES OR TO PROMOTE, MARKET, OR RECOMMEND TO ANOTHER PARTY ANY TRANSACTION OR MATTER.
Re: [VOTE] Apache Ignite PMC Chair
+ 1 Dmitry Pavlov пн, 28 окт. 2019 г. в 21:13, Andrey Gura : > > +1 for Alexey Goncharuk (binding) > > On Mon, Oct 28, 2019 at 9:07 PM Denis Magda wrote: > > > > +1 for Nikolay Izhikov (binding) > > > > - > > Denis > > > > > > On Mon, Oct 28, 2019 at 11:06 AM Denis Magda wrote: > > > > > Ignite community, > > > > > > Please cast a vote for one of the following candidates: > > > > > >- Alexey Goncharuk > > >- Dmitry Pavlov > > >- Nikolay Izhikov > > >- Pavel Tupitsyn > > > > > > Everybody is encouraged to take part in the vote, however, remember that > > > only the binding votes of PMC members result in the Chair election. The > > > candidates can vote for themselves. The vote will end on November 1st, > > > 11:00 AM Pacific Time. More details about the next steps are here: > > > https://www.apache.org/dev/pmc.html#newchair > > > > > > - > > > Denis > > > -- Best regards, Ivan Pavlukhin
Re: JTS license
Thanks for the guide, I'll check them and create the ticket. El lun., 28 oct. 2019 a las 10:12, Nikolay Izhikov () escribió: > Hello, Fernando. > > First of all, thank you for your interest in Apache Ignite. > > > how can I contribute to improve geospatial support and indexing? > > Just create a ticket and discuss the changes on the dev-list. > > Here are some links you can find usefull: > > * https://ignite.apache.org/community/contribute.html > * https://cwiki.apache.org/confluence/display/IGNITE/Development+Process > * https://cwiki.apache.org/confluence/display/IGNITE/Coding+Guidelines > > > В Пн, 28/10/2019 в 09:59 -0500, Fernando Miño пишет: > > Hi all, > > > > Just checking for some spatial features on Apache Ignite I saw this > > document: > > https://apacheignite-sql.readme.io/docs/geospatial-support > > > > Here says JTS is LGPL licenced, but current JTS development is now part > of > > Eclipse LocationTech project, and is now Eclipse Licensed, so I'm > > wondering, with Eclipse license can JTS be included on Ignite delivery in > > future releases (maybe upgrading lib version to last and refactoring to > > updated packages naming)? > > > > New JTS home: > > https://github.com/locationtech/jts > > > > Also how can I contribute to improve geospatial support and indexing? > > > > Thanks and regards. > > > -- Fernando Miño 0989715618 Skype: fernando.mino777 La ciencia es el alma de la prosperidad de las naciones y la fuente de vida de todo progreso. *Louis Pasteur*
Re: [VOTE] Apache Ignite PMC Chair
+1 for Alexey Goncharuk (binding) On Mon, Oct 28, 2019 at 9:07 PM Denis Magda wrote: > > +1 for Nikolay Izhikov (binding) > > - > Denis > > > On Mon, Oct 28, 2019 at 11:06 AM Denis Magda wrote: > > > Ignite community, > > > > Please cast a vote for one of the following candidates: > > > >- Alexey Goncharuk > >- Dmitry Pavlov > >- Nikolay Izhikov > >- Pavel Tupitsyn > > > > Everybody is encouraged to take part in the vote, however, remember that > > only the binding votes of PMC members result in the Chair election. The > > candidates can vote for themselves. The vote will end on November 1st, > > 11:00 AM Pacific Time. More details about the next steps are here: > > https://www.apache.org/dev/pmc.html#newchair > > > > - > > Denis > >
Re: [VOTE] Apache Ignite PMC Chair
+1 for Nikolay Izhikov (binding) - Denis On Mon, Oct 28, 2019 at 11:06 AM Denis Magda wrote: > Ignite community, > > Please cast a vote for one of the following candidates: > >- Alexey Goncharuk >- Dmitry Pavlov >- Nikolay Izhikov >- Pavel Tupitsyn > > Everybody is encouraged to take part in the vote, however, remember that > only the binding votes of PMC members result in the Chair election. The > candidates can vote for themselves. The vote will end on November 1st, > 11:00 AM Pacific Time. More details about the next steps are here: > https://www.apache.org/dev/pmc.html#newchair > > - > Denis >
[VOTE] Apache Ignite PMC Chair
Ignite community, Please cast a vote for one of the following candidates: - Alexey Goncharuk - Dmitry Pavlov - Nikolay Izhikov - Pavel Tupitsyn Everybody is encouraged to take part in the vote, however, remember that only the binding votes of PMC members result in the Chair election. The candidates can vote for themselves. The vote will end on November 1st, 11:00 AM Pacific Time. More details about the next steps are here: https://www.apache.org/dev/pmc.html#newchair - Denis
Re: JTS license
Hi, good to know, I'll try to start contributing with this, thanks! El lun., 28 oct. 2019 a las 11:06, Ilya Kasnacheev (< ilya.kasnach...@gmail.com>) escribió: > Hello! > > I believe we already use org.locationtech for Geometry. > > Maybe we should move this module from lgpl to common. You can try > contributing here. > > Regards, > -- > Ilya Kasnacheev > > > пн, 28 окт. 2019 г. в 18:12, Nikolay Izhikov : > > > Hello, Fernando. > > > > First of all, thank you for your interest in Apache Ignite. > > > > > how can I contribute to improve geospatial support and indexing? > > > > Just create a ticket and discuss the changes on the dev-list. > > > > Here are some links you can find usefull: > > > > * https://ignite.apache.org/community/contribute.html > > * https://cwiki.apache.org/confluence/display/IGNITE/Development+Process > > * https://cwiki.apache.org/confluence/display/IGNITE/Coding+Guidelines > > > > > > В Пн, 28/10/2019 в 09:59 -0500, Fernando Miño пишет: > > > Hi all, > > > > > > Just checking for some spatial features on Apache Ignite I saw this > > > document: > > > https://apacheignite-sql.readme.io/docs/geospatial-support > > > > > > Here says JTS is LGPL licenced, but current JTS development is now part > > of > > > Eclipse LocationTech project, and is now Eclipse Licensed, so I'm > > > wondering, with Eclipse license can JTS be included on Ignite delivery > in > > > future releases (maybe upgrading lib version to last and refactoring to > > > updated packages naming)? > > > > > > New JTS home: > > > https://github.com/locationtech/jts > > > > > > Also how can I contribute to improve geospatial support and indexing? > > > > > > Thanks and regards. > > > > > > -- Fernando Miño 0989715618 Skype: fernando.mino777 La ciencia es el alma de la prosperidad de las naciones y la fuente de vida de todo progreso. *Louis Pasteur*
Re: [DISCUSS] PMC Chair rotation time
Ignites, overall, here is a list of candidates who confirmed their participation in the vote. The others are either rejected or not responded publicly/privately. - Alexey Goncharuk - Dmitry Pavlov - Nikolay Izhikov - Pavel Tupitsyn As proposed in this discussion, let's bring up the PMC rotation topic once a year to see if the community is willing to give another candidate to take the role. But the rotation shouldn't be obligatory if a current PMC is ready to carry on and the community doesn't see a need for the rotation. - Denis On Sat, Oct 26, 2019 at 2:22 AM Alexey Goncharuk wrote: > Thanks folks, I'm in. > > пт, 25 окт. 2019 г. в 23:44, Nikolay Izhikov : > > > I'm in. > > > > В Чт, 24/10/2019 в 11:48 -0700, Denis Magda пишет: > > > Igniters, > > > > > > Below is a list of proposed candidates. Let's give the candidates time > > > until Monday to either confirm or reject their candidacy. Those who > > confirm > > > will be sent for the vote. If we don't hear back from someone by that > > time, > > > then the silence will be treated as a rejection. Keep in mind that even > > > though everyone is free to cast a vote, the votes of PMC members are > > > counted for the Chair election: > > > > > >- Nikolay Izhikov > > >- Alexey Goncharuk > > >- Dmitry Pavlov (confirmed) > > >- Pavel Tupitsyn > > >- Roman Shtykh > > >- Vladimir Ozerov (thinking) > > >- Yakov Zhdanov > > >- Andrey Gura > > >- Anton Vinogradov (rejected) > > >- Denis Magda (rejected) > > > > > > On a side note. > > > > > > Vova, it's nice to hear back from you, look forward to your return to > the > > > community. I know that you're a man of honor but, please, ensure that a > > > demarcation zone is set between what you do for the community and for > > your > > > current employer. We know that Ignite is competing but not > complementing > > > technology to Hazelcast and, as Ignite PMC, need to ensure that the > > vendor > > > doesn't exploit your involvement in the project anyhow harmful for > > Ignite. > > > Again, no any concerns about you, we trust you, just as advice, discuss > > and > > > set the rules with the employer from the get-go. > > > > > > Finally, the reason why the Chair rotation was proposed and why I'm > > > excluding my candidacy from the list. The community is grown-up, we > have > > > excellent candidates who can serve the community as the Chair and they > > need > > > to be given a chance to drive and influence even bigger changes [1]. As > > for > > > me, nothing changes, I'll be contributing to the community growth > > similarly > > > if not bigger. > > > > > > [1] > > > > > > http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-in-2019-Status-and-Directions-td44147.html > > > > > > - > > > Denis > > > > > > > > > On Thu, Oct 24, 2019 at 6:18 AM Dmitriy Pavlov > > wrote: > > > > > > > Alexey Zinoviev, Igniters, sorry for topic high-jacking / side reply, > > but I > > > > have to stress one thing. > > > > > > > > Both Committers and PMC groups are not a sort of clubs, it is just > > roles. > > > > One can accept patches, another can reject a patch using veto and > > > > suggest/vote for new committers. > > > > > > > > There is nothing special in being PMC; and, actually, noting happens > > on a > > > > private list now. Just a couple of requests related to Apache Con. > > This is > > > > sign of a healthy community, when everything is discussed on dev > list, > > in > > > > public. Once private list becomes too active it is a negative thing, > > it is > > > > a sign of a disagreement. This is not a case of Ignite nowadays. > > > > > > > > Please consider both of these roles in community as recognition of > > merit > > > > and sign of trust, but not invitation into closed/private club. > > > > > > > > A bit of info related to PMC and VP: > > > > https://www.apache.org/foundation/governance/pmcs.html#legal > > > > > > > > Sincerely, > > > > Dmitriy Pavlov > > > > > > > > чт, 24 окт. 2019 г. в 13:18, Ivan Pavlukhin : > > > > > > > > > Hi Vova, > > > > > > > > > > Glad to hear from you. I hope that we will hear from you soon about > > > > > Hazelnite (Igncast?) independently whether you become Ignite PMC > > Chair > > > > > or not. > > > > > > > > > > чт, 24 окт. 2019 г. в 11:49, Anton Vinogradov : > > > > > > > > > > > > Vova, > > > > > > +1 to your candidacy. > > > > > > Just say yes. > > > > > > > > > > > > As for me, huge thanks for the proposal but being PMC Member > > currently > > > > > > enough for me :) > > > > > > > > > > > > On Thu, Oct 24, 2019 at 11:21 AM Dmitriy Pavlov < > > dpav...@apache.org> > > > > > > > > > > wrote: > > > > > > > > > > > > > Vova, I will vote for your candidacy as well. Your candidacy > > came for > > > > > > > > > > 2nd > > > > > > > time (I've checked previous thread). > > > > > > > This is a good sign that we should think about you serving as > > Chair. > > > > > > > > > > > > > > чт, 24 окт. 2019 г. в 11:16, Vladimir
[jira] [Created] (IGNITE-12333) [ML] Cleanup the ML module code
Alexey Zinoviev created IGNITE-12333: Summary: [ML] Cleanup the ML module code Key: IGNITE-12333 URL: https://issues.apache.org/jira/browse/IGNITE-12333 Project: Ignite Issue Type: Improvement Components: ml Affects Versions: 2.8 Reporter: Alexey Zinoviev Assignee: Alexey Zinoviev Fix For: 2.8 # Formatting # Abbreviation # Codestyle # Missed JavaDocs -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: JTS license
Hello! I believe we already use org.locationtech for Geometry. Maybe we should move this module from lgpl to common. You can try contributing here. Regards, -- Ilya Kasnacheev пн, 28 окт. 2019 г. в 18:12, Nikolay Izhikov : > Hello, Fernando. > > First of all, thank you for your interest in Apache Ignite. > > > how can I contribute to improve geospatial support and indexing? > > Just create a ticket and discuss the changes on the dev-list. > > Here are some links you can find usefull: > > * https://ignite.apache.org/community/contribute.html > * https://cwiki.apache.org/confluence/display/IGNITE/Development+Process > * https://cwiki.apache.org/confluence/display/IGNITE/Coding+Guidelines > > > В Пн, 28/10/2019 в 09:59 -0500, Fernando Miño пишет: > > Hi all, > > > > Just checking for some spatial features on Apache Ignite I saw this > > document: > > https://apacheignite-sql.readme.io/docs/geospatial-support > > > > Here says JTS is LGPL licenced, but current JTS development is now part > of > > Eclipse LocationTech project, and is now Eclipse Licensed, so I'm > > wondering, with Eclipse license can JTS be included on Ignite delivery in > > future releases (maybe upgrading lib version to last and refactoring to > > updated packages naming)? > > > > New JTS home: > > https://github.com/locationtech/jts > > > > Also how can I contribute to improve geospatial support and indexing? > > > > Thanks and regards. > > >
[jira] [Created] (IGNITE-12332) Fix flaky test GridCacheAtomicClientInvalidPartitionHandlingSelfTest#testPrimaryFullAsync
Alexei Scherbakov created IGNITE-12332: -- Summary: Fix flaky test GridCacheAtomicClientInvalidPartitionHandlingSelfTest#testPrimaryFullAsync Key: IGNITE-12332 URL: https://issues.apache.org/jira/browse/IGNITE-12332 Project: Ignite Issue Type: Bug Affects Versions: 2.7.6 Reporter: Alexei Scherbakov Fix For: 2.8 Can be reproduced locally with range = 10_000 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12331) [ML] ML Preprocessing doesn't work on SQL Tables
Alexey Zinoviev created IGNITE-12331:
Summary: [ML] ML Preprocessing doesn't work on SQL Tables
Key: IGNITE-12331
URL: https://issues.apache.org/jira/browse/IGNITE-12331
Project: Ignite
Issue Type: Bug
Components: ml
Reporter: Alexey Zinoviev
Assignee: Alexey Zinoviev
{code:java}
/*
* Licensed to the Apache Software Foundation (ASF) under one or more
* contributor license agreements. See the NOTICE file distributed with
* this work for additional information regarding copyright ownership.
* The ASF licenses this file to You under the Apache License, Version 2.0
* (the "License"); you may not use this file except in compliance with
* the License. You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*/
package org.apache.ignite.examples.ml.tutorial.sql;
import java.util.List;
import org.apache.ignite.Ignite;
import org.apache.ignite.IgniteCache;
import org.apache.ignite.Ignition;
import org.apache.ignite.cache.query.QueryCursor;
import org.apache.ignite.cache.query.SqlFieldsQuery;
import org.apache.ignite.configuration.CacheConfiguration;
import org.apache.ignite.internal.util.IgniteUtils;
import org.apache.ignite.ml.dataset.feature.extractor.Vectorizer;
import
org.apache.ignite.ml.dataset.feature.extractor.impl.BinaryObjectVectorizer;
import org.apache.ignite.ml.math.primitives.vector.Vector;
import org.apache.ignite.ml.math.primitives.vector.VectorUtils;
import org.apache.ignite.ml.preprocessing.Preprocessor;
import org.apache.ignite.ml.preprocessing.minmaxscaling.MinMaxScalerTrainer;
import org.apache.ignite.ml.preprocessing.normalization.NormalizationTrainer;
import org.apache.ignite.ml.sql.SqlDatasetBuilder;
import org.apache.ignite.ml.tree.DecisionTreeClassificationTrainer;
import org.apache.ignite.ml.tree.DecisionTreeNode;
/**
* Example of using distributed {@link DecisionTreeClassificationTrainer} on a
data stored in SQL table.
*/
public class PreprocessingAndTrainingSQLTableExample {
/**
* Dummy cache name.
*/
private static final String DUMMY_CACHE_NAME = "dummy_cache";
/**
* Training data.
*/
private static final String TRAIN_DATA_RES =
"examples/src/main/resources/datasets/titanic_train.csv";
/**
* Test data.
*/
private static final String TEST_DATA_RES =
"examples/src/main/resources/datasets/titanic_test.csv";
/**
* Run example.
*/
public static void main(String[] args) {
System.out.println(">>> Decision tree classification trainer example
started.");
// Start ignite grid.
try (Ignite ignite =
Ignition.start("examples/config/example-ignite.xml")) {
System.out.println(">>> Ignite grid started.");
// Dummy cache is required to perform SQL queries.
CacheConfiguration cacheCfg = new
CacheConfiguration<>(DUMMY_CACHE_NAME)
.setSqlSchema("PUBLIC");
IgniteCache cache = null;
try {
cache = ignite.getOrCreateCache(cacheCfg);
System.out.println(">>> Creating table with training data...");
cache.query(new SqlFieldsQuery("create table titanic_train (\n"
+
"passengerid int primary key,\n" +
"survived int,\n" +
"pclass int,\n" +
"name varchar(255),\n" +
"sex varchar(255),\n" +
"age float,\n" +
"sibsp int,\n" +
"parch int,\n" +
"ticket varchar(255),\n" +
"fare float,\n" +
"cabin varchar(255),\n" +
"embarked varchar(255)\n" +
") with \"template=partitioned\";")).getAll();
System.out.println(">>> Filling training data...");
cache.query(new SqlFieldsQuery("insert into titanic_train
select * from csvread('" +
IgniteUtils.resolveIgnitePath(TRAIN_DATA_RES).getAbsolutePath() +
"')")).getAll();
System.out.println(">>> Creating table with test data...");
cache.query(new SqlFieldsQuery("create table titanic_test (\n" +
"passengerid int primary key,\n" +
"pclass int,\n" +
"name varchar(255),\n" +
"sex varchar(255),\n" +
"age float,\n" +
"sibsp
Re: JTS license
Hello, Fernando. First of all, thank you for your interest in Apache Ignite. > how can I contribute to improve geospatial support and indexing? Just create a ticket and discuss the changes on the dev-list. Here are some links you can find usefull: * https://ignite.apache.org/community/contribute.html * https://cwiki.apache.org/confluence/display/IGNITE/Development+Process * https://cwiki.apache.org/confluence/display/IGNITE/Coding+Guidelines В Пн, 28/10/2019 в 09:59 -0500, Fernando Miño пишет: > Hi all, > > Just checking for some spatial features on Apache Ignite I saw this > document: > https://apacheignite-sql.readme.io/docs/geospatial-support > > Here says JTS is LGPL licenced, but current JTS development is now part of > Eclipse LocationTech project, and is now Eclipse Licensed, so I'm > wondering, with Eclipse license can JTS be included on Ignite delivery in > future releases (maybe upgrading lib version to last and refactoring to > updated packages naming)? > > New JTS home: > https://github.com/locationtech/jts > > Also how can I contribute to improve geospatial support and indexing? > > Thanks and regards. > signature.asc Description: This is a digitally signed message part
JTS license
Hi all, Just checking for some spatial features on Apache Ignite I saw this document: https://apacheignite-sql.readme.io/docs/geospatial-support Here says JTS is LGPL licenced, but current JTS development is now part of Eclipse LocationTech project, and is now Eclipse Licensed, so I'm wondering, with Eclipse license can JTS be included on Ignite delivery in future releases (maybe upgrading lib version to last and refactoring to updated packages naming)? New JTS home: https://github.com/locationtech/jts Also how can I contribute to improve geospatial support and indexing? Thanks and regards. -- Fernando Miño Github: fernandor777 Skype: fernando.mino777 La ciencia es el alma de la prosperidad de las naciones y la fuente de vida de todo progreso. *Louis Pasteur*
[jira] [Created] (IGNITE-12330) Assertion error in CachedDeploymentInfo
Nikolay Izhikov created IGNITE-12330:
Summary: Assertion error in CachedDeploymentInfo
Key: IGNITE-12330
URL: https://issues.apache.org/jira/browse/IGNITE-12330
Project: Ignite
Issue Type: Bug
Affects Versions: 2.7.6
Reporter: Nikolay Izhikov
Assignee: Nikolay Izhikov
Fix For: 2.8
The following exception occured on some production environment.
It leads to the node fail.
{noformat}
2019-09-17
18:29:29.890[ERROR][query-#1577440%DPL_GRID%DplGridNodeName%][o.a.i.i.p.cache.GridCacheIoManager]
Failed to process message [senderId=4c071d12-325a-4bb1-a68d-cc910f636562,
msg=GridCacheQueryRequest [id=4922,
cacheName=com.sbt.limits.data.entity.LimitTemplateV1Entity_DPL_union-module,
type=SCAN, fields=false, clause=null, clsName=null, keyValFilter=null,
rdc=null, trans=null, pageSize=1024, incBackups=false, cancel=false,
incMeta=false, all=false, keepBinary=true,
subjId=4c071d12-325a-4bb1-a68d-cc910f636562, taskHash=0, part=-1,
topVer=AffinityTopologyVersion [topVer=191, minorTopVer=0],
super=GridCacheIdMessage [cacheId=-724666788]]]2019-09-17
18:29:29.890[ERROR][query-#1577440%DPL_GRID%DplGridNodeName%][o.a.i.i.p.cache.GridCacheIoManager]
Failed to process message [senderId=4c071d12-325a-4bb1-a68d-cc910f636562,
msg=GridCacheQueryRequest [id=4922,
cacheName=com.sbt.limits.data.entity.LimitTemplateV1Entity_DPL_union-module,
type=SCAN, fields=false, clause=null, clsName=null, keyValFilter=null,
rdc=null, trans=null, pageSize=1024, incBackups=false, cancel=false,
incMeta=false, all=false, keepBinary=true,
subjId=4c071d12-325a-4bb1-a68d-cc910f636562, taskHash=0, part=-1,
topVer=AffinityTopologyVersion [topVer=191, minorTopVer=0],
super=GridCacheIdMessage [cacheId=-724666788]]]
java.lang.AssertionError: null
at
org.apache.ignite.internal.processors.cache.GridCacheDeploymentManager$CachedDeploymentInfo.(GridCacheDeploymentManager.java:918)
at
org.apache.ignite.internal.processors.cache.GridCacheDeploymentManager$CachedDeploymentInfo.(GridCacheDeploymentManager.java:889)
at
org.apache.ignite.internal.processors.cache.GridCacheDeploymentManager.p2pContext(GridCacheDeploymentManager.java:422)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.unmarshall(GridCacheIoManager.java:1547)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:582)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:386)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:312)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:102)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:301)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1556)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1184)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:125)
at
org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1091)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
2019-09-17
18:29:29.912[ERROR][query-#1577440%DPL_GRID%DplGridNodeName%][org.apache.ignite.Ignite]
Critical system error detected. Will be handled accordingly to configured
handler [hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0,
super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet
[SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]],
failureCtx=FailureContext [type=CRITICAL_ERROR, err=java.lang.AssertionError]]
java.lang.AssertionError: null
at
org.apache.ignite.internal.processors.cache.GridCacheDeploymentManager$CachedDeploymentInfo.(GridCacheDeploymentManager.java:918)
at
org.apache.ignite.internal.processors.cache.GridCacheDeploymentManager$CachedDeploymentInfo.(GridCacheDeploymentManager.java:889)
at
org.apache.ignite.internal.processors.cache.GridCacheDeploymentManager.p2pContext(GridCacheDeploymentManager.java:422)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.unmarshall(GridCacheIoManager.java:1547)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:582)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:386)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:312)
at
[jira] [Created] (IGNITE-12329) Invalid handling of remote entries causes partition desync and transaction hanging in COMMITTING state.
Alexei Scherbakov created IGNITE-12329: -- Summary: Invalid handling of remote entries causes partition desync and transaction hanging in COMMITTING state. Key: IGNITE-12329 URL: https://issues.apache.org/jira/browse/IGNITE-12329 Project: Ignite Issue Type: Bug Affects Versions: 2.7.6 Reporter: Alexei Scherbakov Assignee: Alexei Scherbakov Fix For: 2.8 This can happen if transaction is mapped on a partition which is about to be evicted on backup. Due to bugs entry belonging to other cache may be excluded from commit or entry containing a lock can be removed without lock release causes depending transactions to hang. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12328) IgniteException "Failed to resolve nodes topology" during cache.removeAll() and constantly changing topology
Alexei Scherbakov created IGNITE-12328:
--
Summary: IgniteException "Failed to resolve nodes topology" during
cache.removeAll() and constantly changing topology
Key: IGNITE-12328
URL: https://issues.apache.org/jira/browse/IGNITE-12328
Project: Ignite
Issue Type: Bug
Affects Versions: 2.7.6
Reporter: Alexei Scherbakov
Assignee: Alexei Scherbakov
Fix For: 2.8
{noformat}
[2019-09-25 13:13:58,339][ERROR][TxThread-threadNum-3] Failed to complete
transaction.
org.apache.ignite.IgniteException: Failed to resolve nodes topology
[cacheGrp=cache_group_36, topVer=AffinityTopologyVersion [topVer=16,
minorTopVer=0], history=[AffinityTopologyVersion [topVer=13, minorTopVer=0],
AffinityTopologyVersion [topVer=14, minorTopVer=0], AffinityTopologyVersion
[topVer=15, minorTopVer=0]], snap=Snapshot [topVer=AffinityTopologyVersion
[topVer=15, minorTopVer=0]], locNode=TcpDiscoveryNode
[id=6cbf7666-9a8c-4b61-8b3f-6351ef44bd4a,
consistentId=poc-tester-client-172.25.1.21-id-0, addrs=ArrayList [172.25.1.21],
sockAddrs=HashSet [lab21.gridgain.local/172.25.1.21:0], discPort=0, order=13,
intOrder=0, lastExchangeTime=1569406379934, loc=true,
ver=2.5.10#20190922-sha1:02133315, isClient=true]]
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.resolveDiscoCache(GridDiscoveryManager.java:2125)
~[ignite-core-2.5.10.jar:2.5.10]
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.cacheGroupAffinityNodes(GridDiscoveryManager.java:2007)
~[ignite-core-2.5.10.jar:2.5.10]
at
org.apache.ignite.internal.processors.cache.GridCacheUtils.affinityNodes(GridCacheUtils.java:465)
~[ignite-core-2.5.10.jar:2.5.10]
at
org.apache.ignite.internal.processors.cache.distributed.dht.colocated.GridDhtColocatedLockFuture.map0(GridDhtColocatedLockFuture.java:939)
~[ignite-core-2.5.10.jar:2.5.10]
at
org.apache.ignite.internal.processors.cache.distributed.dht.colocated.GridDhtColocatedLockFuture.map(GridDhtColocatedLockFuture.java:911)
~[ignite-core-2.5.10.jar:2.5.10]
at
org.apache.ignite.internal.processors.cache.distributed.dht.colocated.GridDhtColocatedLockFuture.map(GridDhtColocatedLockFuture.java:811)
~[ignite-core-2.5.10.jar:2.5.10]
at
org.apache.ignite.internal.processors.cache.distributed.dht.colocated.GridDhtColocatedCache.lockAllAsync(GridDhtColocatedCache.java:656)
~[ignite-core-2.5.10.jar:2.5.10]
at
org.apache.ignite.internal.processors.cache.distributed.GridDistributedCacheAdapter.txLockAsync(GridDistributedCacheAdapter.java:109)
~[ignite-core-2.5.10.jar:2.5.10]
at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.removeAllAsync0(GridNearTxLocal.java:1648)
~[ignite-core-2.5.10.jar:2.5.10]
at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.removeAllAsync(GridNearTxLocal.java:521)
~[ignite-core-2.5.10.jar:2.5.10]
at
org.apache.ignite.internal.processors.cache.GridCacheAdapter$33.inOp(GridCacheAdapter.java:2619)
~[ignite-core-2.5.10.jar:2.5.10]
at
org.apache.ignite.internal.processors.cache.GridCacheAdapter$SyncInOp.op(GridCacheAdapter.java:4701)
~[ignite-core-2.5.10.jar:2.5.10]
at
org.apache.ignite.internal.processors.cache.GridCacheAdapter.syncOp(GridCacheAdapter.java:3780)
~[ignite-core-2.5.10.jar:2.5.10]
at
org.apache.ignite.internal.processors.cache.GridCacheAdapter.removeAll0(GridCacheAdapter.java:2617)
~[ignite-core-2.5.10.jar:2.5.10]
at
org.apache.ignite.internal.processors.cache.GridCacheAdapter.removeAll(GridCacheAdapter.java:2606)
~[ignite-core-2.5.10.jar:2.5.10]
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.removeAll(IgniteCacheProxyImpl.java:1553)
~[ignite-core-2.5.10.jar:2.5.10]
at
org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.removeAll(GatewayProtectedCacheProxy.java:1026)
~[ignite-core-2.5.10.jar:2.5.10]
at
org.apache.ignite.scenario.TxBalanceTask$TxBody.doTxRemoveAll(TxBalanceTask.java:291)
~[poc-tester-0.1.0-SNAPSHOT.jar:?]
at
org.apache.ignite.scenario.TxBalanceTask$TxBody.call(TxBalanceTask.java:93)
~[poc-tester-0.1.0-SNAPSHOT.jar:?]
at
org.apache.ignite.scenario.TxBalanceTask$TxBody.call(TxBalanceTask.java:70)
~[poc-tester-0.1.0-SNAPSHOT.jar:?]
at
org.apache.ignite.scenario.internal.AbstractTxTask.doInTransaction(AbstractTxTask.java:290)
~[poc-tester-0.1.0-SNAPSHOT.jar:?]
at
org.apache.ignite.scenario.internal.AbstractTxTask.access$400(AbstractTxTask.java:56)
~[poc-tester-0.1.0-SNAPSHOT.jar:?]
at
org.apache.ignite.scenario.internal.AbstractTxTask$TxRunner.call(AbstractTxTask.java:470)
[poc-tester-0.1.0-SNAPSHOT.jar:?]
at
