Re: IEP-78 .NET Thin Client for Ignite 3.0

Hi Pavel, I've created a thread. -Val On Mon, Sep 6, 2021 at 12:02 PM Pavel Tupitsyn wrote: > Val, > > Would you like me to start the discussion about sync-over-async in Ignite 3 > Java APIs, or do you plan to do it yourself? > > On Fri, Sep 3, 2021 at 10:10 PM Valentin Kulichenko < > valentin

Sync vs async APIs in Ignite 3

Igniters, I would like to gather some opinions on whether we want to focus on sync vs async APIs in Ignite 3. Here are some initial considerations that I have: 1. Ignite 2.x is essentially "sync first". Async APIs exist, but they use non-standard IgniteFuture and provide counterintuitive guarante

Re: Re[2]: Google Guava in Ignite 3

The voting has been started here On Mon, Sep 6, 2021 at 8:11 PM Andrey Gura wrote: > Alexander, > > Feel free to start voting. Please, refer to this discussion in order

Re: [VOTE] Allow or prohibit usages of the Guava library methods

Aleksandr, thanks for this activity. -1 from my side, all my decisions are in linked discussion.   >Dear Igniters, > >In this thread >< >https://lists.apache.org/thread.html/r4120a03a2bf32098e54e21ae02e509b0d68f413bc7cc1f8f6d85c93d%40%3Cdev.ignite.apache.org%3E > > >we've been discussing the prob

Re: [VOTE] Allow or prohibit usages of the Guava library methods

-1 Potential compatibility issues which are related to user specific code (services, jobs). Potential vulnerabilities which are a problem because we can't manage the Guava release cycle. Arguable approach with unnecessary immutability and unmanageable GC pressure. It's too hard to manage the *reaso

Re: [Announcement] Apache Ignite 2.11 Code Freeze started

Maxim, I've found an original ticket where Ilya was helping with review and testing of the Azure IP finder: https://issues.apache.org/jira/browse/IGNITE-14346 As I understand, the ticket you're referring to bumps up the version and introduces some other little changes: https://issues.apache.org/ji

Re: [VOTE] Allow or prohibit usages of the Guava library methods

+1 We already have some utility methods that are copy-pasted from Guava, which can be removed, and I believe that *reasonable* usage of this library can benefit the code and the product quality. On Tue, Sep 7, 2021 at 6:27 PM Alexander Polovtcev wrote: > Dear Igniters, > > In this thread >

[VOTE] Allow or prohibit usages of the Guava library methods

Dear Igniters, In this thread we've been discussing the problems and opportunities of using Guava in Ignite 3. We have agreed that it sho

Re: [Announcement] Apache Ignite 2.11 Code Freeze started

Maxim, I don't think we're rushing to release the changes. It seems to me that the integration is ready and can be released to the app developers. If we put it off until the next release to add an automated test in the real environment, it can take an unpredictable amount of time before it gets re

Re: [Announcement] Apache Ignite 2.11 Code Freeze started

Denis, AWS has a promotional credits program for open-source projects [1], maybe Azure has something similar too. Have we checked this topic at least? I'm not against the changes themselves, they are important for sure. However, for me, such changes are not as simple as they seem at first glance a

Re: [Announcement] Apache Ignite 2.11 Code Freeze started

Maxim, What's is the "standard way" and who is going to implement this standard approach for the Azure module? Just curious about the ETA of this feature availability. Ignite developers have been requesting the capability for a while and here it is. We're blocking it because of a missing automated

Taking a Break From Community

Hi All, I will be taking a break from the Ignite community for an indefinite period. During this period, I will not be available on the dev list or looking at JIRA tickets. If anything urgent comes up, please email me on my Apache email ID, or reach out on Slack. Atri

Re: [Announcement] Apache Ignite 2.11 Code Freeze started

Denis, Thank you for sharing the details. They look great! Can you clarify what is the reason for rushing these changes? Why we should merge changes without test coverage in the 2.11 release without doing it a standard way? Please, don't say that we always do such things for other modules, it bre

Re: [Announcement] Apache Ignite 2.11 Code Freeze started

A cloud deployment is not needed -- you only need to set the IPFinder to Azure and deploy a local Ignite cluster. If it boots up correctly, it works fine. I did not respond because my time is severely limited these days -- please note that my employment does not incorporate contributions to Ignite

Re: [Announcement] Apache Ignite 2.11 Code Freeze started

Denis, if Atri looked at the changes why didn't he left any comments or review approval? Only the ipfinder test was checked in Azure, it is essentially synthetic, is it enough? As far as I understand, we have to deploy Ignite itself in the cloud and play with it to make sure it works, unfortunate

Re: [Announcement] Apache Ignite 2.11 Code Freeze started

Maxim, Regardless of a lack of automated testing in a real environment, our AWS, GCE and other modules are used actively by the users and we don't receive issue reports. Here are the numbers: - AWS - 7000 *monthly* Maven downloads on average - GCE - 350 downloads - Kubernetes - 6000 down

Re: IEP-78 .NET Thin Client for Ignite 3.0

Igniters, Since there are no more comments, I'm going to merge the first PR later today and continue working on .NET thin client. There are separate tickets for CI setup [1] and full API support [2] [3]. [1] https://issues.apache.org/jira/browse/IGNITE-15432 [2] https://issues.apache.org/jira/bro