[ANNOUNCE] Apache Ignite Extensions Released

The Apache Ignite Community is pleased to announce the release of the following Apache Ignite Extensions: - Ignite AWS Extension 1.0.0 - Ignite Azure Extension 1.0.0 - Ignite GCE Extension 1.0.0 - Ignite Spring Data Extension 2.0.0 - Ignite Spring Session Extension 1.0.0 - Ignite Zookeeper Ip Finde

Re: [DISCUSSION] IEP-88: CLI Tool

Hi, My two cents: 1. CLI Tool - looks like not the best name :) Shell? 2. The description says: "REPL mode is used by default and is activated if the ignite command is executed without parameters." I think it is a bad idea. Firstly, it is usual CLI's behaviour to print a help for a user. An exc

[MTCGA]: new failures in builds [6441382] needs to be handled

Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. If your changes can lead to this failure(s): We're grateful that you were a volunteer to make the contribution to this project, but things change and you may no longer be able to finalize

Re: [DISCUSSION] Add additional 3rd party libraries to Ignite 3 Code style and practices

I personally don't support any additional 3rd party dependencies as well as I don't fully understand the value of autogenerated specs for REST endpoints. In my opinion we have another option: writing spec manually. This option doesn't require any of proposed dependencies and allow to avoid possible

Re: [DISCUSSION] IEP-88: CLI Tool

Hi, Andrey Thanks for comments. 1. Does “Ignite shell” sounds better? 2. Yes, you are right. Most tools print help if they are executed without arguments. But I did not get your point about scripting. What do you mean by saying “it will just hang”? What kind of error is going to be the

Re: IEP-90 Ignite 3 Client Lifecycle

Igor, Thanks for the proposal. I understand that such a situation is almost impossible but "if anything can go wrong, it will". Does the protocol take into account that different connections on different client instances theoretically could generate an already existing connection ID? Also, do I

Re: [DISCUSSION] IEP-88: CLI Tool

> 1. Does “Ignite shell” sounds better? I don't know. It could be Ignite REPL, IGnite Shell or something else. Just an idea. > But I did not get your point about scripting. What do you mean by saying “it > will just hang”? What kind of error is going to be the cause of such > behaviour? I can

Re: [DISCUSSION] Add additional 3rd party libraries to Ignite 3 Code style and practices

Hi, Igniters! I am really glad about the 140 symbol column limit. But aside from possible vulnerabilities mentioned above I have other concerns, which may affect some future users. Micronaut is a rather popular framework. Are we planning some OSGI support (or custom classloader magic) so users w

[MTCGA]: new failures in builds [6437143] needs to be handled

Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. *Test with high flaky rate in master WebSessionV1SelfTest.testRestarts https://ci2.ignite.apache.org/test/-1286479574239436447?currentProjectId=IgniteTests24Java8&branch=%3Cdefault%3E

Re: [DISCUSSION] Move the ignite-yarn, ignite-geospatial, ignite-schedule to the Ignite Extensions

Ilya, Should we start a formal vote about the ignite-schedule deletion? On Mon, 16 May 2022 at 14:28, Ilya Kasnacheev wrote: > > Hello! > > In my opinion, the ignite-schedule module needs to be dropped - it has bad > API, outdated GPL dependency and in general is out of focus of Ignite. > > Rega

Re: [DISCUSSION] Move the ignite-yarn, ignite-geospatial, ignite-schedule to the Ignite Extensions

Folks, Let's extend a bit the list of modules for moving to the Ignite Extensions. The list: - ignite-yarn - ignite-geospatial - ignite-mesos - ignite-cloud - ignite-osgi* - ignite-schedule (deletion proposed) On Thu, 19 May 2022 at 09:20, Maxim Muzafarov wrote: > > Ilya, > > Should we start a