Re: [ANNOUNCE] New committer: Roman Puchkovskiy

> > > > > > > > Great ! My congrats too ! > > > > > > > > > > > > >Congrats, Roman! Well deserved! > > > > > > > >Thanks, > > > >S. > > > > > > > >ср, 8 мая 2024г. в 07:28, Pavel Tupitsyn < ptupit...@apac

Re: [ANNOUNCE] New committer: Mikhail Pochatkin

Congratulations! ср, 8 мая 2024 г. в 10:28, Zhenya Stanilovsky : > > > Great ! Good luck Mikhail ! > > > > >Congratulations, keep it going! > > > >Thanks, > >S. > > > >ср, 8 мая 2024г. в 07:27, Pavel Tupitsyn < ptupit...@apache.org >: > > > >> Dear Igniters, > >> > >> The Project Management

Re: [Announce] New committer: Iurii Gerzhedovich

Congratulations! вт, 13 февр. 2024 г. в 23:51, Dmitriy Pavlov : > > Dear Igniters, > > The Project Management Committee (PMC) for Apache Ignite > has invited Iurii Gerzhedovich to become a committer and we are pleased > to announce that he has accepted. > > Being a committer enables easier

Re: [DISCUSSION] IEP-112: Ignite 3. Criteria API queries

Hi Andrey. I believe IEP-112 is already taken, please consult https://cwiki.apache.org/confluence/display/IGNITE/Active+Proposals The lowest free number is 115. ср, 15 нояб. 2023 г. в 16:12, Andrey Novikov : > > Hi all, > > Please review "IEP-112: Ignite 3. Criteria API queries” proposal. > The

Re: [DISCUSSION] Service awareness for thin client.

Hi Vladimir. Sorry to intervene, but we have a clash with IEP numbers, there is already IEP-110 in Ignite 3, it was created on August, 1: https://cwiki.apache.org/confluence/display/IGNITE/IEP-110%3A+Schema+synchronization%3A+basic+schema+changes Is it possible to pick another number, while your

Re: [ANNOUNCE] Welcome Aleksandr Polovtsev as a new committer

Congratulations! пн, 21 авг. 2023 г. в 09:29, Pavel Tupitsyn : > > Congratulations, Aleksandr! Well deserved! > > On Mon, Aug 21, 2023 at 8:01 AM Kseniya Romanova > wrote: > > > Igniters! > > > > The Project Management Committee (PMC) for Apache Ignite has invited > > Aleksandr > > Polovtsev to

Re: [DISCUSSION] IEP-110: Schema synchronization: basic schema changes

Hi Andrey. Thanks for noting this, I've added the implementation tickets. чт, 27 июл. 2023 г. в 17:35, Andrey Gura : > > Hi, Roman. > > Thanks for IEP. Could you please also add tickets to the corresponding > section (see otghert IEP's for example). > > On Mon, Jul 24,

[DISCUSSION] IEP-110: Schema synchronization: basic schema changes

Hi Igniters! Please take a look at a proposal about the application of the Schema Synchronization framework to basic schema change types in Ignite 3 [1]. 1. https://cwiki.apache.org/confluence/display/IGNITE/IEP-110%3A+Schema+synchronization%3A+basic+schema+changes

Re: [DISCUSSION] IEP-108 Change column type feature in Ignite 3

Hi Andrey. Would it make sense to include the following to the list of type changes that do not require validation? 1. Increasing precision for a type containing a time component (TIME, DATETIME, TIMESTAMP) 2. Conversion of anything to VARCHAR (with enough capacity) ср, 14 июн. 2023 г. в 19:27,

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

Hi guys. The thing is that we already use reactor-core transitively (it is a dependency of scalecube-cluster-api and scalecube-cluster). We also use it directly (in just a few places) in the networking code. If we shade the one that comes with the micronaut, the other one will still remain. We

Ability to comment Confluence pages of Ignite project

Hi Igniters! I would like to contribute by commenting on Confluence pages (namely, I would like to add some comments to https://cwiki.apache.org/confluence/display/IGNITE/IEP-91%3A+Transaction+protocol ). Could you please provide me with the necessary permissions? My login is 'rpuch'. Roman

Re: Naming style for configuration properties defining durations in Ignite 3

t is difficult to > > navigate to relevant docs from there. > > > > I would go with point 3 - longer suffixes like Millis - to make it > > unambiguous. > > > > On Fri, Dec 23, 2022 at 10:06 AM Roman Puchkovskiy < > > roman.puchkovs...@gmail.com> wro

Naming style for configuration properties defining durations in Ignite 3

Hi Igniters! In Ignite 3, in configuration schemas, we have some properties that define durations/intervals (usually, these are timeout durations). Almost always they are defined without mentioning the duration unit, like this: /** Node join timeout. */ @Value(hasDefault = true) public int

Re: [DISCUSSION] IEP-91 Transaction protocol

Hi Alexei. Great proposal, thank you for your efforts. One thing that I noted is that the proposed IgniteInstructions interface contains parameterless commit*() and rollback*() methods. The transactions are not thread-bound, so there seems to be no implicit mechanism for the global

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

Congratulations, Kirill! пн, 10 окт. 2022 г. в 18:15, Pavel Tupitsyn : > > 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: [DISCUSSION] IEP-93: Ignite Packaging

Hi Mikhail. The suggestion looks great. I have a nitpick. In 'ignite3-cli' and 'ignite3-db' sections, Linux and Windows are explicitly mentioned, but MacOS is not. Does this mean that MacOS will not be supported in these cases, or it's just forgotten? Also, when it comes to scripts, could it be

Re: [ANNOUNCE] New PMC member: Vyacheslav Koptilin

Congratulations, Slava! ср, 17 авг. 2022 г. в 22:10, Aleksandr Pakhomov : > > 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

Re: [DISCUSSION] IEP-88: CLI Tool

> any confusion at all. > > What do you think? > > > On 27 May 2022, at 10:20, Roman Puchkovskiy > > wrote: > > > > Hi Aleksandr. > > > > There is a command named 'init' in your proposal. According to its > > description, it initializes the clu

Re: [DISCUSSION] IEP-88: CLI Tool

Hi Aleksandr. There is a command named 'init' in your proposal. According to its description, it initializes the cluster with a distributed configuration. I'm not sure how it's mapped to the existing commands. The thing is that currently, there is `ignite init` command that initializes (actually,

Re: [DISCUSSION] IEP-89: PITR

Hi Maksim. Do I understand correctly that 'consistent cut start' message always contains IDs of transactions to include, while 'consistent cut finish' message always contains IDs of transactions to exclude from the consistent cut? (At least, this is the impression I got from the example of

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

with a given body.'. I suggest replacing 'Update' with 'Patch' because 'update' could mean a full replacement, and 'patch' makes it more specific. Same relates to 'Update cluster configuration with a given body.'. чт, 19 мая 2022 г. в 11:12, Roman Puchkovskiy : > > Hi Aleksandr. > &g

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

Hi Aleksandr. Thank you for your effort, it looks interesting. I have a few comments/questions on some little details. 1. About the paragraph named 'Versioning'. Could you please elaborate what is the difference between 'API version' and 'specification version'? Both might have 'breaking

Re: Re[4]: Apache Ignite 2.13 RELEASE [Time, Scope, Manager]

Roman. > > Vulnerable Spring Boot is used in Ignite extensions. AI 2.13 releases > ignite-parent that will be used for extensions to share versions. I > will cherry-pick the patch. > > Thank you. > > пн, 18 апр. 2022 г. в 15:00, Roman Puchkovskiy : > > > > Hi Ign

Re: [DISCUSSION] Removing extensions for obsolete Ignite Spring Data integrations.

=6533271=buildResultsDiv=IgniteExtensions_Tests_RunAllTests пн, 18 апр. 2022 г. в 14:29, Maxim Muzafarov : > > Hello Roman, > > +1 to your suggestion. > If you need any help with a review, please let me know. > > On Mon, 18 Apr 2022 at 13:17, Roman Puchkovskiy >

Re: Re[4]: Apache Ignite 2.13 RELEASE [Time, Scope, Manager]

Hi Igniters. A fix for CVE-2022-22965 [1] vulnerability was merged to master branch recently, Jira issue is [2]. I'm not sure whether this is a blocker, but the vulnerability seems to be pretty bad. Should it be cherry-picked to release 2.13? [1] -

Re: [DISCUSSION] Removing extensions for obsolete Ignite Spring Data integrations.

Hi guys. This thread has been hanging for quite some time (no pun intended). While it was hanging, CVE-2022-22965 [1] was discovered which makes it extremely dangerous to have vulnerable versions of Spring as dependencies. As discussed, ignite-extensions has 3 versions of spring-data

Re: [VOTE] @Nullable/@NotNull annotation usage in Ignite 3

+1 to option 2 чт, 13 янв. 2022 г. в 15:58, Sergey : > > +1 for option2 (only @Nullable) > > Best regards, > Sergey Kosarev. > > > чт, 13 янв. 2022 г. в 13:25, Alexander Polovtcev : > > > Dear Igniters, > > > > In this thread > >

Re: [ANNOUNCE] Welcome Semyon Danilov as a new committer

Semyon, well done and congratulations! ср, 1 дек. 2021 г. в 15:Congrats and well done! ср, 1 дек. 2021 г. в 15:56, Kseniya Romanova : > > Semyon, congrats! > > ср, 1 дек. 2021 г. в 12:51, Andrey Gura : > > > I'm sorry for the mistake. Of course please join me in welcoming > > **Semyon**, and

Request for contributor permission

Hello Ignite community! My name is Roman Puchkovskiy. I would like to contribute to Apache Ignite. My Apache JIRA username is rpuch. Could you please provide me with the corresponding permission? Roman Puchkovskiy