[jira] [Created] (IGNITE-14303) H2Cursor doesn't match to contract of the GridCursor.

Maksim Timonin created IGNITE-14303: --- Summary: H2Cursor doesn't match to contract of the GridCursor. Key: IGNITE-14303 URL: https://issues.apache.org/jira/browse/IGNITE-14303 Project: Ignite

[jira] [Created] (IGNITE-14302) Generated configuration classes break PMD suite in REST module

Ivan Bessonov created IGNITE-14302: -- Summary: Generated configuration classes break PMD suite in REST module Key: IGNITE-14302 URL: https://issues.apache.org/jira/browse/IGNITE-14302 Project: Ignite

Re: IGNITE-2399 : Asynchronous Acquire method in IgniteSemaphore

Hi Val, Thanks for taking a look. I have updated the PR, please see and let me know your thoughts and feedback. Regards, Atri On Thu, Mar 11, 2021 at 6:16 AM Valentin Kulichenko wrote: > > Atri, > > I've added my comments to the PR. > > -Val > > On Wed, Mar 10, 2021 at 2:44 AM Atri Sharma

[VOTE] Release Apache Ignite 2.10.0 RC2

Dear Community, I have uploaded a release candidate to: https://dist.apache.org/repos/dist/dev/ignite/2.10.0-rc2/ https://dist.apache.org/repos/dist/dev/ignite/packages_2.10.0-rc2/ The following staging can be used for testing:

Re: IGNITE-2399 : Asynchronous Acquire method in IgniteSemaphore

Atri, I've added my comments to the PR. -Val On Wed, Mar 10, 2021 at 2:44 AM Atri Sharma wrote: > I have just updated the PR: > > https://github.com/apache/ignite/pull/8820 > > Please review. > > On Wed, Mar 10, 2021 at 1:51 PM Atri Sharma wrote: > > > > Hi Val, > > > > Thank you for taking

Re: [DISCUSSION] IEP-69 The evolutionary release process

Ksenya, thanks for scheduling this so quickly! Guys, I hope we can make this discussion constructive. Please keep in mind that Ignite 3 is an ongoing project supported by multiple contributors, committers, and PMC members. Neglecting 6+ months of effort and suggesting that it's just "prototyping

Re: Re[2]: [DISCUSSION] Apache Ignite Release 2.10 (time, scope, manager)

Pavel, Thank you! I'll prepare a new rc shortly. On Wed, 10 Mar 2021 at 23:20, Pavel Tupitsyn wrote: > > Maxim, thanks! > I've cherry-picked IGNITE-14293. > > On Wed, Mar 10, 2021 at 10:05 PM Maxim Muzafarov wrote: > > > Pavel, > > > > Sorry, my bad. Entangled in my local branches during

Re: Re[2]: [DISCUSSION] Apache Ignite Release 2.10 (time, scope, manager)

Maxim, thanks! I've cherry-picked IGNITE-14293. On Wed, Mar 10, 2021 at 10:05 PM Maxim Muzafarov wrote: > Pavel, > > Sorry, my bad. Entangled in my local branches during trying to > cherry-pick related commits. > I've reverted this change. > > > On Wed, 10 Mar 2021 at 21:58, Pavel Tupitsyn

Re: Re[2]: [DISCUSSION] Apache Ignite Release 2.10 (time, scope, manager)

Pavel, Sorry, my bad. Entangled in my local branches during trying to cherry-pick related commits. I've reverted this change. On Wed, 10 Mar 2021 at 21:58, Pavel Tupitsyn wrote: > > Maxim, > > I see that you have already cherry-picked IGNITE-13979 - was that > intentional? > If we keep it,

Re: Re[2]: [DISCUSSION] Apache Ignite Release 2.10 (time, scope, manager)

Maxim, I see that you have already cherry-picked IGNITE-13979 - was that intentional? If we keep it, let's cherry-pick 14250 as well? On Wed, Mar 10, 2021 at 8:21 PM Maxim Muzafarov wrote: > Pavel, > > > I think it is better and safe to cherry-pick the `IGNITE-14293 .NET: > AffinityKey does

[jira] [Created] (IGNITE-14301) Authentication processor can hang all user management operation after server node reconnect

Mikhail Petrov created IGNITE-14301: --- Summary: Authentication processor can hang all user management operation after server node reconnect Key: IGNITE-14301 URL:

[jira] [Created] (IGNITE-14300) Rebalance speed as part of test result data

Dmitriy Sorokin created IGNITE-14300: Summary: Rebalance speed as part of test result data Key: IGNITE-14300 URL: https://issues.apache.org/jira/browse/IGNITE-14300 Project: Ignite Issue

Re: Re[2]: [DISCUSSION] Apache Ignite Release 2.10 (time, scope, manager)

Pavel, I think it is better and safe to cherry-pick the `IGNITE-14293 .NET: AffinityKey does not work` only. I will be very happy to accept your help with it. The IGNITE-13979 (.NET: Modernize examples) is very big and has some related issues too (most of them are fixed), so I think it is

Re: Re[2]: [DISCUSSION] Apache Ignite Release 2.10 (time, scope, manager)

Maxim, Sure, I can assist with cherry-picks. 13661 is fixed by 13979 , as indicated by the "fixed by" link in Jira and a comment. IGNITE-14293 .NET: AffinityKey does not work

Re: [DISCUSSION] IEP-69 The evolutionary release process

Let's make a quick call next week and try to find a compromise which can get the process moving: https://www.meetup.com/Moscow-Apache-Ignite-Meetup/events/276851588/ ср, 10 мар. 2021 г. в 16:27, Maxim Muzafarov : > Folks, > > > Agree, the discussion may be endless without compromises on all

Re: Re[2]: [DISCUSSION] Apache Ignite Release 2.10 (time, scope, manager)

Pavel, Can you assist a bit with the cherry-picking process of `.NET: AffinityKey does not work` IGNITE-14293? I'm not sure I can understand all the details of implementation and actually, I'm stuck a bit with the `.NET: Race condition in Events example` IGNITE-14250 [2] issue not sure what

[jira] [Created] (IGNITE-14299) .Net Service loses array type information in case .Net <-> .Net call

Nikolay Izhikov created IGNITE-14299: Summary: .Net Service loses array type information in case .Net <-> .Net call Key: IGNITE-14299 URL: https://issues.apache.org/jira/browse/IGNITE-14299

Re: Re[2]: [DISCUSSION] Apache Ignite Release 2.10 (time, scope, manager)

Maxim, No objections to those cherry-picks, please also include https://issues.apache.org/jira/browse/IGNITE-14293 Thanks! On Wed, Mar 10, 2021 at 10:54 AM Ilya Kasnacheev wrote: > Hello! > > Unless we do extra checks for Windows environment, I suggest merging > IGNITE-14284

Re: [DISCUSSION] IEP-69 The evolutionary release process

Folks, Agree, the discussion may be endless without compromises on all sides. I always think that if there is no consensus (and I see from the thread [1] that it's was no found) for such important decisions like product future development and releases AFS provides the voting procedure. Without

Re: IGNITE-2399 : Asynchronous Acquire method in IgniteSemaphore

I have just updated the PR: https://github.com/apache/ignite/pull/8820 Please review. On Wed, Mar 10, 2021 at 1:51 PM Atri Sharma wrote: > > Hi Val, > > Thank you for taking the time on this one. > > The main reason as to why I chose that signature was because I felt it > gave a clear idea of

[jira] [Created] (IGNITE-14298) DEVNOTES should contain clear instructions on how to run check-style.

Vyacheslav Koptilin created IGNITE-14298: Summary: DEVNOTES should contain clear instructions on how to run check-style. Key: IGNITE-14298 URL: https://issues.apache.org/jira/browse/IGNITE-14298

[jira] [Created] (IGNITE-14297) API to unregister HandlerProvider from network module

Sergey Chugunov created IGNITE-14297: Summary: API to unregister HandlerProvider from network module Key: IGNITE-14297 URL: https://issues.apache.org/jira/browse/IGNITE-14297 Project: Ignite

[jira] [Created] (IGNITE-14296) Classe

Sergey Chugunov created IGNITE-14296: Summary: Classe Key: IGNITE-14296 URL: https://issues.apache.org/jira/browse/IGNITE-14296 Project: Ignite Issue Type: Sub-task Reporter:

[jira] [Created] (IGNITE-14295) Message interface to be introduced

Sergey Chugunov created IGNITE-14295: Summary: Message interface to be introduced Key: IGNITE-14295 URL: https://issues.apache.org/jira/browse/IGNITE-14295 Project: Ignite Issue Type:

Re: IGNITE-2399 : Asynchronous Acquire method in IgniteSemaphore

Hi Val, Thank you for taking the time on this one. The main reason as to why I chose that signature was because I felt it gave a clear idea of the interface that the user should expect when using the method. So essentially, the user is providing a callback listener himself/herself and the API is