Re: [ANNOUNCE] New committer: Mikhail Pochatkin

2024-05-07 Thread Roman Puchkovskiy
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 Commit

Re: [DISCUSSION] IEP-122 Thin client invoke/invokeAll cache operations

2024-05-07 Thread Pavel Tupitsyn
> So, we need to inform the client that the > error was caused by EntryProcessor. First option to do this: introduce > new error code, second option: use dedicated "success" flag. Thanks for the explanation. I lean towards a new error code for this. On Wed, May 8, 2024 at 9:05 AM Alex Plehanov w

Re: [ANNOUNCE] New committer: Mikhail Pochatkin

2024-05-07 Thread 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 Committee (PMC) for Apache Ignite >> has invited Mikhail Pochatkin to become a committer and we ar

Re: [ANNOUNCE] New committer: Roman Puchkovskiy

2024-05-07 Thread Zhenya Stanilovsky
Great ! My congrats too !   >Congrats, Roman! Well deserved! > >Thanks, >S. > >ср, 8 мая 2024г. в 07:28, Pavel Tupitsyn < ptupit...@apache.org >: >  >> Dear Igniters, >> >> The Project Management Committee (PMC) for Apache Ignite >> has invited Roman Puchkovskiy to become a committer and we are

Re: [ANNOUNCE] New committer: Mikhail Pochatkin

2024-05-07 Thread Вячеслав Коптилин
Congratulations, keep it going! Thanks, S. ср, 8 мая 2024 г. в 07:27, Pavel Tupitsyn : > Dear Igniters, > > The Project Management Committee (PMC) for Apache Ignite > has invited Mikhail Pochatkin to become a committer and we are pleased > to announce that they have accepted. > > Being a committ

Re: [ANNOUNCE] New committer: Roman Puchkovskiy

2024-05-07 Thread Вячеслав Коптилин
Congrats, Roman! Well deserved! Thanks, S. ср, 8 мая 2024 г. в 07:28, Pavel Tupitsyn : > Dear Igniters, > > The Project Management Committee (PMC) for Apache Ignite > has invited Roman Puchkovskiy to become a committer and we are pleased > to announce that they have accepted. > > Being a committ

Re: [DISCUSSION] IEP-122 Thin client invoke/invokeAll cache operations

2024-05-07 Thread Alex Plehanov
Sameiksha, send email to dev-unsubscr...@ignite.apache.org if you are no longer interested in Ignite dev list messages. ср, 8 мая 2024 г. в 08:06, sameiksha kiran k : > > Can u please remove from this mail chain , this is so much unwanted mails > in my inbox from ignite Apache mails > > On Tue, Ma

Re: [DISCUSSION] IEP-122 Thin client invoke/invokeAll cache operations

2024-05-07 Thread Alex Plehanov
Pavel, it's not about the stack trace, it's about the right exception to be thrown to the user. JCache specifies that if any exception is thrown by the EntryProcessor, this exception should be wrapped into EntryProcessorException. So, we need to inform the client that the error was caused by EntryP

Re: [DISCUSSION] IEP-122 Thin client invoke/invokeAll cache operations

2024-05-07 Thread sameiksha kiran k
Can u please remove from this mail chain , this is so much unwanted mails in my inbox from ignite Apache mails On Tue, May 7, 2024 at 10:35 PM Pavel Tupitsyn wrote: > > In case of such response we need some new > > error code to distinguish entry processor exceptions and general > client/server

Re: [DISCUSSION] IEP-122 Thin client invoke/invokeAll cache operations

2024-05-07 Thread Pavel Tupitsyn
> In case of such response we need some new > error code to distinguish entry processor exceptions and general client/server exceptions. I don't think we do this anywhere else (e.g. Compute). Full stack trace should be present in the server logs, or sent back to the client when sendServerException

[ANNOUNCE] New committer: Roman Puchkovskiy

2024-05-07 Thread Pavel Tupitsyn
Dear Igniters, The Project Management Committee (PMC) for Apache Ignite has invited Roman Puchkovskiy to become a committer and we are pleased to announce that they have accepted. Being a committer enables easier contribution to the project since there is no need to go via the patch submission pr

[ANNOUNCE] New committer: Mikhail Pochatkin

2024-05-07 Thread Pavel Tupitsyn
Dear Igniters, The Project Management Committee (PMC) for Apache Ignite has invited Mikhail Pochatkin to become a committer and we are pleased to announce that they have accepted. Being a committer enables easier contribution to the project since there is no need to go via the patch submission pr

[DISCUSSION] IEP-122 Thin client invoke/invokeAll cache operations

2024-05-07 Thread Alex Plehanov
Hi Igniters! I've prepared a proposal about implementation of invoke/invokeAll cache operations for thin clients. All proposed changes to the protocol and client API (currently for java thin client only) are described in IEP-122 [1] Please have a look and share your thoughts. [1] https://cwiki.

Re: I want to contribute to Apache ignite

2024-05-07 Thread Pavel Tupitsyn
Hello Tiago, Welcome to the Apache Ignite community! I've added you to the Contributors group in Jira, you should be able to work with tickets now. On Tue, May 7, 2024 at 7:12 PM Tiago Godinho wrote: > Hello, Everyone! > > My name is Tiago. I want to contribute to Ignite. I would like to > sta

I want to contribute to Apache ignite

2024-05-07 Thread Tiago Godinho
Hello, Everyone! My name is Tiago. I want to contribute to Ignite. I would like to start from IGNITE-22175. Please, help me to start contributing. My ASF JIRA username is tmgodinho. Regards, Tiago Marques Godinho

Re: [DISCUSSION] IEP-121: Data Streamer with Receiver (Ignite 3)

2024-05-07 Thread Pavel Tupitsyn
> 1. I think that the "streamData" method has quite a lot of parameters. Can > we reduce their number by introducing a holder class, for example > "ReceiverOptions" or "ReceiverConfig"? I think that's ok. The last 3 parameters are consistent with the Compute API. > 2. Can you please elaborate on