Re: Re[2]: [DISCUSSION] Apache Ignite Release 2.10 (time, scope, manager)
Folks, I've done almost all the release steps with publishing accepted changes. What should I do with an announcement blog post for blogs.apache.org? Should it also be prepared prior to an announcement message? On Thu, 11 Mar 2021 at 00:10, Maxim Muzafarov wrote: > > Pavel, > > Thank you! I'll prepare a new rc shortly. > > On Wed, 10 Mar 2021 at 23:20, Pavel Tupitsyn wrote: > > > > Maxim, thanks! > > I've cherry-picked IGNITE-14293. > > > > On Wed, Mar 10, 2021 at 10:05 PM Maxim Muzafarov wrote: > > > > > Pavel, > > > > > > Sorry, my bad. Entangled in my local branches during trying to > > > cherry-pick related commits. > > > I've reverted this change. > > > > > > > > > On Wed, 10 Mar 2021 at 21:58, Pavel Tupitsyn wrote: > > > > > > > > Maxim, > > > > > > > > I see that you have already cherry-picked IGNITE-13979 - was that > > > > intentional? > > > > If we keep it, let's cherry-pick 14250 as well? > > > > > > > > On Wed, Mar 10, 2021 at 8:21 PM Maxim Muzafarov > > > wrote: > > > > > > > > > Pavel, > > > > > > > > > > > > > > > I think it is better and safe to cherry-pick the `IGNITE-14293 .NET: > > > > > AffinityKey does not work` only. I will be very happy to accept your > > > > > help with it. > > > > > > > > > > > > > > > The IGNITE-13979 (.NET: Modernize examples) is very big and has some > > > > > related issues too (most of them are fixed), so I think it is better > > > > > here to postpone it to the next release and give it a bit of time for > > > > > the self-stabilization process :-) > > > > > > > > > > On Wed, 10 Mar 2021 at 20:17, Pavel Tupitsyn > > > wrote: > > > > > > > > > > > > Maxim, > > > > > > > > > > > > Sure, I can assist with cherry-picks. > > > > > > > > > > > > 13661 is fixed by 13979, as indicated by the "fixed by" link in Jira > > > and > > > > > a comment. > > > > > > > > > > > > IGNITE-14293 .NET: AffinityKey does not work is quite an unpleasant > > > > > regression, > > > > > > I think we should include it in the release. It CAN be included > > > without > > > > > 14250 and 13979. > > > > > > > > > > > > 14250 does not make sense without 13979. > > > > > > > > > > > > Ultimately, the question is - do we want to include 13979 (.NET: > > > > > Modernize examples), > > > > > > or not. Thoughts? > > > > > > > > > > > > > > > > > > On Wed, Mar 10, 2021 at 7:45 PM Maxim Muzafarov > > > > > wrote: > > > > > >> > > > > > >> Pavel, > > > > > >> > > > > > >> > > > > > >> Can you assist a bit with the cherry-picking process of `.NET: > > > > > >> AffinityKey does not work` IGNITE-14293? I'm not sure I can > > > understand > > > > > >> all the details of implementation and actually, I'm stuck a bit > > > > > >> with > > > > > >> the `.NET: Race condition in Events example` IGNITE-14250 [2] issue > > > > > >> not sure what exactly I can exclude from the commit to resolve > > > > > >> conflicts since it has some of them with the 2.10 branch. I'm > > > worried > > > > > >> about missing some important parts of the code. > > > > > >> > > > > > >> > > > > > >> - I dive a bit in addition to the .NET examples and found an issue > > > [4] > > > > > >> that has `Fixed` status, however, I can't find it either by id or > > > > > >> by > > > > > >> history. > > > > > >> - It is also an important issue (probably I've missed) the .NET: > > > > > >> Modernize examples [5]. Currently, it's not included in 2.10 (the > > > fix > > > > > >> `.NET: Race condition in Events example` depends on it) > > > > > >> > > > > > >> So, summarize all if mentioned above: > > > > > >> > > > > > >> Can we cherry-pick only the `.NET: AffinityKey does not work` > > > > > >> IGNITE-14293 without all dependent issues? Or we should apply all > > > from > > > > > >> the chain? > > > > > >> > > > > > >> > > > > > >> [1] https://issues.apache.org/jira/browse/IGNITE-14293 > > > > > >> [2] https://issues.apache.org/jira/browse/IGNITE-14250 > > > > > >> [3] https://issues.apache.org/jira/browse/IGNITE-13661 > > > > > >> [4] https://issues.apache.org/jira/browse/IGNITE-13661 > > > > > >> [5] https://issues.apache.org/jira/browse/IGNITE-13979 > > > > > >> > > > > > >> On Wed, 10 Mar 2021 at 18:50, Pavel Tupitsyn > > > > > wrote: > > > > > >> > > > > > > >> > Maxim, > > > > > >> > > > > > > >> > No objections to those cherry-picks, > > > > > >> > please also include > > > > > https://issues.apache.org/jira/browse/IGNITE-14293 > > > > > >> > > > > > > >> > Thanks! > > > > > >> > > > > > > >> > On Wed, Mar 10, 2021 at 10:54 AM Ilya Kasnacheev < > > > > > ilya.kasnach...@gmail.com> > > > > > >> > wrote: > > > > > >> > > > > > > >> > > Hello! > > > > > >> > > > > > > > >> > > Unless we do extra checks for Windows environment, I suggest > > > merging > > > > > >> > > IGNITE-14284 < > > > https://issues.apache.org/jira/browse/IGNITE-14284> > > > > > >> > > > > > > > >> > > Regards, > > > > > >> > > -- > > > > > >> > > Ilya Kasnacheev > > > > > >> > > > > > > > >> > > > > > > > >> > > вт, 9 мар. 2021 г. в 20:26, Maxim Muzafarov
Re: How to Contribute 2021
Hi Igniters, > I think this guide should be much shorter and simple. As you know we also have CONTRIBUTING.md [1] on GitHub. Perhaps it can be the shortest one for newcomers. [1] https://github.com/apache/ignite/blob/master/CONTRIBUTING.md 2021-03-15 21:56 GMT+03:00, Kseniya Romanova : >> >> > Components and their maintainers >> > It seems that this list should be updated too. >> I would be glad if somebody does it, but I don't have any more >> information >> to fill there. > > > I'll be happy to collect information and update this section. But I also > think this should be a separate page (and howto should have a link on it). > > пн, 15 мар. 2021 г. в 18:25, Pavel Tupitsyn : > >> Ilya, >> >> Thanks for the effort! >> >> I think this guide should be much shorter and simple. >> Right now it is intimidating for newcomers. >> >> What they need is basically >> * Register in Jira, pick a ticket, assign, put In Progress >> * Create a fork, implement >> * Create a PR >> * Ask for review >> >> Maybe we should have a separate, detailed guide for Committers, >> and a simple one for Contributors? >> >> On Mon, Mar 15, 2021 at 6:19 PM Ilya Kasnacheev >> > > >> wrote: >> >> > Hello! >> > >> > Please see inline. >> > >> > пн, 15 мар. 2021 г. в 18:06, Maxim Muzafarov : >> > >> > > Hello, >> > > >> > > >> > > > Ignite employs both Review-Then-Commit processes. >> > > >> > > The Commit-Then-Review (CTR) removed? >> > > >> > I don't see any applications of CTR during the few last years. >> > Streamers >> > were supposed to be CTR but Saikat Maitra still asked for the review of >> > streamers-related commits. >> > >> > > Information for committers >> > > >> > > Do we need this on a page for newcomers? I'd like to mention that >> > > some >> > > of the committers still use the commit script, however, I think it >> > > will be better to configure the GitHub interaction. >> > > >> > I don't think there's a separate page for committers. If there is, >> > please >> > point me to it, and we can remove the section. I don't think we should >> > be >> > writing two pages at once, so I decided not to drop any essential >> > information. >> > >> > > Components and their maintainers >> > > >> > > It seems that this list should be updated too. >> > > >> > I would be glad if somebody does it, but I don't have any more >> information >> > to fill there. >> > >> > >> > > > Working on a ticket >> > > I think we should mention the Intellij IDEA checkstyle plugin and its >> > > configuration (importation of checkstyle.xml to the IDE). >> > > >> > I would be glad if somebody contributes to it, or we may just provide a >> > link to coding guidelines and mention it there. >> > >> > >> > >> > > > GIT workflow >> > > >> > > Do we need it? >> > > >> > I think we do, this workflow is non-trivial and I don't think it is >> > documented anywhere. We can get rid of ASCII art section, though. >> > >> > WDYT? >> > >> > Regards, >> > >> > >> > > >> > > >> > > On Mon, 15 Mar 2021 at 17:25, Ilya Kasnacheev < >> ilya.kasnach...@gmail.com >> > > >> > > wrote: >> > > > >> > > > Hello! >> > > > >> > > > When adding new users to the Contributor role, we usually give them >> > > > a >> > > link >> > > > to "How to Contribute" wiki page. >> > > > >> > > > However, I was feeling that it was in many ways outdated, referring >> to >> > > > outdated development practices and not emphasising TC tests and >> > > > MTCGA >> > > bot. >> > > > >> > > > So we took liberty to rewrite this page, meet >> > > > >> > > >> > >> https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute+2021 >> > > > >> > > > We tried to streamline it, make it more friendly to newcomers and >> just >> > > > shorter. >> > > > >> > > > Please check it out, share your feelings. >> > > > >> > > > I plan to replace the legacy >> > > > https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute >> > > with >> > > > this page based on your feedback.. >> > > > >> > > > Regards, >> > > > -- >> > > > Ilya Kasnacheev >> > > >> > >> > -- Best regards, Ivan Pavlukhin
Re: Hello
Hi Ilya My ID on Apache JIRA is marius_filip. Kind regards, Marius Filip On Mon, Mar 15, 2021 at 10:25 AM Ilya Kasnacheev wrote: > Hello! > > Please write your JIRA account name, when you have it, so that I can add it > to contributors role. > > Ask me if you have any questions. > > Regards, > -- > Ilya Kasnacheev > > > вс, 14 мар. 2021 г. в 19:54, Marius Filip : > > > Hi > > > > My name is Marius Filip, I am based in London and I am Lead of APIs and > > Back-end Services with a small company that produces software for > Commodity > > Trading called Amphora Inc. > > > > We are building the new version of our flagship product (which is > > successful but in need of modernization) and Apache Ignite is an > essential > > part of this effort. > > > > I would like to contribute to Ignite since not only is so important to > the > > company I work for but also is of great interest to me. > > > > I have long experience in system programming (from OS to trading > platforms) > > and for Amphora our main domains of concern are Ignite's > transactionality, > > persistence and continuous querying so those are the areas where, > naturally > > I would like mostly to contribute to. > > > > But I could also help, at least in the beginning, to things like bug > > fixing, testing or documentation. > > > > This endeavour starts with the consent of my employer. Currently I am > > following the steps from here ( > > https://ignite.apache.org/community/resources.html) and here ( > > > > > https://ignite.apache.org/community/contribute.html#:~:text=Contribute%20by%20Helping%20Others,mailing%20list%20or%20on%20StackOverflow > > .) > > but more surely I will soon need a bit of info beyond that. > > > > Regards, > > Marius Filip > > >
Re: Hello
Hi Denis Thank you for the warm welcome. Kind regards, Marius Filip On Mon, Mar 15, 2021 at 4:22 PM Denis Magda wrote: > Hi Marius, > > Welcome to the community! Good to see you coming and contributing back to > the project. > > - > Denis > > > On Sun, Mar 14, 2021 at 12:54 PM Marius Filip > wrote: > > > Hi > > > > My name is Marius Filip, I am based in London and I am Lead of APIs and > > Back-end Services with a small company that produces software for > Commodity > > Trading called Amphora Inc. > > > > We are building the new version of our flagship product (which is > > successful but in need of modernization) and Apache Ignite is an > essential > > part of this effort. > > > > I would like to contribute to Ignite since not only is so important to > the > > company I work for but also is of great interest to me. > > > > I have long experience in system programming (from OS to trading > platforms) > > and for Amphora our main domains of concern are Ignite's > transactionality, > > persistence and continuous querying so those are the areas where, > naturally > > I would like mostly to contribute to. > > > > But I could also help, at least in the beginning, to things like bug > > fixing, testing or documentation. > > > > This endeavour starts with the consent of my employer. Currently I am > > following the steps from here ( > > https://ignite.apache.org/community/resources.html) and here ( > > > > > https://ignite.apache.org/community/contribute.html#:~:text=Contribute%20by%20Helping%20Others,mailing%20list%20or%20on%20StackOverflow > > .) > > but more surely I will soon need a bit of info beyond that. > > > > Regards, > > Marius Filip > > >
[DISCUSSION] Patch completely breaks MVCC.
Hi, Igniters! I'm working on a feature (moving indexes to the core module) and skip specific implementation for MVCC as it is considered deprecated (the vote result [1]). Am I right that now there is no need to support MVCC? Then there are a lot of tests (both Java, C++) that fail because they run with TRANSACTIONAL_SNAPSHOT atomicity mode. There are 2 cases: 1. MVCC mode is just a parameter of a test. I just removed it from a parameters list; 2. There are tests that run only for MVCC. I marked them with the @Ignore annotation. But would it better just completely remove all such tests that are broken by the patch? [1] http://apache-ignite-developers.2346864.n4.nabble.com/RESULT-VOTE-Removing-MVCC-public-API-td50705.html#a50706
Re: How to Contribute 2021
> > > Components and their maintainers > > It seems that this list should be updated too. > I would be glad if somebody does it, but I don't have any more information > to fill there. I'll be happy to collect information and update this section. But I also think this should be a separate page (and howto should have a link on it). пн, 15 мар. 2021 г. в 18:25, Pavel Tupitsyn : > Ilya, > > Thanks for the effort! > > I think this guide should be much shorter and simple. > Right now it is intimidating for newcomers. > > What they need is basically > * Register in Jira, pick a ticket, assign, put In Progress > * Create a fork, implement > * Create a PR > * Ask for review > > Maybe we should have a separate, detailed guide for Committers, > and a simple one for Contributors? > > On Mon, Mar 15, 2021 at 6:19 PM Ilya Kasnacheev > > wrote: > > > Hello! > > > > Please see inline. > > > > пн, 15 мар. 2021 г. в 18:06, Maxim Muzafarov : > > > > > Hello, > > > > > > > > > > Ignite employs both Review-Then-Commit processes. > > > > > > The Commit-Then-Review (CTR) removed? > > > > > I don't see any applications of CTR during the few last years. Streamers > > were supposed to be CTR but Saikat Maitra still asked for the review of > > streamers-related commits. > > > > > Information for committers > > > > > > Do we need this on a page for newcomers? I'd like to mention that some > > > of the committers still use the commit script, however, I think it > > > will be better to configure the GitHub interaction. > > > > > I don't think there's a separate page for committers. If there is, please > > point me to it, and we can remove the section. I don't think we should be > > writing two pages at once, so I decided not to drop any essential > > information. > > > > > Components and their maintainers > > > > > > It seems that this list should be updated too. > > > > > I would be glad if somebody does it, but I don't have any more > information > > to fill there. > > > > > > > > Working on a ticket > > > I think we should mention the Intellij IDEA checkstyle plugin and its > > > configuration (importation of checkstyle.xml to the IDE). > > > > > I would be glad if somebody contributes to it, or we may just provide a > > link to coding guidelines and mention it there. > > > > > > > > > > GIT workflow > > > > > > Do we need it? > > > > > I think we do, this workflow is non-trivial and I don't think it is > > documented anywhere. We can get rid of ASCII art section, though. > > > > WDYT? > > > > Regards, > > > > > > > > > > > > > On Mon, 15 Mar 2021 at 17:25, Ilya Kasnacheev < > ilya.kasnach...@gmail.com > > > > > > wrote: > > > > > > > > Hello! > > > > > > > > When adding new users to the Contributor role, we usually give them a > > > link > > > > to "How to Contribute" wiki page. > > > > > > > > However, I was feeling that it was in many ways outdated, referring > to > > > > outdated development practices and not emphasising TC tests and MTCGA > > > bot. > > > > > > > > So we took liberty to rewrite this page, meet > > > > > > > > > > https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute+2021 > > > > > > > > We tried to streamline it, make it more friendly to newcomers and > just > > > > shorter. > > > > > > > > Please check it out, share your feelings. > > > > > > > > I plan to replace the legacy > > > > https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute > > > with > > > > this page based on your feedback.. > > > > > > > > Regards, > > > > -- > > > > Ilya Kasnacheev > > > > > >
[jira] [Created] (IGNITE-14320) .NET: Collections can't be used as service method parameters
Nikolay Izhikov created IGNITE-14320:
Summary: .NET: Collections can't be used as service method
parameters
Key: IGNITE-14320
URL: https://issues.apache.org/jira/browse/IGNITE-14320
Project: Ignite
Issue Type: Improvement
Reporter: Nikolay Izhikov
Currently, collections (list, map) can't be used as a service method parameter
in case of
.Net (client node) -> .Net (server node) call.
This can be reproduced my one line modification of
{{ServicesTypeAutoResolveTest#DoTestPlatformService}}
{code:java}
///
/// Tests .Net service invocation.
///
public void DoTestPlatformService(IServices svcsForProxy)
{
const string platformSvcName = "PlatformTestService";
_grid1.GetServices().DeployClusterSingleton(platformSvcName, new
PlatformTestService());
var svc =
svcsForProxy.GetServiceProxy(platformSvcName);
DoTestService(svc);
DoTestCollections(svc); // This line was added.
_grid1.GetServices().Cancel(platformSvcName);
}
{code}
Exception:
{noformat}
Apache.Ignite.Core.Services.ServiceInvocationException : Proxy method
invocation failed with an exception. Examine InnerException for details.
> Apache.Ignite.Core.Common.IgniteException : No matching type found for
object [typeId=1552553483,
typeName=org.system.collections.generic.List`1[[org.apache.ignite.platform.model.department,
apache.ignite.core.testDepartment]]]. This usually indicates that assembly
with specified type is not loaded on a node. When using Apache.Ignite.exe, make
sure to load assemblies with -assembly parameter. Alternatively, set
IgniteConfiguration.PeerAssemblyLoadingMode to CurrentAppDomain.
{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
Re: [DISCUSSION] IEP-69 The evolutionary release process
Folks, let me add my 50 cents. I don't see major issues with this IEP, for now. And I really looking forward to talking about it. I can't get what causes misunderstanding. The only thing that concerns me here is that IEP requires the community to support solutions for 1 year, 1 quarter, etc. Apache community is not a commercial company that provides support of any kind, and I would be reluctant to add these or similar statements to any public documents. At any point in time, the community and PMC can vote and introduce any major feature breaking compatibility. We tend to avoid such actions to keep users best interest. But it is not a commitment. Sincerely чт, 11 мар. 2021 г. в 23:11, Maxim Muzafarov : > Val, > > > I'm sorry if anything from what I've said sounded disrespectful. All > of you are examples for me to follow :-) > > Have you checked the `motivation` [1] topic on the IEP-69 page? Should > I add more details to it prior to the call? I want to make Ignite > better and also think that the current 2.x version with all the > advantages and disadvantages is far from exhausted its capabilities. > I'm pretty sure the same motivation page exists for 3.0 version > describing the advantages and disadvantages of developing mentioned > IEPs. It will be good to share it prior to the cal also. > > > [1] > https://cwiki.apache.org/confluence/display/IGNITE/IEP-69%3A+The+evolutionary+release+process#IEP69:Theevolutionaryreleaseprocess-Motivation > > On Thu, 11 Mar 2021 at 01:21, Valentin Kulichenko > wrote: > > > > Ksenya, thanks for scheduling this so quickly! > > > > Guys, I hope we can make this discussion constructive. Please keep in > mind > > that Ignite 3 is an ongoing project supported by multiple contributors, > > committers, and PMC members. Neglecting 6+ months of effort and > suggesting > > that it's just "prototyping some cool features and nothing more" is > really > > bizarre, and, quite frankly, sounds disrespectful to fellow developers > > (although I'm 100% sure it was not intended this way). > > > > Maxim, one of the biggest issues I have with your IEP is that I don't > > understand the motivation behind it. If you don't mind, I would like to > > suggest that you kick off the meeting with a detailed explanation > > of exactly that. The first step is to achieve a mutual understanding of > > each other's goals. Once we do that, I'm sure we will easily find a > > solution. > > > > -Val > > > > On Wed, Mar 10, 2021 at 8:55 AM Kseniya Romanova < > romanova.ks@gmail.com> > > wrote: > > > > > Let's make a quick call next week and try to find a compromise which > can > > > get the process moving: > > > https://www.meetup.com/Moscow-Apache-Ignite-Meetup/events/276851588/ > > > > > > ср, 10 мар. 2021 г. в 16:27, Maxim Muzafarov : > > > > > > > Folks, > > > > > > > > > > > > Agree, the discussion may be endless without compromises on all > sides. > > > > I always think that if there is no consensus (and I see from the > > > > thread [1] that it's was no found) for such important decisions like > > > > product future development and releases AFS provides the voting > > > > procedure. Without fixing the results of the discussion [1] it sounds > > > > like prototyping some cool features and nothing more. > > > > > > > > So, back to Denis suggestion can you share - what would be the best > > > > time for all of us (considering different time zones) to have a call? > > > > > > > > I also think that we should start a vote about the future releases on > > > > our Apache Ignite web-site and user-list, thus all who are using the > > > > Apache Ignite may choose the best option they like. > > > > > > > > > > > > [1] > > > > > > > > http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Ignite-3-0-development-approach-td49922.html > > > > > > > > On Wed, 10 Mar 2021 at 03:57, Valentin Kulichenko > > > > wrote: > > > > > > > > > > Hi Maxim, > > > > > > > > > > I disagree with the suggestions. Several community members have > already > > > > > pointed out the discussion about Ignite 3.0 [1]. During that > > > discussion, > > > > we > > > > > did agree on the scope of the changes for 3.0, as well as the > general > > > > > direction for the product. The new repo was created not to "develop > > > from > > > > > scratch", but to provide an opportunity for the community members > to > > > > > actively work on Ignite 3 without killing the Ignite 2.x. No > > > alternative > > > > > solution for this was presented, so we went ahead with the process > -- I > > > > > consider that to be an example of the silent consensus. > > > > > > > > > > I also want to emphasize that Ignite 3 is active and is moving > forward. > > > > If > > > > > you look at the ignite-3 repo, commits and PRs are coming in on > regular > > > > > basis. We also had the first alpha release early in the year. I do > > > agree > > > > > with you, however, that there is not too much activity on the dev > list. > > > > As > > > > > far as I
IEP-70: Async Continuation Executor
Igniters, Please review the IEP [1] and let me know your thoughts. [1] https://cwiki.apache.org/confluence/display/IGNITE/IEP-70%3A+Async+Continuation+Executor
Re: Hello
Hi Marius, Welcome to the community! Good to see you coming and contributing back to the project. - Denis On Sun, Mar 14, 2021 at 12:54 PM Marius Filip wrote: > Hi > > My name is Marius Filip, I am based in London and I am Lead of APIs and > Back-end Services with a small company that produces software for Commodity > Trading called Amphora Inc. > > We are building the new version of our flagship product (which is > successful but in need of modernization) and Apache Ignite is an essential > part of this effort. > > I would like to contribute to Ignite since not only is so important to the > company I work for but also is of great interest to me. > > I have long experience in system programming (from OS to trading platforms) > and for Amphora our main domains of concern are Ignite's transactionality, > persistence and continuous querying so those are the areas where, naturally > I would like mostly to contribute to. > > But I could also help, at least in the beginning, to things like bug > fixing, testing or documentation. > > This endeavour starts with the consent of my employer. Currently I am > following the steps from here ( > https://ignite.apache.org/community/resources.html) and here ( > > https://ignite.apache.org/community/contribute.html#:~:text=Contribute%20by%20Helping%20Others,mailing%20list%20or%20on%20StackOverflow > .) > but more surely I will soon need a bit of info beyond that. > > Regards, > Marius Filip >
[jira] [Created] (IGNITE-14319) Multithreaded data generation for rebalance tests
Dmitriy Sorokin created IGNITE-14319:
Summary: Multithreaded data generation for rebalance tests
Key: IGNITE-14319
URL: https://issues.apache.org/jira/browse/IGNITE-14319
Project: Ignite
Issue Type: Sub-task
Reporter: Dmitriy Sorokin
Assignee: Dmitriy Sorokin
At the moment, {{DataGenerationApplication}} generates data in the single
thread. We should make that routine multithreaded.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
Re: How to Contribute 2021
Ilya, Thanks for the effort! I think this guide should be much shorter and simple. Right now it is intimidating for newcomers. What they need is basically * Register in Jira, pick a ticket, assign, put In Progress * Create a fork, implement * Create a PR * Ask for review Maybe we should have a separate, detailed guide for Committers, and a simple one for Contributors? On Mon, Mar 15, 2021 at 6:19 PM Ilya Kasnacheev wrote: > Hello! > > Please see inline. > > пн, 15 мар. 2021 г. в 18:06, Maxim Muzafarov : > > > Hello, > > > > > > > Ignite employs both Review-Then-Commit processes. > > > > The Commit-Then-Review (CTR) removed? > > > I don't see any applications of CTR during the few last years. Streamers > were supposed to be CTR but Saikat Maitra still asked for the review of > streamers-related commits. > > > Information for committers > > > > Do we need this on a page for newcomers? I'd like to mention that some > > of the committers still use the commit script, however, I think it > > will be better to configure the GitHub interaction. > > > I don't think there's a separate page for committers. If there is, please > point me to it, and we can remove the section. I don't think we should be > writing two pages at once, so I decided not to drop any essential > information. > > > Components and their maintainers > > > > It seems that this list should be updated too. > > > I would be glad if somebody does it, but I don't have any more information > to fill there. > > > > > Working on a ticket > > I think we should mention the Intellij IDEA checkstyle plugin and its > > configuration (importation of checkstyle.xml to the IDE). > > > I would be glad if somebody contributes to it, or we may just provide a > link to coding guidelines and mention it there. > > > > > > GIT workflow > > > > Do we need it? > > > I think we do, this workflow is non-trivial and I don't think it is > documented anywhere. We can get rid of ASCII art section, though. > > WDYT? > > Regards, > > > > > > > > On Mon, 15 Mar 2021 at 17:25, Ilya Kasnacheev > > > wrote: > > > > > > Hello! > > > > > > When adding new users to the Contributor role, we usually give them a > > link > > > to "How to Contribute" wiki page. > > > > > > However, I was feeling that it was in many ways outdated, referring to > > > outdated development practices and not emphasising TC tests and MTCGA > > bot. > > > > > > So we took liberty to rewrite this page, meet > > > > > > https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute+2021 > > > > > > We tried to streamline it, make it more friendly to newcomers and just > > > shorter. > > > > > > Please check it out, share your feelings. > > > > > > I plan to replace the legacy > > > https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute > > with > > > this page based on your feedback.. > > > > > > Regards, > > > -- > > > Ilya Kasnacheev > > >
Re: How to Contribute 2021
Hello! Please see inline. пн, 15 мар. 2021 г. в 18:06, Maxim Muzafarov : > Hello, > > > > Ignite employs both Review-Then-Commit processes. > > The Commit-Then-Review (CTR) removed? > I don't see any applications of CTR during the few last years. Streamers were supposed to be CTR but Saikat Maitra still asked for the review of streamers-related commits. > Information for committers > > Do we need this on a page for newcomers? I'd like to mention that some > of the committers still use the commit script, however, I think it > will be better to configure the GitHub interaction. > I don't think there's a separate page for committers. If there is, please point me to it, and we can remove the section. I don't think we should be writing two pages at once, so I decided not to drop any essential information. > Components and their maintainers > > It seems that this list should be updated too. > I would be glad if somebody does it, but I don't have any more information to fill there. > > Working on a ticket > I think we should mention the Intellij IDEA checkstyle plugin and its > configuration (importation of checkstyle.xml to the IDE). > I would be glad if somebody contributes to it, or we may just provide a link to coding guidelines and mention it there. > > GIT workflow > > Do we need it? > I think we do, this workflow is non-trivial and I don't think it is documented anywhere. We can get rid of ASCII art section, though. WDYT? Regards, > > > On Mon, 15 Mar 2021 at 17:25, Ilya Kasnacheev > wrote: > > > > Hello! > > > > When adding new users to the Contributor role, we usually give them a > link > > to "How to Contribute" wiki page. > > > > However, I was feeling that it was in many ways outdated, referring to > > outdated development practices and not emphasising TC tests and MTCGA > bot. > > > > So we took liberty to rewrite this page, meet > > > https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute+2021 > > > > We tried to streamline it, make it more friendly to newcomers and just > > shorter. > > > > Please check it out, share your feelings. > > > > I plan to replace the legacy > > https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute > with > > this page based on your feedback.. > > > > Regards, > > -- > > Ilya Kasnacheev >
Re: How to Contribute 2021
Hello, > Ignite employs both Review-Then-Commit processes. The Commit-Then-Review (CTR) removed? > Information for committers Do we need this on a page for newcomers? I'd like to mention that some of the committers still use the commit script, however, I think it will be better to configure the GitHub interaction. > Components and their maintainers It seems that this list should be updated too. > Working on a ticket I think we should mention the Intellij IDEA checkstyle plugin and its configuration (importation of checkstyle.xml to the IDE). > GIT workflow Do we need it? On Mon, 15 Mar 2021 at 17:25, Ilya Kasnacheev wrote: > > Hello! > > When adding new users to the Contributor role, we usually give them a link > to "How to Contribute" wiki page. > > However, I was feeling that it was in many ways outdated, referring to > outdated development practices and not emphasising TC tests and MTCGA bot. > > So we took liberty to rewrite this page, meet > https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute+2021 > > We tried to streamline it, make it more friendly to newcomers and just > shorter. > > Please check it out, share your feelings. > > I plan to replace the legacy > https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute with > this page based on your feedback.. > > Regards, > -- > Ilya Kasnacheev
[jira] [Created] (IGNITE-14318) Add PartitionEvictionOrderTest to IgniteBasicTestSuite
Mirza Aliev created IGNITE-14318: Summary: Add PartitionEvictionOrderTest to IgniteBasicTestSuite Key: IGNITE-14318 URL: https://issues.apache.org/jira/browse/IGNITE-14318 Project: Ignite Issue Type: Bug Reporter: Mirza Aliev Assignee: Mirza Aliev -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14317) IgniteCache.removeAsync(key,val) fails inside an optimistic transaction
Denis Garus created IGNITE-14317:
Summary: IgniteCache.removeAsync(key,val) fails inside an
optimistic transaction
Key: IGNITE-14317
URL: https://issues.apache.org/jira/browse/IGNITE-14317
Project: Ignite
Issue Type: Bug
Affects Versions: 2.9.1
Reporter: Denis Garus
[reproducer|https://github.com/apache/ignite/pull/8841/files]
IgniteCache.removeAsync(key,val) fails inside an optimistic tx with the
exception:
{code:java}
[17:39:28] (err) Failed to notify listener:
o.a.i.i.processors.cache.distributed.near.GridNearTxLocal$6...@19c520dbjava.lang.AssertionError[17:39:28]
(err) Failed to notify listener:
o.a.i.i.processors.cache.distributed.near.GridNearTxLocal$6...@19c520dbjava.lang.AssertionError
at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal$17.apply(GridNearTxLocal.java:2955)
at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal$17.apply(GridNearTxLocal.java:2937)
at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.processLoaded(GridNearTxLocal.java:3475)
at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal$21.apply(GridNearTxLocal.java:3217)
at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal$21.apply(GridNearTxLocal.java:3212)
at
org.apache.ignite.internal.util.future.GridFutureChainListener.applyCallback(GridFutureChainListener.java:78)
at
org.apache.ignite.internal.util.future.GridFutureChainListener.apply(GridFutureChainListener.java:70)
at
org.apache.ignite.internal.util.future.GridFutureChainListener.apply(GridFutureChainListener.java:30)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:399)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.unblock(GridFutureAdapter.java:347)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.unblockAll(GridFutureAdapter.java:335)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:511)
at
org.apache.ignite.internal.processors.cache.GridCacheFutureAdapter.onDone(GridCacheFutureAdapter.java:55)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:490)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.onDone(GridPartitionedSingleGetFuture.java:935)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:467)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.setSkipValueResult(GridPartitionedSingleGetFuture.java:759)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.onResult(GridPartitionedSingleGetFuture.java:636)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter.processNearSingleGetResponse(GridDhtCacheAdapter.java:368)
at
org.apache.ignite.internal.processors.cache.distributed.dht.colocated.GridDhtColocatedCache.access$100(GridDhtColocatedCache.java:88)
at
org.apache.ignite.internal.processors.cache.distributed.dht.colocated.GridDhtColocatedCache$2.apply(GridDhtColocatedCache.java:133)
at
org.apache.ignite.internal.processors.cache.distributed.dht.colocated.GridDhtColocatedCache$2.apply(GridDhtColocatedCache.java:131)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1143)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:592)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:393)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:319)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:309)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1908)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1529)
at
org.apache.ignite.internal.managers.communication.GridIoManager$9.execute(GridIoManager.java:1422)
at
org.apache.ignite.internal.managers.communication.TraceRunnable.run(TraceRunnable.java:55)
at
org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:569)
at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at java.base/java.lang.Thread.run(Thread.java:834){code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
How to Contribute 2021
Hello! When adding new users to the Contributor role, we usually give them a link to "How to Contribute" wiki page. However, I was feeling that it was in many ways outdated, referring to outdated development practices and not emphasising TC tests and MTCGA bot. So we took liberty to rewrite this page, meet https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute+2021 We tried to streamline it, make it more friendly to newcomers and just shorter. Please check it out, share your feelings. I plan to replace the legacy https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute with this page based on your feedback.. Regards, -- Ilya Kasnacheev
[jira] [Created] (IGNITE-14316) BinaryObject API
Andrey Mashenkov created IGNITE-14316: - Summary: BinaryObject API Key: IGNITE-14316 URL: https://issues.apache.org/jira/browse/IGNITE-14316 Project: Ignite Issue Type: Improvement Reporter: Andrey Mashenkov Let's create BinaryObject (BO) interface and a builder interface for it assuming - BO is a self-described object. Similar to Ignite-2 one with a compact footer. - BO is unmanaged. SchemaManager doesn't care about its schema at all. - BO can be deserialized to user class with a specified deserializer. - BO has a flat structure, cyclic links are not allowed. However, one can restore links on reserialization. - BO must not have any dependencies on Ignite internals. - Ignite should provide some base implementation for BO and builder. -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: Thin client implementation removal
Thanks. > 15 марта 2021 г., в 14:35, Igor Sapego написал(а): > > Nikolay, > > That's because we now have separate repos for them: [1], [2] and [3]. > Actually, active development is moved to those repos some time ago and > those directories in main repo are not actual anymore anyway. > > Decision of moving those clients to separate repos was discussed in [4] > > [1] - https://github.com/apache/ignite-python-thin-client > [2] - https://github.com/apache/ignite-nodejs-thin-client > [3] - https://github.com/apache/ignite-php-thin-client > [4] - > http://apache-ignite-developers.2346864.n4.nabble.com/Moving-python-php-and-node-js-in-separate-repos-and-release-cycles-td47030.html > > Best Regards, > Igor > > > On Mon, Mar 15, 2021 at 2:20 PM Nikolay Izhikov wrote: > >> Hello, Igor. >> >> I’ve noticed that Python, NodeJS, PHP thin client implementations were >> removed from master by you. >> Can you, please, comment? >> Why do you make those decision?
Re: Thin client implementation removal
Nikolay, That's because we now have separate repos for them: [1], [2] and [3]. Actually, active development is moved to those repos some time ago and those directories in main repo are not actual anymore anyway. Decision of moving those clients to separate repos was discussed in [4] [1] - https://github.com/apache/ignite-python-thin-client [2] - https://github.com/apache/ignite-nodejs-thin-client [3] - https://github.com/apache/ignite-php-thin-client [4] - http://apache-ignite-developers.2346864.n4.nabble.com/Moving-python-php-and-node-js-in-separate-repos-and-release-cycles-td47030.html Best Regards, Igor On Mon, Mar 15, 2021 at 2:20 PM Nikolay Izhikov wrote: > Hello, Igor. > > I’ve noticed that Python, NodeJS, PHP thin client implementations were > removed from master by you. > Can you, please, comment? > Why do you make those decision?
Thin client implementation removal
Hello, Igor. I’ve noticed that Python, NodeJS, PHP thin client implementations were removed from master by you. Can you, please, comment? Why do you make those decision?
Re: Hello
Hello! Please write your JIRA account name, when you have it, so that I can add it to contributors role. Ask me if you have any questions. Regards, -- Ilya Kasnacheev вс, 14 мар. 2021 г. в 19:54, Marius Filip : > Hi > > My name is Marius Filip, I am based in London and I am Lead of APIs and > Back-end Services with a small company that produces software for Commodity > Trading called Amphora Inc. > > We are building the new version of our flagship product (which is > successful but in need of modernization) and Apache Ignite is an essential > part of this effort. > > I would like to contribute to Ignite since not only is so important to the > company I work for but also is of great interest to me. > > I have long experience in system programming (from OS to trading platforms) > and for Amphora our main domains of concern are Ignite's transactionality, > persistence and continuous querying so those are the areas where, naturally > I would like mostly to contribute to. > > But I could also help, at least in the beginning, to things like bug > fixing, testing or documentation. > > This endeavour starts with the consent of my employer. Currently I am > following the steps from here ( > https://ignite.apache.org/community/resources.html) and here ( > > https://ignite.apache.org/community/contribute.html#:~:text=Contribute%20by%20Helping%20Others,mailing%20list%20or%20on%20StackOverflow > .) > but more surely I will soon need a bit of info beyond that. > > Regards, > Marius Filip >
Re: Access to Apache Ignite Wiki
Hello! I have added the usual grants to your account. Regards, -- Ilya Kasnacheev пн, 15 мар. 2021 г. в 13:17, Kseniya Romanova : > Hi, igniters! > Please grant me access to Ignite Wiki so I can help with editing and > updating info. The account is like in Jira - romanova.ks.spb. > > > -- > Cheers, > Kseniya > > Devrel at GridGain > Don't miss upcoming community events, join > https://www.meetup.com/Apache-Ignite-Virtual-Meetup/ >
Access to Apache Ignite Wiki
Hi, igniters! Please grant me access to Ignite Wiki so I can help with editing and updating info. The account is like in Jira - romanova.ks.spb. -- Cheers, Kseniya Devrel at GridGain Don't miss upcoming community events, join https://www.meetup.com/Apache-Ignite-Virtual-Meetup/
[jira] [Created] (IGNITE-14315) Ignite 3: Use maven-flatten plugin for project pom.xml
Alexey Goncharuk created IGNITE-14315: - Summary: Ignite 3: Use maven-flatten plugin for project pom.xml Key: IGNITE-14315 URL: https://issues.apache.org/jira/browse/IGNITE-14315 Project: Ignite Issue Type: Improvement Reporter: Alexey Goncharuk Without the flatten it would be impossible to use the maven-published artifacts of Ignite 3. -- This message was sent by Atlassian Jira (v8.3.4#803005)
IGNITE-14314: GridDhtLockFuture#onComplete Should Be Aware of Cache Cleanup
Hi All, I would like to propose a change: today, in GridDhtLockFuture, we do not consider if the cache context is being cleaned up before loading missing entries from the store. However, if the cache context is being cleaned up, this operation is moot. I have raised a PR for the same. Please share your thoughts: https://github.com/apache/ignite/pull/8877 Regards, Atri -- Regards, Atri Apache Concerted
[jira] [Created] (IGNITE-14314) GridDhtLockFuture#onComplete Should Be Aware of Cache Cleanup
Atri Sharma created IGNITE-14314: Summary: GridDhtLockFuture#onComplete Should Be Aware of Cache Cleanup Key: IGNITE-14314 URL: https://issues.apache.org/jira/browse/IGNITE-14314 Project: Ignite Issue Type: Improvement Reporter: Atri Sharma Said method only takes node stoppage into account while deciding if store should be accessed. This can lead to race conditions when the cache is being cleaned up. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14313) .NET: Add test to call .Net service from .Net
Nikolay Izhikov created IGNITE-14313:
Summary: .NET: Add test to call .Net service from .Net
Key: IGNITE-14313
URL: https://issues.apache.org/jira/browse/IGNITE-14313
Project: Ignite
Issue Type: Improvement
Reporter: Nikolay Izhikov
Assignee: Nikolay Izhikov
Currently, {{IJavaService}} methods in {{ServicesTest}} and
{{ServicesTypeAutoResolveTest}} only checked for .Net -> Java case. We should
extends it with .Net -> .Net invocation.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
