Re: Add to the Contributors group in JIRA

Hi Ivan, My account name is aleksandr.pakhomov Best regards, Aleksandr Pakhomov > On 5 Apr 2022, at 10:53, Ivan Pavlukhin wrote: > > Hi Aleksandr, > > Welcome to the Apache Ignite Community! > > What is your account name in Apache JIRA [1]? > > [1] htt

Add to the Contributors group in JIRA

Hello to the apache dev community, I am Pakhomov Aleksandr from Russia and I would like to contribute to the project. Could you please add me to the Contributors group in JIRA? Thank you.

Re: [DISCUSSION] IEP-88: CLI Tool

an error in a script it will just hang. So, a separate CLI > utility looks better than ignite CLI. > > > On Thu, May 12, 2022 at 11:43 PM Aleksandr Pakhomov wrote: >> >> Hello, Igniters. >> >> I’d like to start a discussion about Ignite 3 Command L

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

Hi Andrey, Thank you for the valuable arguments. Speaking about micronaut, it is a popular library that provides a lot of build-in features like error handling, auth, IoC, test infrastructure, and many more. The main functionality of micronaut framework is REST, so this library is scanned

Re: [DISCUSSION] IEP-88: CLI Tool

prints help > python -c - executes command > > What about other CLI tools that works with remote services? I can't remember > properly but do AWS, openshift or maybe GCP CLIs also supports shell mode? If > so, how it is organized? > > 19.05.2022 17:53, Aleksandr Pak

Re: [DISCUSSION] IEP-88: CLI Tool

I got it. What do you think about this proposal: - “ignite” prints help - “ignite shell” enters REPL Or - “ignite” prints help - “ignite-shell” enters REPL and it is a separate application I prefer the first varian but I would like to hear opinions of other community members. > On 19

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

serde for > serialization. We already have other serialization libraries as > dependencies and do we really need another one? > > On Thu, May 19, 2022 at 1:06 PM Aleksandr Pakhomov wrote: > >> Hi, Eduard >> >> Thank you for pointing out the 140 symbol column li

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

of proposed dependencies and >> allow to avoid possible vulnerabilities. Of course at the cost of >> manual actions. >> >> I understand that my statement is arguable. So I'll just wait for >> opinions of other community members. >> >> On Mon, May 16, 2022 a

Re: [DISCUSSION] IEP-87: Open API support for REST

Hi Roman, Thanks for the note. I’ve updated ‘Versioning’ paragraph with the example. > On 19 May 2022, at 10:12, Roman Puchkovskiy > wrote: > > Hi Aleksandr. > > Thank you for your effort, it looks interesting. I have a few > comments/questions on some little details. > > 1. About the

Re: [DISCUSSION] IEP-87: Open API support for REST

Yes, micronaut injection is going to be used but only for controllers. The border is MicronautFactory (see RestComponent constructor in the example). This factory declares beans that are needed for controllers. Each module declares its own factory. List of factories are put to RestComponent

Re: [DISCUSSION] IEP-87: Open API support for REST

Agreed. Thank you for comments, Roman. > On 19 May 2022, at 10:17, Roman Puchkovskiy > wrote: > > 3. In the table in the API section, there is this phrase: 'Update node > configuration with a given body.'. I suggest replacing 'Update' with > 'Patch' because 'update' could mean a full

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

not. It is just the number of handlers. > On 25 May 2022, at 17:46, Alexander Polovtcev wrote: > > Aleksandr, > > Can we use these annotations without the micronaut dependencies? If yes, > why do we need micronaut at all? > > On Mon, May 23, 2022 at 5:34 PM Aleksandr Pakhomov w

[CANCEL] [VOTE] Add micronaut dependency to Ignite 3

This vote is canceled. The IEP-87 [1] has to be adjusted. [1] https://cwiki.apache.org/confluence/display/IGNITE/IEP-87:+Open+API+support+for+REST

[VOTE] Add micronaut dependency to Ignite 3 (reopened)

Dear community, We’ve had a productive discussion about a micronaut dependency [1]. As a result, we’ve came to the conclusion that the security support in micronaut is a good reason to use this library. I am reopening the vote for adding the micronaut dependency to the rest module. Also,

Re: [DISCUSSION] IEP-88: CLI Tool

P-77%3A+Node+Join+Protocol+and+Initialization > > пт, 27 мая 2022 г. в 13:04, Aleksandr Pakhomov : >> >> Hi Roman, >> >> That is a good point. In the proposal I mean >> the analogue for existing ‘cluster init’. Maybe >> “distributed configuration” co

Re: [VOTE] Add micronaut dependency to Ignite 3

gh for this purpose I don't see reasons for these dependencies. >> We already have our own controllers for REST-like API's >> implementation. Why can't we just use Swagger annotations only in >> addition to our rest-api module? >> >> On Mon, May 23, 2022 at 8:08 PM Alek

Re: [RESULT][VOTE] Add swagger dependency to Ignite 3

fluence/display/IGNITE/Java+Code+Style+Guide#JavaCodeStyleGuide-2Using3rdpartylibraries> > > On Mon, May 30, 2022 at 12:33 PM Aleksandr Pakhomov <mailto:apk...@gmail.com>> wrote: >> >> Hello Igniters, >> >> The swagger dependency has been accepted. &g

Re: [VOTE] Add micronaut dependency to Ignite 3 (reopened)

. > On 30 May 2022, at 12:13, Alexander Polovtcev wrote: > > Aleksandr, > Thanks for the update, but can you please explain what security > capabilities are planned to be used? Maybe it should be included in the IEP > as well. > > On Sun, May 29, 2022 at 11:03 PM Aleksan

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

Yes, swagger-core has its own set of annotations [1] [1] https://github.com/swagger-api/swagger-core/wiki/Swagger-2.X---Annotations#quick-annotation-overview > On 23 May 2022, at 12:37, Alexander Polovtcev wrote: > > I'm not that scared of having a big library, I just believe that it might >

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

Yes, you are right about the usage of Jackson in another modules. So, the “replacement” is not an argument any more. > On 23 May 2022, at 12:37, Alexander Polovtcev wrote: > > My concern is that we will still use Jackson in other modules, like > sql-engine, for example. Or will you replace

Re: [VOTE] Add swagger dependency to Ignite 3

. > 2. Unintentional use of transitive dependencies. > > Best regards, > Ivan Pavlukhin > > чт, 26 мая 2022 г. в 00:46, Mikhail Pochatkin : >> >> +1 from me, de facto swagger standard within OpenApi. >> >> On Mon, May 23, 2022 at 7:57 PM Aleksandr Pakhomov

[RESULT][VOTE] Add micronaut dependency to Ignite 3 (reopened)

Hello Igniters, The micronaut dependency has been accepted. Java Code Style Guild is adjusted [1]. 8 - “+1” votes received. Here are +1 votes received: - Andrey Gura - Taras Ledkov - Tkalenko Kirill - Alexander Lapin - Ilya Korol - Vyacheslav Koptilin - Alexey - Semen Danilov Link to the

Re: [DISCUSSION] IEP-88: CLI Tool

er > variant, you are welcome. > 2. I think that Ignite CLI should also have default commands like "ignite > help", "ignite clear", "ignite exit" and etc. Could you please add topics > about these commands. > > On Thu, May 12, 2022 at 11:43 PM Aleksandr Pakh

Re: [DISCUSSION] IEP-88: CLI Tool

r > instance, I'm very excited with the wildfly-cli tool usage, however, > may be it has some drawbacks too. > > [1] https://kb.novaordis.com/index.php/WildFly_CLI_Scripting > > On Thu, 12 May 2022 at 23:43, Aleksandr Pakhomov wrote: >> >> Hello, Igniters. >>

[VOTE] Add swagger dependency to Ignite 3

Dear community, Discussion about 3rd party dependencies took place and I think it is time to vote if we agreed to include swagger dependency to the Ignite 3 or not. The exact list of dependencies could be fined in IEP-87 [1] (swagger-annotations, swagger-core, swagger-codegen-maven-plugin)

[VOTE] Add micronaut dependency to Ignite 3

Dear community, Micronaut-based REST server implementation was a hot topic we discussed in the previous week. So, I've separeted votes about swagger and micronaut. This vote is about adding micronaut to the Ignite 3. The exact list of dependencies could be fined in IEP-87 [1]

[VOTE] Add swagger dependency to Ignite 3

ger+dependency+to+Ignite+3=cursive> > On 23 May 2022, at 19:56, Aleksandr Pakhomov wrote: > > Dear community, > > Discussion about 3rd party dependencies took place > and I think it is time to vote if we agreed to include > swagger dependency to the Ignite 3 o

[DISCUSSION] Ignite 3 CLI name

Hi Igniters, I would like to discuss a name for Ignite 3 CLI [1]. Here are candidates from top to bottom. "Ignite CLI". The most general and straightforward. "Ignite Shell". It sounds good, only one point: "shell" is about interpretation, and interaction, but this Ignite CLI is not only about

Re: [DISCUSSION] IEP-88: CLI Tool

config. > > Was it intentional? > > [1] https://issues.apache.org/jira/browse/IGNITE-14871 > > ср, 25 мая 2022 г. в 18:12, Andrey Gura : >> >> Aleksandr, >> >> Both proposed options look good to me because both cases assume that a >> user must ex

[RESULT][VOTE] Add swagger dependency to Ignite 3

Hello Igniters, The swagger dependency has been accepted. 3 - “+1” votes received. 1 - “0.5” vote received. Here are +1 votes received: - Alexander Polovtcev - Andrey Gura - Ivan Pavlukhin Here is -0.5 vote received: - Ilya Kasnacheev (binding) Link to the voting thread -

Re: [DISCUSSION] IEP-87: Open API support for REST

> 5. The task about developer documentation should be added to the > issues list. The documentation is a readme.md file which will help an > Ignite developer to understand how to add a new endpoint, how to > generate API specification, etc. > > On Wed, May 11, 2022 at 1

[DISCUSSION] IEP-88: CLI Tool

Hello, Igniters. I’d like to start a discussion about Ignite 3 Command Line Tool [1]. The main value is to develop a user-friendly command-line tool with advanced completions and SQL REPL mode. The set of commands and parameters can be discussed. Questions and comments are welcomed. [1]

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

Hello, Igniters. I would like to start a discussion about Java Code Style Guide [1] changes that are going to be a part of IEP-87 [2] implementation. The set of libraries and frameworks that are going to be allowed to be used in production: - Micronaut for REST Server [3] -

Re: [ANNOUNCE] Apache Ignite 3.0.0 alpha 5: Code freeze

Hi Andrey, Could you please include this ticket into release? https://issues.apache.org/jira/browse/IGNITE-17126 Thanks > On 6 Jun 2022, at 17:56, Andrey Gura wrote: > > Igniters, > > our release schedule has shifted a bit. But it is

Re: [ANNOUNCE] Apache Ignite 3.0.0 alpha 5: Code freeze

Hi Andrey, As for CLI MVP, the planned timeline is today till 21:00. Probably, will be ready in an hour. Just waiting for CI build. Best regards, Aleksandr > On 6 Jun 2022, at 17:56, Andrey Gura wrote: > > Igniters, > > our release schedule has shifted a bit. But it is time for a code >

Re: Ignite 3 IEP

Thank you, I can create pages. > On 6 May 2022, at 14:17, Andrey Gura wrote: > > Permissions are granted. Please, check. > > On Fri, May 6, 2022 at 1:32 PM Aleksandr Pakhomov wrote: >> >> Sure, >> >> apkhmv >> >>> On 6 May

Re: Ignite 3 IEP

Sure, apkhmv > On 6 May 2022, at 13:05, Andrey Gura wrote: > > Aleksandr, > > could you please create an Apache Confluence account [1] and provide > your user name? > > 1. https://cwiki.apache.org/confluence/signup.action > > On Thu, May 5, 2022 at 7:2

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

://micronaut.io/docs/ [4] https://swagger.io [5] https://micronaut-projects.github.io/micronaut-serialization/snapshot/guide/ -- Best regards, Aleksandr Pakhomov

[DISCUSSION] IEP-87: Open API support for REST

Hello, Igniters. I’d like to start a discussion about Open API support for REST [1]. The main purpose of this improvement is to add the support of Open API specification by generating it from the source code. [1]

Ignite 3 IEP

...@gmail.com. Best regards, Aleksandr Pakhomov

Re: [VOTE] Ignite Packaging IEP

+1 > On 22 Aug 2022, at 17:04, Mikhail Pochatkin wrote: > > Thank you Anton, for this clarification. Yeah, all points in my previous > message and IEP only in the context of Ignite 3. > > On Mon, Aug 22, 2022 at 4:18 PM Anton Vinogradov wrote: > >> It looks like we need to mention that we

Re: [ANNOUNCE] SCOPE FREEZE for Apache Ignite 3.0.0 beta 1 RELEASE

Hi, Igniters. I would like to ask you to add a couple of tickets that are required for packaging: https://issues.apache.org/jira/browse/IGNITE-17781 https://issues.apache.org/jira/browse/IGNITE-17773

Re: [ANNOUNCE] Welcome Kirill Tkalenko as a new committer

Congratulations! > On 10 Oct 2022, at 22:15, Pavel Tupitsyn wrote: > > The Project Management Committee (PMC) for Apache Ignite > has invited Kirill Tkalenko to become a committer and we are pleased > to announce that they have accepted. > > Kirill is an active contributor and community

Re: Apache Ignite 3.0.0 beta 1 RELEASE [Time, Scope, Manager]

+1 > On 7 Oct 2022, at 23:05, Andrey Gura wrote: > > Hi, Igniters! > > It's time for a new release of Apache Ignite 3 beta 1. The expected > feature list consists of: > > - RPM and DEB packages: simplified installation and node management > with system services. > - Client's Partition

Re: [ANNOUNCE] New PMC member: Vyacheslav Koptilin

Congratulations! Well-deserved. > On 17 Aug 2022, at 17:34, Kseniya Romanova wrote: > > Hi Igniters! > > The Project Management Committee (PMC) for Apache Ignite has invited > Vyacheslav Koptilin to become a member of the PMC and we are pleased to > announce that he has accepted. > >

[DISCUSSION] Enable Doclint for Ignite 3

Hi Igniters, I'm working on the javadoc generation in gradle and I mentioned that now standard Doclint [1] is disabled in the maven javadoc generation. I wonder to know why it is disabled. I would suggest enabling Doclint by default because it is a recommended and standard approach to dealing

RE: [DISCUSSION] Enable Doclint for Ignite 3

Here is my PR with enabling DocLint https://github.com/apache/ignite-3/pull/1320 <https://github.com/apache/ignite-3/pull/1320> I wonder if someone can take a look. -- Best regards, Aleksandr On 2022/11/07 11:45:48 Aleksandr Pakhomov wrote: > Hi Igniters, > > I'm working

Re: [ANNOUNCE] SCOPE FREEZE for Apache Ignite 3.0.0 beta 1 RELEASE

Hi Igniters, I would like to ask you to add two more tickets to the beta1: - https://issues.apache.org/jira/browse/IGNITE-18036 - https://issues.apache.org/jira/browse/IGNITE-18025

RE: Re: [DISCUSSION] Add additional 3rd party libraries to Ignite 3

gt;> > > > >>> Hi, Ivan. > > > >>> > > > >>> I don't see any problems with adding *micronaut-security* in the > > > context > > > >>> of > > > >>> the IGNITE-18575 epic of security implementation. Mo

Re: [ANNOUNCE] Welcome Alexander Pakhomov as a new committer

Thank you! I will to my best to contribute to make Apache Ignite even better product. -- Best regards, Aleksandr > On 23 Feb 2023, at 17:06, Kseniya Romanova wrote: > > The Project Management Committee (PMC) for Apache Ignite has invited > Alexander Pakhomov to to become a committer and we

Re: [DISCUSSION] Add additional 3rd party libraries to Ignite 3

Hi Ivan, Why do we add reactor dependency? The Ignite 3 codebase uses java async API. Just wonder to know it we could escape the usage of third party async libraries. -- Best regards, Aleksandr > On 3 Feb 2023, at 10:51, Ivan Gagarkin wrote: > > I'd like to add a few 3rd party libraries to

Re: [DISCUSSION] IEP-105: SSL in Apache Ignite 3

Hi Mikhail, I have a question: Configuration snippets are just snippets or a list of all configration keys? -- Best regards, Aleksandr > On 31 May 2023, at 09:32, Mikhail Pochatkin wrote: > > Hi, Igniters! > > Please take a look at the proposal for SSL in Apache Ignite 3 [1]. > >

Re: [DISCUSSION] IEP-105: Basic Authentication in Apache Ignite 3

Hi, Mikhail > Then the REST client’s exchange with the node will follow the flow: > Client posts the client-id and client-secret to the token endpoint URL using > specified authentication type and receives an access token or error message. > At this point implementation should cache the token.

Re: New Apache Ignite PMC member: Nikita Amelchev

Congratulations! > On 21 Nov 2023, at 18:18, Dmitriy Pavlov wrote: > > Hello Igniters, > > The Project Management Committee (PMC) for Apache Ignite > has invited Nikita Amelchev to become a member of PMC and we are pleased > to announce that he has accepted. > > We appreciate his constant