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

[Maxim Muzafarov]

Denis,


I've checked the permissions now I can make changes.

> I'm encouraging you to work with Kseniya's technical editors

Thank you, we have already started working together.

On Thu, 18 Mar 2021 at 03:00, Denis Magda  wrote:
>
> Maxim,
>
> I had to grant you admin access in the blogging settings. No you should be
> able to create an article and invite other members (log in with your apache
> ID): https://blogs.apache.org/roller-ui/authoring/members!save.rol
>
> Like the blog. (if you haven't done this yet, I'm encouraging you to work
> with Kseniya's technical editors who can suggest style and flow-related
> changes).
>
> -
> Denis
>
>
> On Wed, Mar 17, 2021 at 12:44 PM Maxim Muzafarov  wrote:
>
> > Denis,
> >
> > I'm getting the following error while trying to create a new Weblog
> > > Sorry, the blog administrator has disabled creation of new blogs.
> >
> > By the way, Nikita, Denis
> >
> > Can you review my blog post, please?
> >
> > https://github.com/Mmuzaf/mmuzaf.github.io/blob/main/_post/Release_Newsletter_210.md
> >
> >
> > On Wed, 17 Mar 2021 at 19:32, Denis Magda  wrote:
> > >
> > > Maxim,
> > >
> > > Check one more time. The infra instruction that you shared says a
> > contributor needs to be in the Admin group in JIRA to get write access to
> > the blog. I've added you to the Admin group.
> > > -
> > > Denis
> > >
> > >
> > >
> > > On Wed, Mar 17, 2021 at 12:00 PM Maxim Muzafarov 
> > wrote:
> > >>
> > >> Denis,
> > >>
> > >>
> > >> I'd like to create a post on the blogs.apache.org news feed with the
> > >> 2.10 release news. Do I need additional privileges to do this?
> > >>
> > >> According to the wiki page [1] after login with my credentials, I
> > >> should see the `add post` button, however, I can't find it on the main
> > >> page. Am I missing something?
> > >>
> > >>
> > >>
> > >> [1] https://infra.apache.org/project-blogs
> > >> [2] https://blogs.apache.org/ignite/
> > >>
> > >> On Wed, 17 Mar 2021 at 13:43, Pavel Tupitsyn 
> > wrote:
> > >> >
> > >> > Maxim,
> > >> >
> > >> > I've prepared a blog post about Ignite.NET changes [1],
> > >> > please link it in the main post.
> > >> >
> > >> > [1] https://ptupitsyn.github.io/Whats-New-In-Ignite-Net-2.10/
> > >> >
> > >> > On Tue, Mar 16, 2021 at 5:15 PM Maxim Muzafarov 
> > wrote:
> > >> >
> > >> > > Denis,
> > >> > >
> > >> > >
> > >> > > Thank you. I'll prepare a blog post notes for the major 2.10
> > features.
> > >> > > The release hasn't been announced yet, some artefacts still waiting
> > to
> > >> > > be published. Hope everything will be ready by the end of this week.
> > >> > >
> > >> > >
> > >> > > > Btw, don't we want to arrange a meetup gathering for Virtual or
> > >> > > Russian-speaking meetup or both?
> > >> > >
> > >> > > It depends on our goals. If we want to promote Ignite Summit 2021,
> > so
> > >> > > the English-speaking meetup makes sense.
> > >> > >
> > >> > > On Tue, 16 Mar 2021 at 16:00, Denis Magda 
> > wrote:
> > >> > > >
> > >> > > > Hi Maxim,
> > >> > > >
> > >> > > > Ideally, a blog post should be published together with the
> > announcement
> > >> > > > email. So that the readers can learn more details from the
> > article.
> > >> > > Anyway,
> > >> > > > you can post it later for 2.10 as long as the release is already
> > >> > > completed.
> > >> > > >
> > >> > > > Btw, don't we want to arrange a meetup gathering for Virtual or
> > >> > > > Russian-speaking meetup, or both?
> > >> > > >
> > >> > > > -
> > >> > > > Denis
> > >> > > >
> > >> > > >
> > >> > > > On Mon, Mar 15, 2021 at 8:55 PM Maxim Muzafarov <
> > mmu...@apache.org>
> > >> > > wrote:
> > >> > > >
> > >> > > > > Folks,
> > >> > > > >
> > >> > > > > I've done almost all the release steps with publishing accepted
> > >> > > changes.
> > >> > > > > What should I do with an announcement blog post for
> > blogs.apache.org?
> > >> > > > > Should it also be prepared prior to an announcement message?
> > >> > > > >
> > >> > > > > On Thu, 11 Mar 2021 at 00:10, Maxim Muzafarov <
> > mmu...@apache.org>
> > >> > > wrote:
> > >> > > > > >
> > >> > > > > > Pavel,
> > >> > > > > >
> > >> > > > > > Thank you! I'll prepare a new rc shortly.
> > >> > > > > >
> > >> > > > > > On Wed, 10 Mar 2021 at 23:20, Pavel Tupitsyn <
> > ptupit...@apache.org>
> > >> > > > > wrote:
> > >> > > > > > >
> > >> > > > > > > Maxim, thanks!
> > >> > > > > > > I've cherry-picked IGNITE-14293.
> > >> > > > > > >
> > >> > > > > > > On Wed, Mar 10, 2021 at 10:05 PM Maxim Muzafarov <
> > >> > > mmu...@apache.org>
> > >> > > > > 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 <
> > >> > > ptupit...@apache.org>
> > >> > > > > wrote:
> > >> > > > > > > > >
> > >> > > > 

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

[Denis Magda]

Maxim,

I had to grant you admin access in the blogging settings. No you should be
able to create an article and invite other members (log in with your apache
ID): https://blogs.apache.org/roller-ui/authoring/members!save.rol

Like the blog. (if you haven't done this yet, I'm encouraging you to work
with Kseniya's technical editors who can suggest style and flow-related
changes).

-
Denis


On Wed, Mar 17, 2021 at 12:44 PM Maxim Muzafarov  wrote:

> Denis,
>
> I'm getting the following error while trying to create a new Weblog
> > Sorry, the blog administrator has disabled creation of new blogs.
>
> By the way, Nikita, Denis
>
> Can you review my blog post, please?
>
> https://github.com/Mmuzaf/mmuzaf.github.io/blob/main/_post/Release_Newsletter_210.md
>
>
> On Wed, 17 Mar 2021 at 19:32, Denis Magda  wrote:
> >
> > Maxim,
> >
> > Check one more time. The infra instruction that you shared says a
> contributor needs to be in the Admin group in JIRA to get write access to
> the blog. I've added you to the Admin group.
> > -
> > Denis
> >
> >
> >
> > On Wed, Mar 17, 2021 at 12:00 PM Maxim Muzafarov 
> wrote:
> >>
> >> Denis,
> >>
> >>
> >> I'd like to create a post on the blogs.apache.org news feed with the
> >> 2.10 release news. Do I need additional privileges to do this?
> >>
> >> According to the wiki page [1] after login with my credentials, I
> >> should see the `add post` button, however, I can't find it on the main
> >> page. Am I missing something?
> >>
> >>
> >>
> >> [1] https://infra.apache.org/project-blogs
> >> [2] https://blogs.apache.org/ignite/
> >>
> >> On Wed, 17 Mar 2021 at 13:43, Pavel Tupitsyn 
> wrote:
> >> >
> >> > Maxim,
> >> >
> >> > I've prepared a blog post about Ignite.NET changes [1],
> >> > please link it in the main post.
> >> >
> >> > [1] https://ptupitsyn.github.io/Whats-New-In-Ignite-Net-2.10/
> >> >
> >> > On Tue, Mar 16, 2021 at 5:15 PM Maxim Muzafarov 
> wrote:
> >> >
> >> > > Denis,
> >> > >
> >> > >
> >> > > Thank you. I'll prepare a blog post notes for the major 2.10
> features.
> >> > > The release hasn't been announced yet, some artefacts still waiting
> to
> >> > > be published. Hope everything will be ready by the end of this week.
> >> > >
> >> > >
> >> > > > Btw, don't we want to arrange a meetup gathering for Virtual or
> >> > > Russian-speaking meetup or both?
> >> > >
> >> > > It depends on our goals. If we want to promote Ignite Summit 2021,
> so
> >> > > the English-speaking meetup makes sense.
> >> > >
> >> > > On Tue, 16 Mar 2021 at 16:00, Denis Magda 
> wrote:
> >> > > >
> >> > > > Hi Maxim,
> >> > > >
> >> > > > Ideally, a blog post should be published together with the
> announcement
> >> > > > email. So that the readers can learn more details from the
> article.
> >> > > Anyway,
> >> > > > you can post it later for 2.10 as long as the release is already
> >> > > completed.
> >> > > >
> >> > > > Btw, don't we want to arrange a meetup gathering for Virtual or
> >> > > > Russian-speaking meetup, or both?
> >> > > >
> >> > > > -
> >> > > > Denis
> >> > > >
> >> > > >
> >> > > > On Mon, Mar 15, 2021 at 8:55 PM Maxim Muzafarov <
> mmu...@apache.org>
> >> > > wrote:
> >> > > >
> >> > > > > Folks,
> >> > > > >
> >> > > > > I've done almost all the release steps with publishing accepted
> >> > > changes.
> >> > > > > What should I do with an announcement blog post for
> blogs.apache.org?
> >> > > > > Should it also be prepared prior to an announcement message?
> >> > > > >
> >> > > > > On Thu, 11 Mar 2021 at 00:10, Maxim Muzafarov <
> mmu...@apache.org>
> >> > > wrote:
> >> > > > > >
> >> > > > > > Pavel,
> >> > > > > >
> >> > > > > > Thank you! I'll prepare a new rc shortly.
> >> > > > > >
> >> > > > > > On Wed, 10 Mar 2021 at 23:20, Pavel Tupitsyn <
> ptupit...@apache.org>
> >> > > > > wrote:
> >> > > > > > >
> >> > > > > > > Maxim, thanks!
> >> > > > > > > I've cherry-picked IGNITE-14293.
> >> > > > > > >
> >> > > > > > > On Wed, Mar 10, 2021 at 10:05 PM Maxim Muzafarov <
> >> > > mmu...@apache.org>
> >> > > > > 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 <
> >> > > ptupit...@apache.org>
> >> > > > > wrote:
> >> > > > > > > > >
> >> > > > > > > > > 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 <
> >> > > mmu...@apache.org
> >> > > > > >
> >> > > > > > > > wrote:
> >> > > > > > > > >
> >> > > > > > > > > > Pavel,
> >> > > > > > > > > >
> >> > > > > > > > > >
> >> > > > > > > > > > I think it 

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

[Maxim Muzafarov]

Denis,

I'm getting the following error while trying to create a new Weblog
> Sorry, the blog administrator has disabled creation of new blogs.

By the way, Nikita, Denis

Can you review my blog post, please?
https://github.com/Mmuzaf/mmuzaf.github.io/blob/main/_post/Release_Newsletter_210.md


On Wed, 17 Mar 2021 at 19:32, Denis Magda  wrote:
>
> Maxim,
>
> Check one more time. The infra instruction that you shared says a contributor 
> needs to be in the Admin group in JIRA to get write access to the blog. I've 
> added you to the Admin group.
> -
> Denis
>
>
>
> On Wed, Mar 17, 2021 at 12:00 PM Maxim Muzafarov  wrote:
>>
>> Denis,
>>
>>
>> I'd like to create a post on the blogs.apache.org news feed with the
>> 2.10 release news. Do I need additional privileges to do this?
>>
>> According to the wiki page [1] after login with my credentials, I
>> should see the `add post` button, however, I can't find it on the main
>> page. Am I missing something?
>>
>>
>>
>> [1] https://infra.apache.org/project-blogs
>> [2] https://blogs.apache.org/ignite/
>>
>> On Wed, 17 Mar 2021 at 13:43, Pavel Tupitsyn  wrote:
>> >
>> > Maxim,
>> >
>> > I've prepared a blog post about Ignite.NET changes [1],
>> > please link it in the main post.
>> >
>> > [1] https://ptupitsyn.github.io/Whats-New-In-Ignite-Net-2.10/
>> >
>> > On Tue, Mar 16, 2021 at 5:15 PM Maxim Muzafarov  wrote:
>> >
>> > > Denis,
>> > >
>> > >
>> > > Thank you. I'll prepare a blog post notes for the major 2.10 features.
>> > > The release hasn't been announced yet, some artefacts still waiting to
>> > > be published. Hope everything will be ready by the end of this week.
>> > >
>> > >
>> > > > Btw, don't we want to arrange a meetup gathering for Virtual or
>> > > Russian-speaking meetup or both?
>> > >
>> > > It depends on our goals. If we want to promote Ignite Summit 2021, so
>> > > the English-speaking meetup makes sense.
>> > >
>> > > On Tue, 16 Mar 2021 at 16:00, Denis Magda  wrote:
>> > > >
>> > > > Hi Maxim,
>> > > >
>> > > > Ideally, a blog post should be published together with the announcement
>> > > > email. So that the readers can learn more details from the article.
>> > > Anyway,
>> > > > you can post it later for 2.10 as long as the release is already
>> > > completed.
>> > > >
>> > > > Btw, don't we want to arrange a meetup gathering for Virtual or
>> > > > Russian-speaking meetup, or both?
>> > > >
>> > > > -
>> > > > Denis
>> > > >
>> > > >
>> > > > On Mon, Mar 15, 2021 at 8:55 PM Maxim Muzafarov 
>> > > wrote:
>> > > >
>> > > > > Folks,
>> > > > >
>> > > > > I've done almost all the release steps with publishing accepted
>> > > changes.
>> > > > > What should I do with an announcement blog post for blogs.apache.org?
>> > > > > Should it also be prepared prior to an announcement message?
>> > > > >
>> > > > > On Thu, 11 Mar 2021 at 00:10, Maxim Muzafarov 
>> > > wrote:
>> > > > > >
>> > > > > > 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 <
>> > > mmu...@apache.org>
>> > > > > 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 <
>> > > ptupit...@apache.org>
>> > > > > wrote:
>> > > > > > > > >
>> > > > > > > > > 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 <
>> > > mmu...@apache.org
>> > > > > >
>> > > > > > > > wrote:
>> > > > > > > > >
>> > > > > > > > > > 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
>> > > > > better
>> > > > > > > > > > here to postpone it to the next release and give it a bit 
>> > > > > > > > > > of
>> > > > > time for
>> > > > > > > > > > the self-stabilization process :-)
>> > > > > > > > > >
>> > > > > > > > > > On Wed, 10 Mar 2021 at 20:17, Pavel Tupitsyn <
>> > > > > ptupit...@apache.org>
>> > > > > > > 

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

[Denis Magda]

Maxim,

Check one more time. The infra instruction that you shared says a
contributor needs to be in the Admin group in JIRA to get write access to
the blog. I've added you to the Admin group.
-
Denis



On Wed, Mar 17, 2021 at 12:00 PM Maxim Muzafarov  wrote:

> Denis,
>
>
> I'd like to create a post on the blogs.apache.org news feed with the
> 2.10 release news. Do I need additional privileges to do this?
>
> According to the wiki page [1] after login with my credentials, I
> should see the `add post` button, however, I can't find it on the main
> page. Am I missing something?
>
>
>
> [1] https://infra.apache.org/project-blogs
> [2] https://blogs.apache.org/ignite/
>
> On Wed, 17 Mar 2021 at 13:43, Pavel Tupitsyn  wrote:
> >
> > Maxim,
> >
> > I've prepared a blog post about Ignite.NET changes [1],
> > please link it in the main post.
> >
> > [1] https://ptupitsyn.github.io/Whats-New-In-Ignite-Net-2.10/
> >
> > On Tue, Mar 16, 2021 at 5:15 PM Maxim Muzafarov 
> wrote:
> >
> > > Denis,
> > >
> > >
> > > Thank you. I'll prepare a blog post notes for the major 2.10 features.
> > > The release hasn't been announced yet, some artefacts still waiting to
> > > be published. Hope everything will be ready by the end of this week.
> > >
> > >
> > > > Btw, don't we want to arrange a meetup gathering for Virtual or
> > > Russian-speaking meetup or both?
> > >
> > > It depends on our goals. If we want to promote Ignite Summit 2021, so
> > > the English-speaking meetup makes sense.
> > >
> > > On Tue, 16 Mar 2021 at 16:00, Denis Magda  wrote:
> > > >
> > > > Hi Maxim,
> > > >
> > > > Ideally, a blog post should be published together with the
> announcement
> > > > email. So that the readers can learn more details from the article.
> > > Anyway,
> > > > you can post it later for 2.10 as long as the release is already
> > > completed.
> > > >
> > > > Btw, don't we want to arrange a meetup gathering for Virtual or
> > > > Russian-speaking meetup, or both?
> > > >
> > > > -
> > > > Denis
> > > >
> > > >
> > > > On Mon, Mar 15, 2021 at 8:55 PM Maxim Muzafarov 
> > > wrote:
> > > >
> > > > > Folks,
> > > > >
> > > > > I've done almost all the release steps with publishing accepted
> > > changes.
> > > > > What should I do with an announcement blog post for
> blogs.apache.org?
> > > > > Should it also be prepared prior to an announcement message?
> > > > >
> > > > > On Thu, 11 Mar 2021 at 00:10, Maxim Muzafarov 
> > > wrote:
> > > > > >
> > > > > > Pavel,
> > > > > >
> > > > > > Thank you! I'll prepare a new rc shortly.
> > > > > >
> > > > > > On Wed, 10 Mar 2021 at 23:20, Pavel Tupitsyn <
> ptupit...@apache.org>
> > > > > wrote:
> > > > > > >
> > > > > > > Maxim, thanks!
> > > > > > > I've cherry-picked IGNITE-14293.
> > > > > > >
> > > > > > > On Wed, Mar 10, 2021 at 10:05 PM Maxim Muzafarov <
> > > mmu...@apache.org>
> > > > > 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 <
> > > ptupit...@apache.org>
> > > > > wrote:
> > > > > > > > >
> > > > > > > > > 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 <
> > > mmu...@apache.org
> > > > > >
> > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > 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
> > > > > better
> > > > > > > > > > here to postpone it to the next release and give it a
> bit of
> > > > > time for
> > > > > > > > > > the self-stabilization process :-)
> > > > > > > > > >
> > > > > > > > > > On Wed, 10 Mar 2021 at 20:17, Pavel Tupitsyn <
> > > > > ptupit...@apache.org>
> > > > > > > > wrote:
> > > > > > > > > > >
> > > > > > > > > > > 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 is quite
> an
> > > > > unpleasant
> > > > > > > > > > regression,
> > > > > > > > > > > I 

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

[Maxim Muzafarov]

Denis,


I'd like to create a post on the blogs.apache.org news feed with the
2.10 release news. Do I need additional privileges to do this?

According to the wiki page [1] after login with my credentials, I
should see the `add post` button, however, I can't find it on the main
page. Am I missing something?



[1] https://infra.apache.org/project-blogs
[2] https://blogs.apache.org/ignite/

On Wed, 17 Mar 2021 at 13:43, Pavel Tupitsyn  wrote:
>
> Maxim,
>
> I've prepared a blog post about Ignite.NET changes [1],
> please link it in the main post.
>
> [1] https://ptupitsyn.github.io/Whats-New-In-Ignite-Net-2.10/
>
> On Tue, Mar 16, 2021 at 5:15 PM Maxim Muzafarov  wrote:
>
> > Denis,
> >
> >
> > Thank you. I'll prepare a blog post notes for the major 2.10 features.
> > The release hasn't been announced yet, some artefacts still waiting to
> > be published. Hope everything will be ready by the end of this week.
> >
> >
> > > Btw, don't we want to arrange a meetup gathering for Virtual or
> > Russian-speaking meetup or both?
> >
> > It depends on our goals. If we want to promote Ignite Summit 2021, so
> > the English-speaking meetup makes sense.
> >
> > On Tue, 16 Mar 2021 at 16:00, Denis Magda  wrote:
> > >
> > > Hi Maxim,
> > >
> > > Ideally, a blog post should be published together with the announcement
> > > email. So that the readers can learn more details from the article.
> > Anyway,
> > > you can post it later for 2.10 as long as the release is already
> > completed.
> > >
> > > Btw, don't we want to arrange a meetup gathering for Virtual or
> > > Russian-speaking meetup, or both?
> > >
> > > -
> > > Denis
> > >
> > >
> > > On Mon, Mar 15, 2021 at 8:55 PM Maxim Muzafarov 
> > wrote:
> > >
> > > > Folks,
> > > >
> > > > I've done almost all the release steps with publishing accepted
> > changes.
> > > > What should I do with an announcement blog post for blogs.apache.org?
> > > > Should it also be prepared prior to an announcement message?
> > > >
> > > > On Thu, 11 Mar 2021 at 00:10, Maxim Muzafarov 
> > wrote:
> > > > >
> > > > > 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 <
> > mmu...@apache.org>
> > > > 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 <
> > ptupit...@apache.org>
> > > > wrote:
> > > > > > > >
> > > > > > > > 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 <
> > mmu...@apache.org
> > > > >
> > > > > > > wrote:
> > > > > > > >
> > > > > > > > > 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
> > > > better
> > > > > > > > > here to postpone it to the next release and give it a bit of
> > > > time for
> > > > > > > > > the self-stabilization process :-)
> > > > > > > > >
> > > > > > > > > On Wed, 10 Mar 2021 at 20:17, Pavel Tupitsyn <
> > > > ptupit...@apache.org>
> > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > 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 is quite an
> > > > unpleasant
> > > > > > > > > regression,
> > > > > > > > > > I think we should include it in the release. It CAN be
> > included
> > > > > > > without
> > > > > > > > > 14250 and 13979.
> > > > > > > > > >
> > > > > > > > > > 14250 does not make sense without 13979.
> > > > > > > > > >
> > > > > > > > > > Ultimately, the question is - do we want to include 13979
> > > > (.NET:
> > > > > > > > > Modernize examples),
> > > > > > > > > > or not. Thoughts?
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > On Wed, Mar 10, 2021 at 7:45 PM Maxim Muzafarov <
> > > > mmu...@apache.org>
> > > > > > > > > wrote:
> > > > > > > > > >>
> > > > > > > > 

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

[Pavel Tupitsyn]

Maxim,

I've prepared a blog post about Ignite.NET changes [1],
please link it in the main post.

[1] https://ptupitsyn.github.io/Whats-New-In-Ignite-Net-2.10/

On Tue, Mar 16, 2021 at 5:15 PM Maxim Muzafarov  wrote:

> Denis,
>
>
> Thank you. I'll prepare a blog post notes for the major 2.10 features.
> The release hasn't been announced yet, some artefacts still waiting to
> be published. Hope everything will be ready by the end of this week.
>
>
> > Btw, don't we want to arrange a meetup gathering for Virtual or
> Russian-speaking meetup or both?
>
> It depends on our goals. If we want to promote Ignite Summit 2021, so
> the English-speaking meetup makes sense.
>
> On Tue, 16 Mar 2021 at 16:00, Denis Magda  wrote:
> >
> > Hi Maxim,
> >
> > Ideally, a blog post should be published together with the announcement
> > email. So that the readers can learn more details from the article.
> Anyway,
> > you can post it later for 2.10 as long as the release is already
> completed.
> >
> > Btw, don't we want to arrange a meetup gathering for Virtual or
> > Russian-speaking meetup, or both?
> >
> > -
> > Denis
> >
> >
> > On Mon, Mar 15, 2021 at 8:55 PM Maxim Muzafarov 
> wrote:
> >
> > > Folks,
> > >
> > > I've done almost all the release steps with publishing accepted
> changes.
> > > What should I do with an announcement blog post for blogs.apache.org?
> > > Should it also be prepared prior to an announcement message?
> > >
> > > On Thu, 11 Mar 2021 at 00:10, Maxim Muzafarov 
> wrote:
> > > >
> > > > 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 <
> mmu...@apache.org>
> > > 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 <
> ptupit...@apache.org>
> > > wrote:
> > > > > > >
> > > > > > > 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 <
> mmu...@apache.org
> > > >
> > > > > > wrote:
> > > > > > >
> > > > > > > > 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
> > > better
> > > > > > > > here to postpone it to the next release and give it a bit of
> > > time for
> > > > > > > > the self-stabilization process :-)
> > > > > > > >
> > > > > > > > On Wed, 10 Mar 2021 at 20:17, Pavel Tupitsyn <
> > > ptupit...@apache.org>
> > > > > > wrote:
> > > > > > > > >
> > > > > > > > > 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 is quite an
> > > unpleasant
> > > > > > > > regression,
> > > > > > > > > I think we should include it in the release. It CAN be
> included
> > > > > > without
> > > > > > > > 14250 and 13979.
> > > > > > > > >
> > > > > > > > > 14250 does not make sense without 13979.
> > > > > > > > >
> > > > > > > > > Ultimately, the question is - do we want to include 13979
> > > (.NET:
> > > > > > > > Modernize examples),
> > > > > > > > > or not. Thoughts?
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On Wed, Mar 10, 2021 at 7:45 PM Maxim Muzafarov <
> > > mmu...@apache.org>
> > > > > > > > wrote:
> > > > > > > > >>
> > > > > > > > >> 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 exactly I can exclude from the commit to
> resolve
> > > > > > > > >> conflicts since it has some of them with the 2.10 branch.
> I'm
> > > > > > worried
> > > > > > > > >> about missing some important parts of the code.
> > > > > > > > >>
> > > > > > > > >>
> > > > > > > 

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

[Maxim Muzafarov]

Denis,


Thank you. I'll prepare a blog post notes for the major 2.10 features.
The release hasn't been announced yet, some artefacts still waiting to
be published. Hope everything will be ready by the end of this week.


> Btw, don't we want to arrange a meetup gathering for Virtual or 
> Russian-speaking meetup or both?

It depends on our goals. If we want to promote Ignite Summit 2021, so
the English-speaking meetup makes sense.

On Tue, 16 Mar 2021 at 16:00, Denis Magda  wrote:
>
> Hi Maxim,
>
> Ideally, a blog post should be published together with the announcement
> email. So that the readers can learn more details from the article. Anyway,
> you can post it later for 2.10 as long as the release is already completed.
>
> Btw, don't we want to arrange a meetup gathering for Virtual or
> Russian-speaking meetup, or both?
>
> -
> Denis
>
>
> On Mon, Mar 15, 2021 at 8:55 PM Maxim Muzafarov  wrote:
>
> > Folks,
> >
> > I've done almost all the release steps with publishing accepted changes.
> > What should I do with an announcement blog post for blogs.apache.org?
> > Should it also be prepared prior to an announcement message?
> >
> > On Thu, 11 Mar 2021 at 00:10, Maxim Muzafarov  wrote:
> > >
> > > 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 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, 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 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
> > better
> > > > > > > here to postpone it to the next release and give it a bit of
> > time for
> > > > > > > the self-stabilization process :-)
> > > > > > >
> > > > > > > On Wed, 10 Mar 2021 at 20:17, Pavel Tupitsyn <
> > ptupit...@apache.org>
> > > > > wrote:
> > > > > > > >
> > > > > > > > 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 is quite an
> > unpleasant
> > > > > > > regression,
> > > > > > > > I think we should include it in the release. It CAN be included
> > > > > without
> > > > > > > 14250 and 13979.
> > > > > > > >
> > > > > > > > 14250 does not make sense without 13979.
> > > > > > > >
> > > > > > > > Ultimately, the question is - do we want to include 13979
> > (.NET:
> > > > > > > Modernize examples),
> > > > > > > > or not. Thoughts?
> > > > > > > >
> > > > > > > >
> > > > > > > > On Wed, Mar 10, 2021 at 7:45 PM Maxim Muzafarov <
> > mmu...@apache.org>
> > > > > > > wrote:
> > > > > > > >>
> > > > > > > >> 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 exactly I can exclude from the commit to resolve
> > > > > > > >> conflicts since it has some of them with the 2.10 branch. I'm
> > > > > worried
> > > > > > > >> about missing some important parts of the code.
> > > > > > > >>
> > > > > > > >>
> > > > > > > >> - I dive a bit in addition to the .NET examples and found an
> > issue
> > > > > [4]
> > > > > > > >> that has `Fixed` status, however, I can't find it either by
> > id or by
> > > > > > > >> history.
> > > > > > > >> - It is also an important issue (probably I've missed) the
> > .NET:
> > > > > > > >> Modernize examples [5]. Currently, it's not included in 2.10
> > (the
> > > > > fix
> > > > > > > >> `.NET: Race condition in Events example` depends on it)
> > > > > > > >>
> > > > > > > >> So, summarize all if mentioned above:
> > > > > > > >>
> > > > > > > >> Can we cherry-pick 

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

[Denis Magda]

Hi Maxim,

Ideally, a blog post should be published together with the announcement
email. So that the readers can learn more details from the article. Anyway,
you can post it later for 2.10 as long as the release is already completed.

Btw, don't we want to arrange a meetup gathering for Virtual or
Russian-speaking meetup, or both?

-
Denis


On Mon, Mar 15, 2021 at 8:55 PM Maxim Muzafarov  wrote:

> Folks,
>
> I've done almost all the release steps with publishing accepted changes.
> What should I do with an announcement blog post for blogs.apache.org?
> Should it also be prepared prior to an announcement message?
>
> On Thu, 11 Mar 2021 at 00:10, Maxim Muzafarov  wrote:
> >
> > 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 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, 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 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
> better
> > > > > > here to postpone it to the next release and give it a bit of
> time for
> > > > > > the self-stabilization process :-)
> > > > > >
> > > > > > On Wed, 10 Mar 2021 at 20:17, Pavel Tupitsyn <
> ptupit...@apache.org>
> > > > wrote:
> > > > > > >
> > > > > > > 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 is quite an
> unpleasant
> > > > > > regression,
> > > > > > > I think we should include it in the release. It CAN be included
> > > > without
> > > > > > 14250 and 13979.
> > > > > > >
> > > > > > > 14250 does not make sense without 13979.
> > > > > > >
> > > > > > > Ultimately, the question is - do we want to include 13979
> (.NET:
> > > > > > Modernize examples),
> > > > > > > or not. Thoughts?
> > > > > > >
> > > > > > >
> > > > > > > On Wed, Mar 10, 2021 at 7:45 PM Maxim Muzafarov <
> mmu...@apache.org>
> > > > > > wrote:
> > > > > > >>
> > > > > > >> 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 exactly I can exclude from the commit to resolve
> > > > > > >> conflicts since it has some of them with the 2.10 branch. I'm
> > > > worried
> > > > > > >> about missing some important parts of the code.
> > > > > > >>
> > > > > > >>
> > > > > > >> - I dive a bit in addition to the .NET examples and found an
> issue
> > > > [4]
> > > > > > >> that has `Fixed` status, however, I can't find it either by
> id or by
> > > > > > >> history.
> > > > > > >> - It is also an important issue (probably I've missed) the
> .NET:
> > > > > > >> Modernize examples [5]. Currently, it's not included in 2.10
> (the
> > > > fix
> > > > > > >> `.NET: Race condition in Events example` depends on it)
> > > > > > >>
> > > > > > >> So, summarize all if mentioned above:
> > > > > > >>
> > > > > > >> Can we cherry-pick only the `.NET: AffinityKey does not work`
> > > > > > >> IGNITE-14293 without all dependent issues? Or we should apply
> all
> > > > from
> > > > > > >> the chain?
> > > > > > >>
> > > > > > >>
> > > > > > >> [1] https://issues.apache.org/jira/browse/IGNITE-14293
> > > > > > >> [2] https://issues.apache.org/jira/browse/IGNITE-14250
> > > > > > >> [3] https://issues.apache.org/jira/browse/IGNITE-13661
> > > > > > >> [4] https://issues.apache.org/jira/browse/IGNITE-13661
> > > > > > >> [5] https://issues.apache.org/jira/browse/IGNITE-13979
> > > > > > >>
> > > > > > >> On Wed, 10 Mar 2021 at 18:50, Pavel Tupitsyn <
> ptupit...@apache.org>
> > > > > > wrote:
> > > > > > >> >
> > > > > > >> > Maxim,
> > > > > > >> >
> > > > > > >> > No objections to 

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

[Maxim Muzafarov]

Folks,

I've done almost all the release steps with publishing accepted changes.
What should I do with an announcement blog post for blogs.apache.org?
Should it also be prepared prior to an announcement message?

On Thu, 11 Mar 2021 at 00:10, Maxim Muzafarov  wrote:
>
> 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 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, 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 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 better
> > > > > here to postpone it to the next release and give it a bit of time for
> > > > > the self-stabilization process :-)
> > > > >
> > > > > On Wed, 10 Mar 2021 at 20:17, Pavel Tupitsyn 
> > > wrote:
> > > > > >
> > > > > > 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 is quite an unpleasant
> > > > > regression,
> > > > > > I think we should include it in the release. It CAN be included
> > > without
> > > > > 14250 and 13979.
> > > > > >
> > > > > > 14250 does not make sense without 13979.
> > > > > >
> > > > > > Ultimately, the question is - do we want to include 13979 (.NET:
> > > > > Modernize examples),
> > > > > > or not. Thoughts?
> > > > > >
> > > > > >
> > > > > > On Wed, Mar 10, 2021 at 7:45 PM Maxim Muzafarov 
> > > > > wrote:
> > > > > >>
> > > > > >> 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 exactly I can exclude from the commit to resolve
> > > > > >> conflicts since it has some of them with the 2.10 branch. I'm
> > > worried
> > > > > >> about missing some important parts of the code.
> > > > > >>
> > > > > >>
> > > > > >> - I dive a bit in addition to the .NET examples and found an issue
> > > [4]
> > > > > >> that has `Fixed` status, however, I can't find it either by id or 
> > > > > >> by
> > > > > >> history.
> > > > > >> - It is also an important issue (probably I've missed) the .NET:
> > > > > >> Modernize examples [5]. Currently, it's not included in 2.10 (the
> > > fix
> > > > > >> `.NET: Race condition in Events example` depends on it)
> > > > > >>
> > > > > >> So, summarize all if mentioned above:
> > > > > >>
> > > > > >> Can we cherry-pick only the `.NET: AffinityKey does not work`
> > > > > >> IGNITE-14293 without all dependent issues? Or we should apply all
> > > from
> > > > > >> the chain?
> > > > > >>
> > > > > >>
> > > > > >> [1] https://issues.apache.org/jira/browse/IGNITE-14293
> > > > > >> [2] https://issues.apache.org/jira/browse/IGNITE-14250
> > > > > >> [3] https://issues.apache.org/jira/browse/IGNITE-13661
> > > > > >> [4] https://issues.apache.org/jira/browse/IGNITE-13661
> > > > > >> [5] https://issues.apache.org/jira/browse/IGNITE-13979
> > > > > >>
> > > > > >> On Wed, 10 Mar 2021 at 18:50, Pavel Tupitsyn 
> > > > > wrote:
> > > > > >> >
> > > > > >> > 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 <
> > > > > ilya.kasnach...@gmail.com>
> > > > > >> > wrote:
> > > > > >> >
> > > > > >> > > Hello!
> > > > > >> > >
> > > > > >> > > Unless we do extra checks for Windows environment, I suggest
> > > merging
> > > > > >> > > IGNITE-14284 <
> > > https://issues.apache.org/jira/browse/IGNITE-14284>
> > > > > >> > >
> > > > > >> > > Regards,
> > > > > >> > > --
> > > > > >> > > Ilya Kasnacheev
> > > > > >> > >
> > > > > >> > >
> > > > > >> > > вт, 9 мар. 2021 г. в 20:26, Maxim Muzafarov  

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

[Maxim Muzafarov]

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 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, 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 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 better
> > > > here to postpone it to the next release and give it a bit of time for
> > > > the self-stabilization process :-)
> > > >
> > > > On Wed, 10 Mar 2021 at 20:17, Pavel Tupitsyn 
> > wrote:
> > > > >
> > > > > 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 is quite an unpleasant
> > > > regression,
> > > > > I think we should include it in the release. It CAN be included
> > without
> > > > 14250 and 13979.
> > > > >
> > > > > 14250 does not make sense without 13979.
> > > > >
> > > > > Ultimately, the question is - do we want to include 13979 (.NET:
> > > > Modernize examples),
> > > > > or not. Thoughts?
> > > > >
> > > > >
> > > > > On Wed, Mar 10, 2021 at 7:45 PM Maxim Muzafarov 
> > > > wrote:
> > > > >>
> > > > >> 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 exactly I can exclude from the commit to resolve
> > > > >> conflicts since it has some of them with the 2.10 branch. I'm
> > worried
> > > > >> about missing some important parts of the code.
> > > > >>
> > > > >>
> > > > >> - I dive a bit in addition to the .NET examples and found an issue
> > [4]
> > > > >> that has `Fixed` status, however, I can't find it either by id or by
> > > > >> history.
> > > > >> - It is also an important issue (probably I've missed) the .NET:
> > > > >> Modernize examples [5]. Currently, it's not included in 2.10 (the
> > fix
> > > > >> `.NET: Race condition in Events example` depends on it)
> > > > >>
> > > > >> So, summarize all if mentioned above:
> > > > >>
> > > > >> Can we cherry-pick only the `.NET: AffinityKey does not work`
> > > > >> IGNITE-14293 without all dependent issues? Or we should apply all
> > from
> > > > >> the chain?
> > > > >>
> > > > >>
> > > > >> [1] https://issues.apache.org/jira/browse/IGNITE-14293
> > > > >> [2] https://issues.apache.org/jira/browse/IGNITE-14250
> > > > >> [3] https://issues.apache.org/jira/browse/IGNITE-13661
> > > > >> [4] https://issues.apache.org/jira/browse/IGNITE-13661
> > > > >> [5] https://issues.apache.org/jira/browse/IGNITE-13979
> > > > >>
> > > > >> On Wed, 10 Mar 2021 at 18:50, Pavel Tupitsyn 
> > > > wrote:
> > > > >> >
> > > > >> > 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 <
> > > > ilya.kasnach...@gmail.com>
> > > > >> > wrote:
> > > > >> >
> > > > >> > > Hello!
> > > > >> > >
> > > > >> > > Unless we do extra checks for Windows environment, I suggest
> > merging
> > > > >> > > IGNITE-14284 <
> > https://issues.apache.org/jira/browse/IGNITE-14284>
> > > > >> > >
> > > > >> > > Regards,
> > > > >> > > --
> > > > >> > > Ilya Kasnacheev
> > > > >> > >
> > > > >> > >
> > > > >> > > вт, 9 мар. 2021 г. в 20:26, Maxim Muzafarov  > >:
> > > > >> > >
> > > > >> > > > Folks,
> > > > >> > > >
> > > > >> > > >
> > > > >> > > > Sharing the release status:
> > > > >> > > >
> > > > >> > > > .NET: AffinityKey does not work - In-Progress
> > > > >> > > > https://issues.apache.org/jira/browse/IGNITE-14293
> > > > >> > > >
> > > > >> > > > sqlline: `Property "url" is required' - Patch Available
> > > > >> > > > https://issues.apache.org/jira/browse/IGNITE-14284
> > > > >> > > >
> > > > >> > > > sqllline: `Bad history file syntax!' - Resolved
> > > > >> > > > 

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

[Pavel Tupitsyn]

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  wrote:
> >
> > 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 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 better
> > > here to postpone it to the next release and give it a bit of time for
> > > the self-stabilization process :-)
> > >
> > > On Wed, 10 Mar 2021 at 20:17, Pavel Tupitsyn 
> wrote:
> > > >
> > > > 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 is quite an unpleasant
> > > regression,
> > > > I think we should include it in the release. It CAN be included
> without
> > > 14250 and 13979.
> > > >
> > > > 14250 does not make sense without 13979.
> > > >
> > > > Ultimately, the question is - do we want to include 13979 (.NET:
> > > Modernize examples),
> > > > or not. Thoughts?
> > > >
> > > >
> > > > On Wed, Mar 10, 2021 at 7:45 PM Maxim Muzafarov 
> > > wrote:
> > > >>
> > > >> 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 exactly I can exclude from the commit to resolve
> > > >> conflicts since it has some of them with the 2.10 branch. I'm
> worried
> > > >> about missing some important parts of the code.
> > > >>
> > > >>
> > > >> - I dive a bit in addition to the .NET examples and found an issue
> [4]
> > > >> that has `Fixed` status, however, I can't find it either by id or by
> > > >> history.
> > > >> - It is also an important issue (probably I've missed) the .NET:
> > > >> Modernize examples [5]. Currently, it's not included in 2.10 (the
> fix
> > > >> `.NET: Race condition in Events example` depends on it)
> > > >>
> > > >> So, summarize all if mentioned above:
> > > >>
> > > >> Can we cherry-pick only the `.NET: AffinityKey does not work`
> > > >> IGNITE-14293 without all dependent issues? Or we should apply all
> from
> > > >> the chain?
> > > >>
> > > >>
> > > >> [1] https://issues.apache.org/jira/browse/IGNITE-14293
> > > >> [2] https://issues.apache.org/jira/browse/IGNITE-14250
> > > >> [3] https://issues.apache.org/jira/browse/IGNITE-13661
> > > >> [4] https://issues.apache.org/jira/browse/IGNITE-13661
> > > >> [5] https://issues.apache.org/jira/browse/IGNITE-13979
> > > >>
> > > >> On Wed, 10 Mar 2021 at 18:50, Pavel Tupitsyn 
> > > wrote:
> > > >> >
> > > >> > 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 <
> > > ilya.kasnach...@gmail.com>
> > > >> > wrote:
> > > >> >
> > > >> > > Hello!
> > > >> > >
> > > >> > > Unless we do extra checks for Windows environment, I suggest
> merging
> > > >> > > IGNITE-14284 <
> https://issues.apache.org/jira/browse/IGNITE-14284>
> > > >> > >
> > > >> > > Regards,
> > > >> > > --
> > > >> > > Ilya Kasnacheev
> > > >> > >
> > > >> > >
> > > >> > > вт, 9 мар. 2021 г. в 20:26, Maxim Muzafarov  >:
> > > >> > >
> > > >> > > > Folks,
> > > >> > > >
> > > >> > > >
> > > >> > > > Sharing the release status:
> > > >> > > >
> > > >> > > > .NET: AffinityKey does not work - In-Progress
> > > >> > > > https://issues.apache.org/jira/browse/IGNITE-14293
> > > >> > > >
> > > >> > > > sqlline: `Property "url" is required' - Patch Available
> > > >> > > > https://issues.apache.org/jira/browse/IGNITE-14284
> > > >> > > >
> > > >> > > > sqllline: `Bad history file syntax!' - Resolved
> > > >> > > > https://issues.apache.org/jira/browse/IGNITE-14285
> > > >> > > >
> > > >> > > >
> > > >> > > > I'd like to cherry-pick the following fixed bugs to the 2.10
> > > release
> > > >> > > > branch.
> > > >> > > > Do you have any objections?
> > > >> > > >
> > > >> > > > IGNITE-14250 .NET: Fix race condition in Events example, test
> > > example
> > > >> > > > output
> > > >> > > > 

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

[Maxim Muzafarov]

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, 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 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 better
> > here to postpone it to the next release and give it a bit of time for
> > the self-stabilization process :-)
> >
> > On Wed, 10 Mar 2021 at 20:17, Pavel Tupitsyn  wrote:
> > >
> > > 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 is quite an unpleasant
> > regression,
> > > I think we should include it in the release. It CAN be included without
> > 14250 and 13979.
> > >
> > > 14250 does not make sense without 13979.
> > >
> > > Ultimately, the question is - do we want to include 13979 (.NET:
> > Modernize examples),
> > > or not. Thoughts?
> > >
> > >
> > > On Wed, Mar 10, 2021 at 7:45 PM Maxim Muzafarov 
> > wrote:
> > >>
> > >> 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 exactly I can exclude from the commit to resolve
> > >> conflicts since it has some of them with the 2.10 branch. I'm worried
> > >> about missing some important parts of the code.
> > >>
> > >>
> > >> - I dive a bit in addition to the .NET examples and found an issue [4]
> > >> that has `Fixed` status, however, I can't find it either by id or by
> > >> history.
> > >> - It is also an important issue (probably I've missed) the .NET:
> > >> Modernize examples [5]. Currently, it's not included in 2.10 (the fix
> > >> `.NET: Race condition in Events example` depends on it)
> > >>
> > >> So, summarize all if mentioned above:
> > >>
> > >> Can we cherry-pick only the `.NET: AffinityKey does not work`
> > >> IGNITE-14293 without all dependent issues? Or we should apply all from
> > >> the chain?
> > >>
> > >>
> > >> [1] https://issues.apache.org/jira/browse/IGNITE-14293
> > >> [2] https://issues.apache.org/jira/browse/IGNITE-14250
> > >> [3] https://issues.apache.org/jira/browse/IGNITE-13661
> > >> [4] https://issues.apache.org/jira/browse/IGNITE-13661
> > >> [5] https://issues.apache.org/jira/browse/IGNITE-13979
> > >>
> > >> On Wed, 10 Mar 2021 at 18:50, Pavel Tupitsyn 
> > wrote:
> > >> >
> > >> > 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 <
> > ilya.kasnach...@gmail.com>
> > >> > wrote:
> > >> >
> > >> > > Hello!
> > >> > >
> > >> > > Unless we do extra checks for Windows environment, I suggest merging
> > >> > > IGNITE-14284 
> > >> > >
> > >> > > Regards,
> > >> > > --
> > >> > > Ilya Kasnacheev
> > >> > >
> > >> > >
> > >> > > вт, 9 мар. 2021 г. в 20:26, Maxim Muzafarov :
> > >> > >
> > >> > > > Folks,
> > >> > > >
> > >> > > >
> > >> > > > Sharing the release status:
> > >> > > >
> > >> > > > .NET: AffinityKey does not work - In-Progress
> > >> > > > https://issues.apache.org/jira/browse/IGNITE-14293
> > >> > > >
> > >> > > > sqlline: `Property "url" is required' - Patch Available
> > >> > > > https://issues.apache.org/jira/browse/IGNITE-14284
> > >> > > >
> > >> > > > sqllline: `Bad history file syntax!' - Resolved
> > >> > > > https://issues.apache.org/jira/browse/IGNITE-14285
> > >> > > >
> > >> > > >
> > >> > > > I'd like to cherry-pick the following fixed bugs to the 2.10
> > release
> > >> > > > branch.
> > >> > > > Do you have any objections?
> > >> > > >
> > >> > > > IGNITE-14250 .NET: Fix race condition in Events example, test
> > example
> > >> > > > output
> > >> > > > https://issues.apache.org/jira/browse/IGNITE-14250
> > >> > > >
> > >> > > > IGNITE-14168 fix description of validate_indexes command (#8798)
> > >> > > > https://issues.apache.org/jira/browse/IGNITE-14168
> > >> > > >
> > >> > > > IGNITE-14138 Fixed an issue where historical rebalance can kill
> > >> > > > supplier node. Fixes #8769
> > >> > > > https://issues.apache.org/jira/browse/IGNITE-14138
> > >> > > >
> > >> > > > On Mon, 1 Mar 2021 at 

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

[Pavel Tupitsyn]

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 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 better
> here to postpone it to the next release and give it a bit of time for
> the self-stabilization process :-)
>
> On Wed, 10 Mar 2021 at 20:17, Pavel Tupitsyn  wrote:
> >
> > 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 is quite an unpleasant
> regression,
> > I think we should include it in the release. It CAN be included without
> 14250 and 13979.
> >
> > 14250 does not make sense without 13979.
> >
> > Ultimately, the question is - do we want to include 13979 (.NET:
> Modernize examples),
> > or not. Thoughts?
> >
> >
> > On Wed, Mar 10, 2021 at 7:45 PM Maxim Muzafarov 
> wrote:
> >>
> >> 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 exactly I can exclude from the commit to resolve
> >> conflicts since it has some of them with the 2.10 branch. I'm worried
> >> about missing some important parts of the code.
> >>
> >>
> >> - I dive a bit in addition to the .NET examples and found an issue [4]
> >> that has `Fixed` status, however, I can't find it either by id or by
> >> history.
> >> - It is also an important issue (probably I've missed) the .NET:
> >> Modernize examples [5]. Currently, it's not included in 2.10 (the fix
> >> `.NET: Race condition in Events example` depends on it)
> >>
> >> So, summarize all if mentioned above:
> >>
> >> Can we cherry-pick only the `.NET: AffinityKey does not work`
> >> IGNITE-14293 without all dependent issues? Or we should apply all from
> >> the chain?
> >>
> >>
> >> [1] https://issues.apache.org/jira/browse/IGNITE-14293
> >> [2] https://issues.apache.org/jira/browse/IGNITE-14250
> >> [3] https://issues.apache.org/jira/browse/IGNITE-13661
> >> [4] https://issues.apache.org/jira/browse/IGNITE-13661
> >> [5] https://issues.apache.org/jira/browse/IGNITE-13979
> >>
> >> On Wed, 10 Mar 2021 at 18:50, Pavel Tupitsyn 
> wrote:
> >> >
> >> > 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 <
> ilya.kasnach...@gmail.com>
> >> > wrote:
> >> >
> >> > > Hello!
> >> > >
> >> > > Unless we do extra checks for Windows environment, I suggest merging
> >> > > IGNITE-14284 
> >> > >
> >> > > Regards,
> >> > > --
> >> > > Ilya Kasnacheev
> >> > >
> >> > >
> >> > > вт, 9 мар. 2021 г. в 20:26, Maxim Muzafarov :
> >> > >
> >> > > > Folks,
> >> > > >
> >> > > >
> >> > > > Sharing the release status:
> >> > > >
> >> > > > .NET: AffinityKey does not work - In-Progress
> >> > > > https://issues.apache.org/jira/browse/IGNITE-14293
> >> > > >
> >> > > > sqlline: `Property "url" is required' - Patch Available
> >> > > > https://issues.apache.org/jira/browse/IGNITE-14284
> >> > > >
> >> > > > sqllline: `Bad history file syntax!' - Resolved
> >> > > > https://issues.apache.org/jira/browse/IGNITE-14285
> >> > > >
> >> > > >
> >> > > > I'd like to cherry-pick the following fixed bugs to the 2.10
> release
> >> > > > branch.
> >> > > > Do you have any objections?
> >> > > >
> >> > > > IGNITE-14250 .NET: Fix race condition in Events example, test
> example
> >> > > > output
> >> > > > https://issues.apache.org/jira/browse/IGNITE-14250
> >> > > >
> >> > > > IGNITE-14168 fix description of validate_indexes command (#8798)
> >> > > > https://issues.apache.org/jira/browse/IGNITE-14168
> >> > > >
> >> > > > IGNITE-14138 Fixed an issue where historical rebalance can kill
> >> > > > supplier node. Fixes #8769
> >> > > > https://issues.apache.org/jira/browse/IGNITE-14138
> >> > > >
> >> > > > On Mon, 1 Mar 2021 at 21:26, Maxim Muzafarov 
> wrote:
> >> > > > >
> >> > > > > Igor,
> >> > > > >
> >> > > > > Many thanks for fixing the issue!
> >> > > > > I've cherry-picked it to the 2.10 branch.
> >> > > > >
> >> > > > > Folks,
> >> > > > >
> >> > > > > I'll finalize the latest changes for the documentation pages and
> >> > > > > prepare the rc build shortly.
> >> > > > >
> >> > > > > On Mon, 1 Mar 2021 at 21:08, Igor Sapego 
> wrote:
> >> > > > > >
> >> > > > > > 

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

[Maxim Muzafarov]

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 better
here to postpone it to the next release and give it a bit of time for
the self-stabilization process :-)

On Wed, 10 Mar 2021 at 20:17, Pavel Tupitsyn  wrote:
>
> 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 is quite an unpleasant 
> regression,
> I think we should include it in the release. It CAN be included without 14250 
> and 13979.
>
> 14250 does not make sense without 13979.
>
> Ultimately, the question is - do we want to include 13979 (.NET: Modernize 
> examples),
> or not. Thoughts?
>
>
> On Wed, Mar 10, 2021 at 7:45 PM Maxim Muzafarov  wrote:
>>
>> 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 exactly I can exclude from the commit to resolve
>> conflicts since it has some of them with the 2.10 branch. I'm worried
>> about missing some important parts of the code.
>>
>>
>> - I dive a bit in addition to the .NET examples and found an issue [4]
>> that has `Fixed` status, however, I can't find it either by id or by
>> history.
>> - It is also an important issue (probably I've missed) the .NET:
>> Modernize examples [5]. Currently, it's not included in 2.10 (the fix
>> `.NET: Race condition in Events example` depends on it)
>>
>> So, summarize all if mentioned above:
>>
>> Can we cherry-pick only the `.NET: AffinityKey does not work`
>> IGNITE-14293 without all dependent issues? Or we should apply all from
>> the chain?
>>
>>
>> [1] https://issues.apache.org/jira/browse/IGNITE-14293
>> [2] https://issues.apache.org/jira/browse/IGNITE-14250
>> [3] https://issues.apache.org/jira/browse/IGNITE-13661
>> [4] https://issues.apache.org/jira/browse/IGNITE-13661
>> [5] https://issues.apache.org/jira/browse/IGNITE-13979
>>
>> On Wed, 10 Mar 2021 at 18:50, Pavel Tupitsyn  wrote:
>> >
>> > 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 
>> > >
>> > > Regards,
>> > > --
>> > > Ilya Kasnacheev
>> > >
>> > >
>> > > вт, 9 мар. 2021 г. в 20:26, Maxim Muzafarov :
>> > >
>> > > > Folks,
>> > > >
>> > > >
>> > > > Sharing the release status:
>> > > >
>> > > > .NET: AffinityKey does not work - In-Progress
>> > > > https://issues.apache.org/jira/browse/IGNITE-14293
>> > > >
>> > > > sqlline: `Property "url" is required' - Patch Available
>> > > > https://issues.apache.org/jira/browse/IGNITE-14284
>> > > >
>> > > > sqllline: `Bad history file syntax!' - Resolved
>> > > > https://issues.apache.org/jira/browse/IGNITE-14285
>> > > >
>> > > >
>> > > > I'd like to cherry-pick the following fixed bugs to the 2.10 release
>> > > > branch.
>> > > > Do you have any objections?
>> > > >
>> > > > IGNITE-14250 .NET: Fix race condition in Events example, test example
>> > > > output
>> > > > https://issues.apache.org/jira/browse/IGNITE-14250
>> > > >
>> > > > IGNITE-14168 fix description of validate_indexes command (#8798)
>> > > > https://issues.apache.org/jira/browse/IGNITE-14168
>> > > >
>> > > > IGNITE-14138 Fixed an issue where historical rebalance can kill
>> > > > supplier node. Fixes #8769
>> > > > https://issues.apache.org/jira/browse/IGNITE-14138
>> > > >
>> > > > On Mon, 1 Mar 2021 at 21:26, Maxim Muzafarov  wrote:
>> > > > >
>> > > > > Igor,
>> > > > >
>> > > > > Many thanks for fixing the issue!
>> > > > > I've cherry-picked it to the 2.10 branch.
>> > > > >
>> > > > > Folks,
>> > > > >
>> > > > > I'll finalize the latest changes for the documentation pages and
>> > > > > prepare the rc build shortly.
>> > > > >
>> > > > > On Mon, 1 Mar 2021 at 21:08, Igor Sapego  wrote:
>> > > > > >
>> > > > > > The following commit should be cherry-picked:
>> > > > 0675e2a7e800730c9c8230332b82809754ddae5a
>> > > > > >
>> > > > > > Sorry for a delay.
>> > > > > >
>> > > > > > Best Regards,
>> > > > > > Igor
>> > > > > >
>> > > > > >
>> > > > > > On Mon, Mar 1, 2021 at 9:06 PM Igor Sapego 
>> > > wrote:
>> > > > > >>
>> > > > > >> Maxim,
>> > > > > >>
>> > > > > >> The issue is fixed and is merged to master now.
>> > > > > >>
>> > > > > >> Best Regards,
>> > > > > >> Igor
>> > > > > >>
>> > > 

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

[Pavel Tupitsyn]

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
 is quite an unpleasant
regression,
I think we should include it in the release. It CAN be included without
14250  and 13979
.

14250 does not make sense without 13979.

Ultimately, the question is - do we want to include 13979 (.NET: Modernize
examples),
or not. Thoughts?


On Wed, Mar 10, 2021 at 7:45 PM Maxim Muzafarov  wrote:

> 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 exactly I can exclude from the commit to resolve
> conflicts since it has some of them with the 2.10 branch. I'm worried
> about missing some important parts of the code.
>
>
> - I dive a bit in addition to the .NET examples and found an issue [4]
> that has `Fixed` status, however, I can't find it either by id or by
> history.
> - It is also an important issue (probably I've missed) the .NET:
> Modernize examples [5]. Currently, it's not included in 2.10 (the fix
> `.NET: Race condition in Events example` depends on it)
>
> So, summarize all if mentioned above:
>
> Can we cherry-pick only the `.NET: AffinityKey does not work`
> IGNITE-14293 without all dependent issues? Or we should apply all from
> the chain?
>
>
> [1] https://issues.apache.org/jira/browse/IGNITE-14293
> [2] https://issues.apache.org/jira/browse/IGNITE-14250
> [3] https://issues.apache.org/jira/browse/IGNITE-13661
> [4] https://issues.apache.org/jira/browse/IGNITE-13661
> [5] https://issues.apache.org/jira/browse/IGNITE-13979
>
> On Wed, 10 Mar 2021 at 18:50, Pavel Tupitsyn  wrote:
> >
> > 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 <
> ilya.kasnach...@gmail.com>
> > wrote:
> >
> > > Hello!
> > >
> > > Unless we do extra checks for Windows environment, I suggest merging
> > > IGNITE-14284 
> > >
> > > Regards,
> > > --
> > > Ilya Kasnacheev
> > >
> > >
> > > вт, 9 мар. 2021 г. в 20:26, Maxim Muzafarov :
> > >
> > > > Folks,
> > > >
> > > >
> > > > Sharing the release status:
> > > >
> > > > .NET: AffinityKey does not work - In-Progress
> > > > https://issues.apache.org/jira/browse/IGNITE-14293
> > > >
> > > > sqlline: `Property "url" is required' - Patch Available
> > > > https://issues.apache.org/jira/browse/IGNITE-14284
> > > >
> > > > sqllline: `Bad history file syntax!' - Resolved
> > > > https://issues.apache.org/jira/browse/IGNITE-14285
> > > >
> > > >
> > > > I'd like to cherry-pick the following fixed bugs to the 2.10 release
> > > > branch.
> > > > Do you have any objections?
> > > >
> > > > IGNITE-14250 .NET: Fix race condition in Events example, test example
> > > > output
> > > > https://issues.apache.org/jira/browse/IGNITE-14250
> > > >
> > > > IGNITE-14168 fix description of validate_indexes command (#8798)
> > > > https://issues.apache.org/jira/browse/IGNITE-14168
> > > >
> > > > IGNITE-14138 Fixed an issue where historical rebalance can kill
> > > > supplier node. Fixes #8769
> > > > https://issues.apache.org/jira/browse/IGNITE-14138
> > > >
> > > > On Mon, 1 Mar 2021 at 21:26, Maxim Muzafarov 
> wrote:
> > > > >
> > > > > Igor,
> > > > >
> > > > > Many thanks for fixing the issue!
> > > > > I've cherry-picked it to the 2.10 branch.
> > > > >
> > > > > Folks,
> > > > >
> > > > > I'll finalize the latest changes for the documentation pages and
> > > > > prepare the rc build shortly.
> > > > >
> > > > > On Mon, 1 Mar 2021 at 21:08, Igor Sapego 
> wrote:
> > > > > >
> > > > > > The following commit should be cherry-picked:
> > > > 0675e2a7e800730c9c8230332b82809754ddae5a
> > > > > >
> > > > > > Sorry for a delay.
> > > > > >
> > > > > > Best Regards,
> > > > > > Igor
> > > > > >
> > > > > >
> > > > > > On Mon, Mar 1, 2021 at 9:06 PM Igor Sapego 
> > > wrote:
> > > > > >>
> > > > > >> Maxim,
> > > > > >>
> > > > > >> The issue is fixed and is merged to master now.
> > > > > >>
> > > > > >> Best Regards,
> > > > > >> Igor
> > > > > >>
> > > > > >>
> > > > > >> On Sun, Feb 28, 2021 at 8:12 PM Maxim Muzafarov <
> mmu...@apache.org>
> > > > wrote:
> > > > > >>>
> > > > > >>> Hello Igor,
> > > > > >>>
> > > > > >>> >  I believe I could fix the ticket [1] by the end of the next
> > > week.
> > > > > >>> Should we still wait a bit for t his fix or postpone it to
> 

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

[Maxim Muzafarov]

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 exactly I can exclude from the commit to resolve
conflicts since it has some of them with the 2.10 branch. I'm worried
about missing some important parts of the code.


- I dive a bit in addition to the .NET examples and found an issue [4]
that has `Fixed` status, however, I can't find it either by id or by
history.
- It is also an important issue (probably I've missed) the .NET:
Modernize examples [5]. Currently, it's not included in 2.10 (the fix
`.NET: Race condition in Events example` depends on it)

So, summarize all if mentioned above:

Can we cherry-pick only the `.NET: AffinityKey does not work`
IGNITE-14293 without all dependent issues? Or we should apply all from
the chain?


[1] https://issues.apache.org/jira/browse/IGNITE-14293
[2] https://issues.apache.org/jira/browse/IGNITE-14250
[3] https://issues.apache.org/jira/browse/IGNITE-13661
[4] https://issues.apache.org/jira/browse/IGNITE-13661
[5] https://issues.apache.org/jira/browse/IGNITE-13979

On Wed, 10 Mar 2021 at 18:50, Pavel Tupitsyn  wrote:
>
> 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 
> >
> > Regards,
> > --
> > Ilya Kasnacheev
> >
> >
> > вт, 9 мар. 2021 г. в 20:26, Maxim Muzafarov :
> >
> > > Folks,
> > >
> > >
> > > Sharing the release status:
> > >
> > > .NET: AffinityKey does not work - In-Progress
> > > https://issues.apache.org/jira/browse/IGNITE-14293
> > >
> > > sqlline: `Property "url" is required' - Patch Available
> > > https://issues.apache.org/jira/browse/IGNITE-14284
> > >
> > > sqllline: `Bad history file syntax!' - Resolved
> > > https://issues.apache.org/jira/browse/IGNITE-14285
> > >
> > >
> > > I'd like to cherry-pick the following fixed bugs to the 2.10 release
> > > branch.
> > > Do you have any objections?
> > >
> > > IGNITE-14250 .NET: Fix race condition in Events example, test example
> > > output
> > > https://issues.apache.org/jira/browse/IGNITE-14250
> > >
> > > IGNITE-14168 fix description of validate_indexes command (#8798)
> > > https://issues.apache.org/jira/browse/IGNITE-14168
> > >
> > > IGNITE-14138 Fixed an issue where historical rebalance can kill
> > > supplier node. Fixes #8769
> > > https://issues.apache.org/jira/browse/IGNITE-14138
> > >
> > > On Mon, 1 Mar 2021 at 21:26, Maxim Muzafarov  wrote:
> > > >
> > > > Igor,
> > > >
> > > > Many thanks for fixing the issue!
> > > > I've cherry-picked it to the 2.10 branch.
> > > >
> > > > Folks,
> > > >
> > > > I'll finalize the latest changes for the documentation pages and
> > > > prepare the rc build shortly.
> > > >
> > > > On Mon, 1 Mar 2021 at 21:08, Igor Sapego  wrote:
> > > > >
> > > > > The following commit should be cherry-picked:
> > > 0675e2a7e800730c9c8230332b82809754ddae5a
> > > > >
> > > > > Sorry for a delay.
> > > > >
> > > > > Best Regards,
> > > > > Igor
> > > > >
> > > > >
> > > > > On Mon, Mar 1, 2021 at 9:06 PM Igor Sapego 
> > wrote:
> > > > >>
> > > > >> Maxim,
> > > > >>
> > > > >> The issue is fixed and is merged to master now.
> > > > >>
> > > > >> Best Regards,
> > > > >> Igor
> > > > >>
> > > > >>
> > > > >> On Sun, Feb 28, 2021 at 8:12 PM Maxim Muzafarov 
> > > wrote:
> > > > >>>
> > > > >>> Hello Igor,
> > > > >>>
> > > > >>> >  I believe I could fix the ticket [1] by the end of the next
> > week.
> > > > >>> Should we still wait a bit for t his fix or postpone it to 2.10.1?
> > > WDYT?
> > > > >>>
> > > > >>>
> > > > >>>
> > > > >>> [1] https://issues.apache.org/jira/browse/IGNITE-14204
> > > > >>>
> > > > >>> On Fri, 26 Feb 2021 at 11:20, Max Timonin  > >
> > > wrote:
> > > > >>> >
> > > > >>> > Hi, Maxim!
> > > > >>> >
> > > > >>> > The bug IGNITE-14206 [1] fixed. There are 2 commits to
> > cherry-pick
> > > > >>> >
> > > > >>> > 1.
> > > > >>> >
> > >
> > https://github.com/apache/ignite/commit/851f650ba03e0b6c081cfe23f411fd2bf6be0228
> > > > >>> > 2.
> > > > >>> >
> > >
> > https://github.com/apache/ignite/commit/93b74922bd04b164301d7bc5a2788b9693d4a8a4
> > > > >>> >
> > > > >>> >
> > > > >>> > https://issues.apache.org/jira/browse/IGNITE-14206
> > > > >>> >
> > > > >>> > On Wed, Feb 24, 2021 at 5:47 PM Maxim Muzafarov <
> > mmu...@apache.org>
> > > wrote:
> > > > >>> >
> > > > >>> > > Anton,
> > > > >>> > >
> > > > >>> > > Your improvement is very important, for sure, but it's almost 2
> > > months
> > > > >>> > > have passed since the initiation of the release branch. I think
> > > we
> > > > >>> > > should prepare the 

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

[Pavel Tupitsyn]

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 
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> вт, 9 мар. 2021 г. в 20:26, Maxim Muzafarov :
>
> > Folks,
> >
> >
> > Sharing the release status:
> >
> > .NET: AffinityKey does not work - In-Progress
> > https://issues.apache.org/jira/browse/IGNITE-14293
> >
> > sqlline: `Property "url" is required' - Patch Available
> > https://issues.apache.org/jira/browse/IGNITE-14284
> >
> > sqllline: `Bad history file syntax!' - Resolved
> > https://issues.apache.org/jira/browse/IGNITE-14285
> >
> >
> > I'd like to cherry-pick the following fixed bugs to the 2.10 release
> > branch.
> > Do you have any objections?
> >
> > IGNITE-14250 .NET: Fix race condition in Events example, test example
> > output
> > https://issues.apache.org/jira/browse/IGNITE-14250
> >
> > IGNITE-14168 fix description of validate_indexes command (#8798)
> > https://issues.apache.org/jira/browse/IGNITE-14168
> >
> > IGNITE-14138 Fixed an issue where historical rebalance can kill
> > supplier node. Fixes #8769
> > https://issues.apache.org/jira/browse/IGNITE-14138
> >
> > On Mon, 1 Mar 2021 at 21:26, Maxim Muzafarov  wrote:
> > >
> > > Igor,
> > >
> > > Many thanks for fixing the issue!
> > > I've cherry-picked it to the 2.10 branch.
> > >
> > > Folks,
> > >
> > > I'll finalize the latest changes for the documentation pages and
> > > prepare the rc build shortly.
> > >
> > > On Mon, 1 Mar 2021 at 21:08, Igor Sapego  wrote:
> > > >
> > > > The following commit should be cherry-picked:
> > 0675e2a7e800730c9c8230332b82809754ddae5a
> > > >
> > > > Sorry for a delay.
> > > >
> > > > Best Regards,
> > > > Igor
> > > >
> > > >
> > > > On Mon, Mar 1, 2021 at 9:06 PM Igor Sapego 
> wrote:
> > > >>
> > > >> Maxim,
> > > >>
> > > >> The issue is fixed and is merged to master now.
> > > >>
> > > >> Best Regards,
> > > >> Igor
> > > >>
> > > >>
> > > >> On Sun, Feb 28, 2021 at 8:12 PM Maxim Muzafarov 
> > wrote:
> > > >>>
> > > >>> Hello Igor,
> > > >>>
> > > >>> >  I believe I could fix the ticket [1] by the end of the next
> week.
> > > >>> Should we still wait a bit for t his fix or postpone it to 2.10.1?
> > WDYT?
> > > >>>
> > > >>>
> > > >>>
> > > >>> [1] https://issues.apache.org/jira/browse/IGNITE-14204
> > > >>>
> > > >>> On Fri, 26 Feb 2021 at 11:20, Max Timonin  >
> > wrote:
> > > >>> >
> > > >>> > Hi, Maxim!
> > > >>> >
> > > >>> > The bug IGNITE-14206 [1] fixed. There are 2 commits to
> cherry-pick
> > > >>> >
> > > >>> > 1.
> > > >>> >
> >
> https://github.com/apache/ignite/commit/851f650ba03e0b6c081cfe23f411fd2bf6be0228
> > > >>> > 2.
> > > >>> >
> >
> https://github.com/apache/ignite/commit/93b74922bd04b164301d7bc5a2788b9693d4a8a4
> > > >>> >
> > > >>> >
> > > >>> > https://issues.apache.org/jira/browse/IGNITE-14206
> > > >>> >
> > > >>> > On Wed, Feb 24, 2021 at 5:47 PM Maxim Muzafarov <
> mmu...@apache.org>
> > wrote:
> > > >>> >
> > > >>> > > Anton,
> > > >>> > >
> > > >>> > > Your improvement is very important, for sure, but it's almost 2
> > months
> > > >>> > > have passed since the initiation of the release branch. I think
> > we
> > > >>> > > should prepare the changes as fast as possible for now and
> > initiate
> > > >>> > > with the next one release. In general, it would be nice to
> have a
> > > >>> > > release plan for the year ahead so each developer will
> > understand on
> > > >>> > > which release his changes can get into.
> > > >>> > >
> > > >>> > > That's why I'm going to prepare an RC-build on Monday 1-st
> March.
> > > >>> > >
> > > >>> > > On Wed, 24 Feb 2021 at 11:13, Anton Vinogradov 
> > wrote:
> > > >>> > > >
> > > >>> > > > Maxim,
> > > >>> > > >
> > > >>> > > > https://issues.apache.org/jira/browse/IGNITE-13873
> > > >>> > > > Is ready for review, is it possible to wait for it?
> > > >>> > > >
> > > >>> > > > On Wed, Feb 24, 2021 at 12:01 AM Maxim Muzafarov <
> > mmu...@apache.org>
> > > >>> > > wrote:
> > > >>> > > >
> > > >>> > > > > Folks,
> > > >>> > > > >
> > > >>> > > > >
> > > >>> > > > > I'd like to cherry-pick to the release branch the following
> > fixes:
> > > >>> > > > >
> > > >>> > > > > Fix security context for JDBC bulk-load operations
> > > >>> > > > > https://issues.apache.org/jira/browse/IGNITE-13472
> > > >>> > > > >
> > > >>> > > > > Fixed an issue that caused a deadlock when user cache was
> > created in
> > > >>> > > > > parallel with TTL worker was in progress.
> > > >>> > > > > https://issues.apache.org/jira/browse/IGNITE-14078
> > > >>> > > > >
> > > >>> > > > > On Thu, 18 Feb 2021 at 20:26, Maxim Muzafarov <
> > mmu...@apache.org>
> > > >>> > > wrote:
> > > >>> > > > > >
> > > >>> > > > > > Maxim, Igor,
> > > >>> > > > > >
> > > >>> > > > > > Thanks for sharing 

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

[Ilya Kasnacheev]

Hello!

Unless we do extra checks for Windows environment, I suggest merging
IGNITE-14284 

Regards,
-- 
Ilya Kasnacheev


вт, 9 мар. 2021 г. в 20:26, Maxim Muzafarov :

> Folks,
>
>
> Sharing the release status:
>
> .NET: AffinityKey does not work - In-Progress
> https://issues.apache.org/jira/browse/IGNITE-14293
>
> sqlline: `Property "url" is required' - Patch Available
> https://issues.apache.org/jira/browse/IGNITE-14284
>
> sqllline: `Bad history file syntax!' - Resolved
> https://issues.apache.org/jira/browse/IGNITE-14285
>
>
> I'd like to cherry-pick the following fixed bugs to the 2.10 release
> branch.
> Do you have any objections?
>
> IGNITE-14250 .NET: Fix race condition in Events example, test example
> output
> https://issues.apache.org/jira/browse/IGNITE-14250
>
> IGNITE-14168 fix description of validate_indexes command (#8798)
> https://issues.apache.org/jira/browse/IGNITE-14168
>
> IGNITE-14138 Fixed an issue where historical rebalance can kill
> supplier node. Fixes #8769
> https://issues.apache.org/jira/browse/IGNITE-14138
>
> On Mon, 1 Mar 2021 at 21:26, Maxim Muzafarov  wrote:
> >
> > Igor,
> >
> > Many thanks for fixing the issue!
> > I've cherry-picked it to the 2.10 branch.
> >
> > Folks,
> >
> > I'll finalize the latest changes for the documentation pages and
> > prepare the rc build shortly.
> >
> > On Mon, 1 Mar 2021 at 21:08, Igor Sapego  wrote:
> > >
> > > The following commit should be cherry-picked:
> 0675e2a7e800730c9c8230332b82809754ddae5a
> > >
> > > Sorry for a delay.
> > >
> > > Best Regards,
> > > Igor
> > >
> > >
> > > On Mon, Mar 1, 2021 at 9:06 PM Igor Sapego  wrote:
> > >>
> > >> Maxim,
> > >>
> > >> The issue is fixed and is merged to master now.
> > >>
> > >> Best Regards,
> > >> Igor
> > >>
> > >>
> > >> On Sun, Feb 28, 2021 at 8:12 PM Maxim Muzafarov 
> wrote:
> > >>>
> > >>> Hello Igor,
> > >>>
> > >>> >  I believe I could fix the ticket [1] by the end of the next week.
> > >>> Should we still wait a bit for t his fix or postpone it to 2.10.1?
> WDYT?
> > >>>
> > >>>
> > >>>
> > >>> [1] https://issues.apache.org/jira/browse/IGNITE-14204
> > >>>
> > >>> On Fri, 26 Feb 2021 at 11:20, Max Timonin 
> wrote:
> > >>> >
> > >>> > Hi, Maxim!
> > >>> >
> > >>> > The bug IGNITE-14206 [1] fixed. There are 2 commits to cherry-pick
> > >>> >
> > >>> > 1.
> > >>> >
> https://github.com/apache/ignite/commit/851f650ba03e0b6c081cfe23f411fd2bf6be0228
> > >>> > 2.
> > >>> >
> https://github.com/apache/ignite/commit/93b74922bd04b164301d7bc5a2788b9693d4a8a4
> > >>> >
> > >>> >
> > >>> > https://issues.apache.org/jira/browse/IGNITE-14206
> > >>> >
> > >>> > On Wed, Feb 24, 2021 at 5:47 PM Maxim Muzafarov 
> wrote:
> > >>> >
> > >>> > > Anton,
> > >>> > >
> > >>> > > Your improvement is very important, for sure, but it's almost 2
> months
> > >>> > > have passed since the initiation of the release branch. I think
> we
> > >>> > > should prepare the changes as fast as possible for now and
> initiate
> > >>> > > with the next one release. In general, it would be nice to have a
> > >>> > > release plan for the year ahead so each developer will
> understand on
> > >>> > > which release his changes can get into.
> > >>> > >
> > >>> > > That's why I'm going to prepare an RC-build on Monday 1-st March.
> > >>> > >
> > >>> > > On Wed, 24 Feb 2021 at 11:13, Anton Vinogradov 
> wrote:
> > >>> > > >
> > >>> > > > Maxim,
> > >>> > > >
> > >>> > > > https://issues.apache.org/jira/browse/IGNITE-13873
> > >>> > > > Is ready for review, is it possible to wait for it?
> > >>> > > >
> > >>> > > > On Wed, Feb 24, 2021 at 12:01 AM Maxim Muzafarov <
> mmu...@apache.org>
> > >>> > > wrote:
> > >>> > > >
> > >>> > > > > Folks,
> > >>> > > > >
> > >>> > > > >
> > >>> > > > > I'd like to cherry-pick to the release branch the following
> fixes:
> > >>> > > > >
> > >>> > > > > Fix security context for JDBC bulk-load operations
> > >>> > > > > https://issues.apache.org/jira/browse/IGNITE-13472
> > >>> > > > >
> > >>> > > > > Fixed an issue that caused a deadlock when user cache was
> created in
> > >>> > > > > parallel with TTL worker was in progress.
> > >>> > > > > https://issues.apache.org/jira/browse/IGNITE-14078
> > >>> > > > >
> > >>> > > > > On Thu, 18 Feb 2021 at 20:26, Maxim Muzafarov <
> mmu...@apache.org>
> > >>> > > wrote:
> > >>> > > > > >
> > >>> > > > > > Maxim, Igor,
> > >>> > > > > >
> > >>> > > > > > Thanks for sharing details.
> > >>> > > > > > Let's wait for these fixes.
> > >>> > > > > >
> > >>> > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14206
> > >>> > > > > > [2] https://issues.apache.org/jira/browse/IGNITE-14204
> > >>> > > > > >
> > >>> > > > > > On Thu, 18 Feb 2021 at 18:35, Igor Sapego <
> isap...@apache.org>
> > >>> > > wrote:
> > >>> > > > > > >
> > >>> > > > > > > Maxim,
> > >>> > > > > > >
> > >>> > > > > > > I believe I could fix the ticket [1] by the end of the
> next week.
> > >>> > > > > > >
> > >>> > > > > > 

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

[Maxim Muzafarov]

Folks,


Sharing the release status:

.NET: AffinityKey does not work - In-Progress
https://issues.apache.org/jira/browse/IGNITE-14293

sqlline: `Property "url" is required' - Patch Available
https://issues.apache.org/jira/browse/IGNITE-14284

sqllline: `Bad history file syntax!' - Resolved
https://issues.apache.org/jira/browse/IGNITE-14285


I'd like to cherry-pick the following fixed bugs to the 2.10 release branch.
Do you have any objections?

IGNITE-14250 .NET: Fix race condition in Events example, test example output
https://issues.apache.org/jira/browse/IGNITE-14250

IGNITE-14168 fix description of validate_indexes command (#8798)
https://issues.apache.org/jira/browse/IGNITE-14168

IGNITE-14138 Fixed an issue where historical rebalance can kill
supplier node. Fixes #8769
https://issues.apache.org/jira/browse/IGNITE-14138

On Mon, 1 Mar 2021 at 21:26, Maxim Muzafarov  wrote:
>
> Igor,
>
> Many thanks for fixing the issue!
> I've cherry-picked it to the 2.10 branch.
>
> Folks,
>
> I'll finalize the latest changes for the documentation pages and
> prepare the rc build shortly.
>
> On Mon, 1 Mar 2021 at 21:08, Igor Sapego  wrote:
> >
> > The following commit should be cherry-picked: 
> > 0675e2a7e800730c9c8230332b82809754ddae5a
> >
> > Sorry for a delay.
> >
> > Best Regards,
> > Igor
> >
> >
> > On Mon, Mar 1, 2021 at 9:06 PM Igor Sapego  wrote:
> >>
> >> Maxim,
> >>
> >> The issue is fixed and is merged to master now.
> >>
> >> Best Regards,
> >> Igor
> >>
> >>
> >> On Sun, Feb 28, 2021 at 8:12 PM Maxim Muzafarov  wrote:
> >>>
> >>> Hello Igor,
> >>>
> >>> >  I believe I could fix the ticket [1] by the end of the next week.
> >>> Should we still wait a bit for t his fix or postpone it to 2.10.1? WDYT?
> >>>
> >>>
> >>>
> >>> [1] https://issues.apache.org/jira/browse/IGNITE-14204
> >>>
> >>> On Fri, 26 Feb 2021 at 11:20, Max Timonin  wrote:
> >>> >
> >>> > Hi, Maxim!
> >>> >
> >>> > The bug IGNITE-14206 [1] fixed. There are 2 commits to cherry-pick
> >>> >
> >>> > 1.
> >>> > https://github.com/apache/ignite/commit/851f650ba03e0b6c081cfe23f411fd2bf6be0228
> >>> > 2.
> >>> > https://github.com/apache/ignite/commit/93b74922bd04b164301d7bc5a2788b9693d4a8a4
> >>> >
> >>> >
> >>> > https://issues.apache.org/jira/browse/IGNITE-14206
> >>> >
> >>> > On Wed, Feb 24, 2021 at 5:47 PM Maxim Muzafarov  
> >>> > wrote:
> >>> >
> >>> > > Anton,
> >>> > >
> >>> > > Your improvement is very important, for sure, but it's almost 2 months
> >>> > > have passed since the initiation of the release branch. I think we
> >>> > > should prepare the changes as fast as possible for now and initiate
> >>> > > with the next one release. In general, it would be nice to have a
> >>> > > release plan for the year ahead so each developer will understand on
> >>> > > which release his changes can get into.
> >>> > >
> >>> > > That's why I'm going to prepare an RC-build on Monday 1-st March.
> >>> > >
> >>> > > On Wed, 24 Feb 2021 at 11:13, Anton Vinogradov  
> >>> > > wrote:
> >>> > > >
> >>> > > > Maxim,
> >>> > > >
> >>> > > > https://issues.apache.org/jira/browse/IGNITE-13873
> >>> > > > Is ready for review, is it possible to wait for it?
> >>> > > >
> >>> > > > On Wed, Feb 24, 2021 at 12:01 AM Maxim Muzafarov 
> >>> > > wrote:
> >>> > > >
> >>> > > > > Folks,
> >>> > > > >
> >>> > > > >
> >>> > > > > I'd like to cherry-pick to the release branch the following fixes:
> >>> > > > >
> >>> > > > > Fix security context for JDBC bulk-load operations
> >>> > > > > https://issues.apache.org/jira/browse/IGNITE-13472
> >>> > > > >
> >>> > > > > Fixed an issue that caused a deadlock when user cache was created 
> >>> > > > > in
> >>> > > > > parallel with TTL worker was in progress.
> >>> > > > > https://issues.apache.org/jira/browse/IGNITE-14078
> >>> > > > >
> >>> > > > > On Thu, 18 Feb 2021 at 20:26, Maxim Muzafarov 
> >>> > > wrote:
> >>> > > > > >
> >>> > > > > > Maxim, Igor,
> >>> > > > > >
> >>> > > > > > Thanks for sharing details.
> >>> > > > > > Let's wait for these fixes.
> >>> > > > > >
> >>> > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14206
> >>> > > > > > [2] https://issues.apache.org/jira/browse/IGNITE-14204
> >>> > > > > >
> >>> > > > > > On Thu, 18 Feb 2021 at 18:35, Igor Sapego 
> >>> > > wrote:
> >>> > > > > > >
> >>> > > > > > > Maxim,
> >>> > > > > > >
> >>> > > > > > > I believe I could fix the ticket [1] by the end of the next 
> >>> > > > > > > week.
> >>> > > > > > >
> >>> > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14204
> >>> > > > > > >
> >>> > > > > > > Best Regards,
> >>> > > > > > > Igor
> >>> > > > > > >
> >>> > > > > > >
> >>> > > > > > > On Thu, Feb 18, 2021 at 6:30 PM Max Timonin <
> >>> > > timonin.ma...@gmail.com>
> >>> > > > > wrote:
> >>> > > > > > >
> >>> > > > > > > > Hi! I've today found an issue [1], there is wrong handling 
> >>> > > > > > > > of
> >>> > > > > inlined POJO.
> >>> > > > > > > > This bug appeared in 2.9.0 and makes it impossible to work 
> >>> > > > > > 

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

[Maxim Muzafarov]

Igor,

Many thanks for fixing the issue!
I've cherry-picked it to the 2.10 branch.

Folks,

I'll finalize the latest changes for the documentation pages and
prepare the rc build shortly.

On Mon, 1 Mar 2021 at 21:08, Igor Sapego  wrote:
>
> The following commit should be cherry-picked: 
> 0675e2a7e800730c9c8230332b82809754ddae5a
>
> Sorry for a delay.
>
> Best Regards,
> Igor
>
>
> On Mon, Mar 1, 2021 at 9:06 PM Igor Sapego  wrote:
>>
>> Maxim,
>>
>> The issue is fixed and is merged to master now.
>>
>> Best Regards,
>> Igor
>>
>>
>> On Sun, Feb 28, 2021 at 8:12 PM Maxim Muzafarov  wrote:
>>>
>>> Hello Igor,
>>>
>>> >  I believe I could fix the ticket [1] by the end of the next week.
>>> Should we still wait a bit for t his fix or postpone it to 2.10.1? WDYT?
>>>
>>>
>>>
>>> [1] https://issues.apache.org/jira/browse/IGNITE-14204
>>>
>>> On Fri, 26 Feb 2021 at 11:20, Max Timonin  wrote:
>>> >
>>> > Hi, Maxim!
>>> >
>>> > The bug IGNITE-14206 [1] fixed. There are 2 commits to cherry-pick
>>> >
>>> > 1.
>>> > https://github.com/apache/ignite/commit/851f650ba03e0b6c081cfe23f411fd2bf6be0228
>>> > 2.
>>> > https://github.com/apache/ignite/commit/93b74922bd04b164301d7bc5a2788b9693d4a8a4
>>> >
>>> >
>>> > https://issues.apache.org/jira/browse/IGNITE-14206
>>> >
>>> > On Wed, Feb 24, 2021 at 5:47 PM Maxim Muzafarov  wrote:
>>> >
>>> > > Anton,
>>> > >
>>> > > Your improvement is very important, for sure, but it's almost 2 months
>>> > > have passed since the initiation of the release branch. I think we
>>> > > should prepare the changes as fast as possible for now and initiate
>>> > > with the next one release. In general, it would be nice to have a
>>> > > release plan for the year ahead so each developer will understand on
>>> > > which release his changes can get into.
>>> > >
>>> > > That's why I'm going to prepare an RC-build on Monday 1-st March.
>>> > >
>>> > > On Wed, 24 Feb 2021 at 11:13, Anton Vinogradov  wrote:
>>> > > >
>>> > > > Maxim,
>>> > > >
>>> > > > https://issues.apache.org/jira/browse/IGNITE-13873
>>> > > > Is ready for review, is it possible to wait for it?
>>> > > >
>>> > > > On Wed, Feb 24, 2021 at 12:01 AM Maxim Muzafarov 
>>> > > wrote:
>>> > > >
>>> > > > > Folks,
>>> > > > >
>>> > > > >
>>> > > > > I'd like to cherry-pick to the release branch the following fixes:
>>> > > > >
>>> > > > > Fix security context for JDBC bulk-load operations
>>> > > > > https://issues.apache.org/jira/browse/IGNITE-13472
>>> > > > >
>>> > > > > Fixed an issue that caused a deadlock when user cache was created in
>>> > > > > parallel with TTL worker was in progress.
>>> > > > > https://issues.apache.org/jira/browse/IGNITE-14078
>>> > > > >
>>> > > > > On Thu, 18 Feb 2021 at 20:26, Maxim Muzafarov 
>>> > > wrote:
>>> > > > > >
>>> > > > > > Maxim, Igor,
>>> > > > > >
>>> > > > > > Thanks for sharing details.
>>> > > > > > Let's wait for these fixes.
>>> > > > > >
>>> > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14206
>>> > > > > > [2] https://issues.apache.org/jira/browse/IGNITE-14204
>>> > > > > >
>>> > > > > > On Thu, 18 Feb 2021 at 18:35, Igor Sapego 
>>> > > wrote:
>>> > > > > > >
>>> > > > > > > Maxim,
>>> > > > > > >
>>> > > > > > > I believe I could fix the ticket [1] by the end of the next 
>>> > > > > > > week.
>>> > > > > > >
>>> > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14204
>>> > > > > > >
>>> > > > > > > Best Regards,
>>> > > > > > > Igor
>>> > > > > > >
>>> > > > > > >
>>> > > > > > > On Thu, Feb 18, 2021 at 6:30 PM Max Timonin <
>>> > > timonin.ma...@gmail.com>
>>> > > > > wrote:
>>> > > > > > >
>>> > > > > > > > Hi! I've today found an issue [1], there is wrong handling of
>>> > > > > inlined POJO.
>>> > > > > > > > This bug appeared in 2.9.0 and makes it impossible to work 
>>> > > > > > > > with
>>> > > > > > > > multi-column indexes created on old AI versions that contain
>>> > > inlined
>>> > > > > POJO
>>> > > > > > > > keys in the middle.
>>> > > > > > > >
>>> > > > > > > > I'm working on the fix and asked Konstantin Orlov to review 
>>> > > > > > > > it. I
>>> > > > > think
>>> > > > > > > > that it will take only a couple of days to fix this issue. 
>>> > > > > > > > From
>>> > > my
>>> > > > > side, it
>>> > > > > > > > looks like a release blocker, but we've been living with that
>>> > > since
>>> > > > > 2.9.0.
>>> > > > > > > > WDYT if the release can wait for the fix?
>>> > > > > > > >
>>> > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14206
>>> > > > > > > >
>>> > > > > > > > On Thu, Feb 18, 2021 at 5:38 PM Maxim Muzafarov <
>>> > > mmu...@apache.org>
>>> > > > > wrote:
>>> > > > > > > >
>>> > > > > > > > > Folks,
>>> > > > > > > > >
>>> > > > > > > > >
>>> > > > > > > > > Do we have any estimations of how long does it take to fix 
>>> > > > > > > > > the
>>> > > > > issue
>>> > > > > > > > > [1] in C++ thin client? The bug must be fixed for sure,
>>> > > however, I
>>> > > > > > > > > tend to continue with the release (if fixing 

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

[Igor Sapego]

The following commit should be
cherry-picked: 0675e2a7e800730c9c8230332b82809754ddae5a

Sorry for a delay.

Best Regards,
Igor


On Mon, Mar 1, 2021 at 9:06 PM Igor Sapego  wrote:

> Maxim,
>
> The issue is fixed and is merged to master now.
>
> Best Regards,
> Igor
>
>
> On Sun, Feb 28, 2021 at 8:12 PM Maxim Muzafarov  wrote:
>
>> Hello Igor,
>>
>> >  I believe I could fix the ticket [1] by the end of the next week.
>> Should we still wait a bit for t his fix or postpone it to 2.10.1? WDYT?
>>
>>
>>
>> [1] https://issues.apache.org/jira/browse/IGNITE-14204
>>
>> On Fri, 26 Feb 2021 at 11:20, Max Timonin 
>> wrote:
>> >
>> > Hi, Maxim!
>> >
>> > The bug IGNITE-14206 [1] fixed. There are 2 commits to cherry-pick
>> >
>> > 1.
>> >
>> https://github.com/apache/ignite/commit/851f650ba03e0b6c081cfe23f411fd2bf6be0228
>> > 2.
>> >
>> https://github.com/apache/ignite/commit/93b74922bd04b164301d7bc5a2788b9693d4a8a4
>> >
>> >
>> > https://issues.apache.org/jira/browse/IGNITE-14206
>> >
>> > On Wed, Feb 24, 2021 at 5:47 PM Maxim Muzafarov 
>> wrote:
>> >
>> > > Anton,
>> > >
>> > > Your improvement is very important, for sure, but it's almost 2 months
>> > > have passed since the initiation of the release branch. I think we
>> > > should prepare the changes as fast as possible for now and initiate
>> > > with the next one release. In general, it would be nice to have a
>> > > release plan for the year ahead so each developer will understand on
>> > > which release his changes can get into.
>> > >
>> > > That's why I'm going to prepare an RC-build on Monday 1-st March.
>> > >
>> > > On Wed, 24 Feb 2021 at 11:13, Anton Vinogradov  wrote:
>> > > >
>> > > > Maxim,
>> > > >
>> > > > https://issues.apache.org/jira/browse/IGNITE-13873
>> > > > Is ready for review, is it possible to wait for it?
>> > > >
>> > > > On Wed, Feb 24, 2021 at 12:01 AM Maxim Muzafarov > >
>> > > wrote:
>> > > >
>> > > > > Folks,
>> > > > >
>> > > > >
>> > > > > I'd like to cherry-pick to the release branch the following fixes:
>> > > > >
>> > > > > Fix security context for JDBC bulk-load operations
>> > > > > https://issues.apache.org/jira/browse/IGNITE-13472
>> > > > >
>> > > > > Fixed an issue that caused a deadlock when user cache was created
>> in
>> > > > > parallel with TTL worker was in progress.
>> > > > > https://issues.apache.org/jira/browse/IGNITE-14078
>> > > > >
>> > > > > On Thu, 18 Feb 2021 at 20:26, Maxim Muzafarov 
>> > > wrote:
>> > > > > >
>> > > > > > Maxim, Igor,
>> > > > > >
>> > > > > > Thanks for sharing details.
>> > > > > > Let's wait for these fixes.
>> > > > > >
>> > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14206
>> > > > > > [2] https://issues.apache.org/jira/browse/IGNITE-14204
>> > > > > >
>> > > > > > On Thu, 18 Feb 2021 at 18:35, Igor Sapego 
>> > > wrote:
>> > > > > > >
>> > > > > > > Maxim,
>> > > > > > >
>> > > > > > > I believe I could fix the ticket [1] by the end of the next
>> week.
>> > > > > > >
>> > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14204
>> > > > > > >
>> > > > > > > Best Regards,
>> > > > > > > Igor
>> > > > > > >
>> > > > > > >
>> > > > > > > On Thu, Feb 18, 2021 at 6:30 PM Max Timonin <
>> > > timonin.ma...@gmail.com>
>> > > > > wrote:
>> > > > > > >
>> > > > > > > > Hi! I've today found an issue [1], there is wrong handling
>> of
>> > > > > inlined POJO.
>> > > > > > > > This bug appeared in 2.9.0 and makes it impossible to work
>> with
>> > > > > > > > multi-column indexes created on old AI versions that contain
>> > > inlined
>> > > > > POJO
>> > > > > > > > keys in the middle.
>> > > > > > > >
>> > > > > > > > I'm working on the fix and asked Konstantin Orlov to review
>> it. I
>> > > > > think
>> > > > > > > > that it will take only a couple of days to fix this issue.
>> From
>> > > my
>> > > > > side, it
>> > > > > > > > looks like a release blocker, but we've been living with
>> that
>> > > since
>> > > > > 2.9.0.
>> > > > > > > > WDYT if the release can wait for the fix?
>> > > > > > > >
>> > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14206
>> > > > > > > >
>> > > > > > > > On Thu, Feb 18, 2021 at 5:38 PM Maxim Muzafarov <
>> > > mmu...@apache.org>
>> > > > > wrote:
>> > > > > > > >
>> > > > > > > > > Folks,
>> > > > > > > > >
>> > > > > > > > >
>> > > > > > > > > Do we have any estimations of how long does it take to
>> fix the
>> > > > > issue
>> > > > > > > > > [1] in C++ thin client? The bug must be fixed for sure,
>> > > however, I
>> > > > > > > > > tend to continue with the release (if fixing the bug
>> require a
>> > > few
>> > > > > > > > > weeks) and prepare a batch of fixes for the 2.10.1.
>> > > > > > > > >
>> > > > > > > > >
>> > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14204
>> > > > > > > > >
>> > > > > > > > > On Thu, 18 Feb 2021 at 13:22, Ilya Kasnacheev <
>> > > > > ilya.kasnach...@gmail.com
>> > > > > > > > >
>> > > > > > > > > wrote:
>> > > > > > > > > >
>> > > > > > > > > > Hello!
>> > > > > > 

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

[Igor Sapego]

Maxim,

The issue is fixed and is merged to master now.

Best Regards,
Igor


On Sun, Feb 28, 2021 at 8:12 PM Maxim Muzafarov  wrote:

> Hello Igor,
>
> >  I believe I could fix the ticket [1] by the end of the next week.
> Should we still wait a bit for t his fix or postpone it to 2.10.1? WDYT?
>
>
>
> [1] https://issues.apache.org/jira/browse/IGNITE-14204
>
> On Fri, 26 Feb 2021 at 11:20, Max Timonin  wrote:
> >
> > Hi, Maxim!
> >
> > The bug IGNITE-14206 [1] fixed. There are 2 commits to cherry-pick
> >
> > 1.
> >
> https://github.com/apache/ignite/commit/851f650ba03e0b6c081cfe23f411fd2bf6be0228
> > 2.
> >
> https://github.com/apache/ignite/commit/93b74922bd04b164301d7bc5a2788b9693d4a8a4
> >
> >
> > https://issues.apache.org/jira/browse/IGNITE-14206
> >
> > On Wed, Feb 24, 2021 at 5:47 PM Maxim Muzafarov 
> wrote:
> >
> > > Anton,
> > >
> > > Your improvement is very important, for sure, but it's almost 2 months
> > > have passed since the initiation of the release branch. I think we
> > > should prepare the changes as fast as possible for now and initiate
> > > with the next one release. In general, it would be nice to have a
> > > release plan for the year ahead so each developer will understand on
> > > which release his changes can get into.
> > >
> > > That's why I'm going to prepare an RC-build on Monday 1-st March.
> > >
> > > On Wed, 24 Feb 2021 at 11:13, Anton Vinogradov  wrote:
> > > >
> > > > Maxim,
> > > >
> > > > https://issues.apache.org/jira/browse/IGNITE-13873
> > > > Is ready for review, is it possible to wait for it?
> > > >
> > > > On Wed, Feb 24, 2021 at 12:01 AM Maxim Muzafarov 
> > > wrote:
> > > >
> > > > > Folks,
> > > > >
> > > > >
> > > > > I'd like to cherry-pick to the release branch the following fixes:
> > > > >
> > > > > Fix security context for JDBC bulk-load operations
> > > > > https://issues.apache.org/jira/browse/IGNITE-13472
> > > > >
> > > > > Fixed an issue that caused a deadlock when user cache was created
> in
> > > > > parallel with TTL worker was in progress.
> > > > > https://issues.apache.org/jira/browse/IGNITE-14078
> > > > >
> > > > > On Thu, 18 Feb 2021 at 20:26, Maxim Muzafarov 
> > > wrote:
> > > > > >
> > > > > > Maxim, Igor,
> > > > > >
> > > > > > Thanks for sharing details.
> > > > > > Let's wait for these fixes.
> > > > > >
> > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14206
> > > > > > [2] https://issues.apache.org/jira/browse/IGNITE-14204
> > > > > >
> > > > > > On Thu, 18 Feb 2021 at 18:35, Igor Sapego 
> > > wrote:
> > > > > > >
> > > > > > > Maxim,
> > > > > > >
> > > > > > > I believe I could fix the ticket [1] by the end of the next
> week.
> > > > > > >
> > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14204
> > > > > > >
> > > > > > > Best Regards,
> > > > > > > Igor
> > > > > > >
> > > > > > >
> > > > > > > On Thu, Feb 18, 2021 at 6:30 PM Max Timonin <
> > > timonin.ma...@gmail.com>
> > > > > wrote:
> > > > > > >
> > > > > > > > Hi! I've today found an issue [1], there is wrong handling of
> > > > > inlined POJO.
> > > > > > > > This bug appeared in 2.9.0 and makes it impossible to work
> with
> > > > > > > > multi-column indexes created on old AI versions that contain
> > > inlined
> > > > > POJO
> > > > > > > > keys in the middle.
> > > > > > > >
> > > > > > > > I'm working on the fix and asked Konstantin Orlov to review
> it. I
> > > > > think
> > > > > > > > that it will take only a couple of days to fix this issue.
> From
> > > my
> > > > > side, it
> > > > > > > > looks like a release blocker, but we've been living with that
> > > since
> > > > > 2.9.0.
> > > > > > > > WDYT if the release can wait for the fix?
> > > > > > > >
> > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14206
> > > > > > > >
> > > > > > > > On Thu, Feb 18, 2021 at 5:38 PM Maxim Muzafarov <
> > > mmu...@apache.org>
> > > > > wrote:
> > > > > > > >
> > > > > > > > > Folks,
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Do we have any estimations of how long does it take to fix
> the
> > > > > issue
> > > > > > > > > [1] in C++ thin client? The bug must be fixed for sure,
> > > however, I
> > > > > > > > > tend to continue with the release (if fixing the bug
> require a
> > > few
> > > > > > > > > weeks) and prepare a batch of fixes for the 2.10.1.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14204
> > > > > > > > >
> > > > > > > > > On Thu, 18 Feb 2021 at 13:22, Ilya Kasnacheev <
> > > > > ilya.kasnach...@gmail.com
> > > > > > > > >
> > > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > Hello!
> > > > > > > > > >
> > > > > > > > > > There was a ticket filed about the new feature,
> transactions
> > > in
> > > > > C++
> > > > > > > > thin
> > > > > > > > > > client, making this feature unusable if there's more
> than one
> > > > > > > > connection
> > > > > > > > > > endpoint:
> > > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-14204
> 

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

[Maxim Muzafarov]

Hello Igor,

>  I believe I could fix the ticket [1] by the end of the next week.
Should we still wait a bit for t his fix or postpone it to 2.10.1? WDYT?



[1] https://issues.apache.org/jira/browse/IGNITE-14204

On Fri, 26 Feb 2021 at 11:20, Max Timonin  wrote:
>
> Hi, Maxim!
>
> The bug IGNITE-14206 [1] fixed. There are 2 commits to cherry-pick
>
> 1.
> https://github.com/apache/ignite/commit/851f650ba03e0b6c081cfe23f411fd2bf6be0228
> 2.
> https://github.com/apache/ignite/commit/93b74922bd04b164301d7bc5a2788b9693d4a8a4
>
>
> https://issues.apache.org/jira/browse/IGNITE-14206
>
> On Wed, Feb 24, 2021 at 5:47 PM Maxim Muzafarov  wrote:
>
> > Anton,
> >
> > Your improvement is very important, for sure, but it's almost 2 months
> > have passed since the initiation of the release branch. I think we
> > should prepare the changes as fast as possible for now and initiate
> > with the next one release. In general, it would be nice to have a
> > release plan for the year ahead so each developer will understand on
> > which release his changes can get into.
> >
> > That's why I'm going to prepare an RC-build on Monday 1-st March.
> >
> > On Wed, 24 Feb 2021 at 11:13, Anton Vinogradov  wrote:
> > >
> > > Maxim,
> > >
> > > https://issues.apache.org/jira/browse/IGNITE-13873
> > > Is ready for review, is it possible to wait for it?
> > >
> > > On Wed, Feb 24, 2021 at 12:01 AM Maxim Muzafarov 
> > wrote:
> > >
> > > > Folks,
> > > >
> > > >
> > > > I'd like to cherry-pick to the release branch the following fixes:
> > > >
> > > > Fix security context for JDBC bulk-load operations
> > > > https://issues.apache.org/jira/browse/IGNITE-13472
> > > >
> > > > Fixed an issue that caused a deadlock when user cache was created in
> > > > parallel with TTL worker was in progress.
> > > > https://issues.apache.org/jira/browse/IGNITE-14078
> > > >
> > > > On Thu, 18 Feb 2021 at 20:26, Maxim Muzafarov 
> > wrote:
> > > > >
> > > > > Maxim, Igor,
> > > > >
> > > > > Thanks for sharing details.
> > > > > Let's wait for these fixes.
> > > > >
> > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14206
> > > > > [2] https://issues.apache.org/jira/browse/IGNITE-14204
> > > > >
> > > > > On Thu, 18 Feb 2021 at 18:35, Igor Sapego 
> > wrote:
> > > > > >
> > > > > > Maxim,
> > > > > >
> > > > > > I believe I could fix the ticket [1] by the end of the next week.
> > > > > >
> > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14204
> > > > > >
> > > > > > Best Regards,
> > > > > > Igor
> > > > > >
> > > > > >
> > > > > > On Thu, Feb 18, 2021 at 6:30 PM Max Timonin <
> > timonin.ma...@gmail.com>
> > > > wrote:
> > > > > >
> > > > > > > Hi! I've today found an issue [1], there is wrong handling of
> > > > inlined POJO.
> > > > > > > This bug appeared in 2.9.0 and makes it impossible to work with
> > > > > > > multi-column indexes created on old AI versions that contain
> > inlined
> > > > POJO
> > > > > > > keys in the middle.
> > > > > > >
> > > > > > > I'm working on the fix and asked Konstantin Orlov to review it. I
> > > > think
> > > > > > > that it will take only a couple of days to fix this issue. From
> > my
> > > > side, it
> > > > > > > looks like a release blocker, but we've been living with that
> > since
> > > > 2.9.0.
> > > > > > > WDYT if the release can wait for the fix?
> > > > > > >
> > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14206
> > > > > > >
> > > > > > > On Thu, Feb 18, 2021 at 5:38 PM Maxim Muzafarov <
> > mmu...@apache.org>
> > > > wrote:
> > > > > > >
> > > > > > > > Folks,
> > > > > > > >
> > > > > > > >
> > > > > > > > Do we have any estimations of how long does it take to fix the
> > > > issue
> > > > > > > > [1] in C++ thin client? The bug must be fixed for sure,
> > however, I
> > > > > > > > tend to continue with the release (if fixing the bug require a
> > few
> > > > > > > > weeks) and prepare a batch of fixes for the 2.10.1.
> > > > > > > >
> > > > > > > >
> > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14204
> > > > > > > >
> > > > > > > > On Thu, 18 Feb 2021 at 13:22, Ilya Kasnacheev <
> > > > ilya.kasnach...@gmail.com
> > > > > > > >
> > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > Hello!
> > > > > > > > >
> > > > > > > > > There was a ticket filed about the new feature, transactions
> > in
> > > > C++
> > > > > > > thin
> > > > > > > > > client, making this feature unusable if there's more than one
> > > > > > > connection
> > > > > > > > > endpoint:
> > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-14204
> > > > > > > > >
> > > > > > > > > I don't think this is a genuine blocker for 2.10, since
> > there is
> > > > a
> > > > > > > > > workaround (use just one endpoint), nevertheless it is a
> > critical
> > > > > > > crasher
> > > > > > > > > bug, so I wonder if Igor could take a look at it promptly,
> > > > include the
> > > > > > > > fix
> > > > > > > > > in 2.10.
> > > > > > > > >
> > > > > > > > > Regards,
> > > > > > > > > 

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

[Max Timonin]

Hi, Maxim!

The bug IGNITE-14206 [1] fixed. There are 2 commits to cherry-pick

1.
https://github.com/apache/ignite/commit/851f650ba03e0b6c081cfe23f411fd2bf6be0228
2.
https://github.com/apache/ignite/commit/93b74922bd04b164301d7bc5a2788b9693d4a8a4


https://issues.apache.org/jira/browse/IGNITE-14206

On Wed, Feb 24, 2021 at 5:47 PM Maxim Muzafarov  wrote:

> Anton,
>
> Your improvement is very important, for sure, but it's almost 2 months
> have passed since the initiation of the release branch. I think we
> should prepare the changes as fast as possible for now and initiate
> with the next one release. In general, it would be nice to have a
> release plan for the year ahead so each developer will understand on
> which release his changes can get into.
>
> That's why I'm going to prepare an RC-build on Monday 1-st March.
>
> On Wed, 24 Feb 2021 at 11:13, Anton Vinogradov  wrote:
> >
> > Maxim,
> >
> > https://issues.apache.org/jira/browse/IGNITE-13873
> > Is ready for review, is it possible to wait for it?
> >
> > On Wed, Feb 24, 2021 at 12:01 AM Maxim Muzafarov 
> wrote:
> >
> > > Folks,
> > >
> > >
> > > I'd like to cherry-pick to the release branch the following fixes:
> > >
> > > Fix security context for JDBC bulk-load operations
> > > https://issues.apache.org/jira/browse/IGNITE-13472
> > >
> > > Fixed an issue that caused a deadlock when user cache was created in
> > > parallel with TTL worker was in progress.
> > > https://issues.apache.org/jira/browse/IGNITE-14078
> > >
> > > On Thu, 18 Feb 2021 at 20:26, Maxim Muzafarov 
> wrote:
> > > >
> > > > Maxim, Igor,
> > > >
> > > > Thanks for sharing details.
> > > > Let's wait for these fixes.
> > > >
> > > > [1] https://issues.apache.org/jira/browse/IGNITE-14206
> > > > [2] https://issues.apache.org/jira/browse/IGNITE-14204
> > > >
> > > > On Thu, 18 Feb 2021 at 18:35, Igor Sapego 
> wrote:
> > > > >
> > > > > Maxim,
> > > > >
> > > > > I believe I could fix the ticket [1] by the end of the next week.
> > > > >
> > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14204
> > > > >
> > > > > Best Regards,
> > > > > Igor
> > > > >
> > > > >
> > > > > On Thu, Feb 18, 2021 at 6:30 PM Max Timonin <
> timonin.ma...@gmail.com>
> > > wrote:
> > > > >
> > > > > > Hi! I've today found an issue [1], there is wrong handling of
> > > inlined POJO.
> > > > > > This bug appeared in 2.9.0 and makes it impossible to work with
> > > > > > multi-column indexes created on old AI versions that contain
> inlined
> > > POJO
> > > > > > keys in the middle.
> > > > > >
> > > > > > I'm working on the fix and asked Konstantin Orlov to review it. I
> > > think
> > > > > > that it will take only a couple of days to fix this issue. From
> my
> > > side, it
> > > > > > looks like a release blocker, but we've been living with that
> since
> > > 2.9.0.
> > > > > > WDYT if the release can wait for the fix?
> > > > > >
> > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14206
> > > > > >
> > > > > > On Thu, Feb 18, 2021 at 5:38 PM Maxim Muzafarov <
> mmu...@apache.org>
> > > wrote:
> > > > > >
> > > > > > > Folks,
> > > > > > >
> > > > > > >
> > > > > > > Do we have any estimations of how long does it take to fix the
> > > issue
> > > > > > > [1] in C++ thin client? The bug must be fixed for sure,
> however, I
> > > > > > > tend to continue with the release (if fixing the bug require a
> few
> > > > > > > weeks) and prepare a batch of fixes for the 2.10.1.
> > > > > > >
> > > > > > >
> > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14204
> > > > > > >
> > > > > > > On Thu, 18 Feb 2021 at 13:22, Ilya Kasnacheev <
> > > ilya.kasnach...@gmail.com
> > > > > > >
> > > > > > > wrote:
> > > > > > > >
> > > > > > > > Hello!
> > > > > > > >
> > > > > > > > There was a ticket filed about the new feature, transactions
> in
> > > C++
> > > > > > thin
> > > > > > > > client, making this feature unusable if there's more than one
> > > > > > connection
> > > > > > > > endpoint:
> > > > > > > > https://issues.apache.org/jira/browse/IGNITE-14204
> > > > > > > >
> > > > > > > > I don't think this is a genuine blocker for 2.10, since
> there is
> > > a
> > > > > > > > workaround (use just one endpoint), nevertheless it is a
> critical
> > > > > > crasher
> > > > > > > > bug, so I wonder if Igor could take a look at it promptly,
> > > include the
> > > > > > > fix
> > > > > > > > in 2.10.
> > > > > > > >
> > > > > > > > Regards,
> > > > > > > > --
> > > > > > > > Ilya Kasnacheev
> > > > > > > >
> > > > > > > >
> > > > > > > > чт, 18 февр. 2021 г. в 09:03, Zhenya Stanilovsky
> > > > > > >  > > > > > > > >:
> > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > I fill the ticket with drop problem, plz take a look [1]
> > > > > > > > >
> > > > > > > > > [1]  https://issues.apache.org/jira/browse/IGNITE-14205
> > > > > > > > >
> > > > > > > > > >Ilya,
> > > > > > > > > >
> > > > > > > > > >Thanks!
> > > > > > > > > >I've added this step to the Release Process wiki page 

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

[Maxim Muzafarov]

Anton,

Your improvement is very important, for sure, but it's almost 2 months
have passed since the initiation of the release branch. I think we
should prepare the changes as fast as possible for now and initiate
with the next one release. In general, it would be nice to have a
release plan for the year ahead so each developer will understand on
which release his changes can get into.

That's why I'm going to prepare an RC-build on Monday 1-st March.

On Wed, 24 Feb 2021 at 11:13, Anton Vinogradov  wrote:
>
> Maxim,
>
> https://issues.apache.org/jira/browse/IGNITE-13873
> Is ready for review, is it possible to wait for it?
>
> On Wed, Feb 24, 2021 at 12:01 AM Maxim Muzafarov  wrote:
>
> > Folks,
> >
> >
> > I'd like to cherry-pick to the release branch the following fixes:
> >
> > Fix security context for JDBC bulk-load operations
> > https://issues.apache.org/jira/browse/IGNITE-13472
> >
> > Fixed an issue that caused a deadlock when user cache was created in
> > parallel with TTL worker was in progress.
> > https://issues.apache.org/jira/browse/IGNITE-14078
> >
> > On Thu, 18 Feb 2021 at 20:26, Maxim Muzafarov  wrote:
> > >
> > > Maxim, Igor,
> > >
> > > Thanks for sharing details.
> > > Let's wait for these fixes.
> > >
> > > [1] https://issues.apache.org/jira/browse/IGNITE-14206
> > > [2] https://issues.apache.org/jira/browse/IGNITE-14204
> > >
> > > On Thu, 18 Feb 2021 at 18:35, Igor Sapego  wrote:
> > > >
> > > > Maxim,
> > > >
> > > > I believe I could fix the ticket [1] by the end of the next week.
> > > >
> > > > [1] https://issues.apache.org/jira/browse/IGNITE-14204
> > > >
> > > > Best Regards,
> > > > Igor
> > > >
> > > >
> > > > On Thu, Feb 18, 2021 at 6:30 PM Max Timonin 
> > wrote:
> > > >
> > > > > Hi! I've today found an issue [1], there is wrong handling of
> > inlined POJO.
> > > > > This bug appeared in 2.9.0 and makes it impossible to work with
> > > > > multi-column indexes created on old AI versions that contain inlined
> > POJO
> > > > > keys in the middle.
> > > > >
> > > > > I'm working on the fix and asked Konstantin Orlov to review it. I
> > think
> > > > > that it will take only a couple of days to fix this issue. From my
> > side, it
> > > > > looks like a release blocker, but we've been living with that since
> > 2.9.0.
> > > > > WDYT if the release can wait for the fix?
> > > > >
> > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14206
> > > > >
> > > > > On Thu, Feb 18, 2021 at 5:38 PM Maxim Muzafarov 
> > wrote:
> > > > >
> > > > > > Folks,
> > > > > >
> > > > > >
> > > > > > Do we have any estimations of how long does it take to fix the
> > issue
> > > > > > [1] in C++ thin client? The bug must be fixed for sure, however, I
> > > > > > tend to continue with the release (if fixing the bug require a few
> > > > > > weeks) and prepare a batch of fixes for the 2.10.1.
> > > > > >
> > > > > >
> > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14204
> > > > > >
> > > > > > On Thu, 18 Feb 2021 at 13:22, Ilya Kasnacheev <
> > ilya.kasnach...@gmail.com
> > > > > >
> > > > > > wrote:
> > > > > > >
> > > > > > > Hello!
> > > > > > >
> > > > > > > There was a ticket filed about the new feature, transactions in
> > C++
> > > > > thin
> > > > > > > client, making this feature unusable if there's more than one
> > > > > connection
> > > > > > > endpoint:
> > > > > > > https://issues.apache.org/jira/browse/IGNITE-14204
> > > > > > >
> > > > > > > I don't think this is a genuine blocker for 2.10, since there is
> > a
> > > > > > > workaround (use just one endpoint), nevertheless it is a critical
> > > > > crasher
> > > > > > > bug, so I wonder if Igor could take a look at it promptly,
> > include the
> > > > > > fix
> > > > > > > in 2.10.
> > > > > > >
> > > > > > > Regards,
> > > > > > > --
> > > > > > > Ilya Kasnacheev
> > > > > > >
> > > > > > >
> > > > > > > чт, 18 февр. 2021 г. в 09:03, Zhenya Stanilovsky
> > > > > >  > > > > > > >:
> > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > I fill the ticket with drop problem, plz take a look [1]
> > > > > > > >
> > > > > > > > [1]  https://issues.apache.org/jira/browse/IGNITE-14205
> > > > > > > >
> > > > > > > > >Ilya,
> > > > > > > > >
> > > > > > > > >Thanks!
> > > > > > > > >I've added this step to the Release Process wiki page also
> > [1].
> > > > > > > > >
> > > > > > > > >[1]
> > > > > > > >
> > > > > >
> > > > >
> > https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-P1.2ImplementationandScopeFinalization
> > > > > > > > >
> > > > > > > > >On Wed, 17 Feb 2021 at 18:05, Ilya Kasnacheev <
> > > > > > ilya.kasnach...@gmail.com
> > > > > > > > > wrote:
> > > > > > > > >>
> > > > > > > > >> Hello!
> > > > > > > > >>
> > > > > > > > >> I have added ignite-2.10 to Nightly build triggering. I
> > hope we
> > > > > will
> > > > > > > > have a
> > > > > > > > >> 2.10 nightly tomorrow. Shame that I didn't do it earlier.
> > > > > > > > >>
> > > > > > > >
> > > > > >
> > > > >
> > 

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

[Anton Vinogradov]

Maxim,

https://issues.apache.org/jira/browse/IGNITE-13873
Is ready for review, is it possible to wait for it?

On Wed, Feb 24, 2021 at 12:01 AM Maxim Muzafarov  wrote:

> Folks,
>
>
> I'd like to cherry-pick to the release branch the following fixes:
>
> Fix security context for JDBC bulk-load operations
> https://issues.apache.org/jira/browse/IGNITE-13472
>
> Fixed an issue that caused a deadlock when user cache was created in
> parallel with TTL worker was in progress.
> https://issues.apache.org/jira/browse/IGNITE-14078
>
> On Thu, 18 Feb 2021 at 20:26, Maxim Muzafarov  wrote:
> >
> > Maxim, Igor,
> >
> > Thanks for sharing details.
> > Let's wait for these fixes.
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-14206
> > [2] https://issues.apache.org/jira/browse/IGNITE-14204
> >
> > On Thu, 18 Feb 2021 at 18:35, Igor Sapego  wrote:
> > >
> > > Maxim,
> > >
> > > I believe I could fix the ticket [1] by the end of the next week.
> > >
> > > [1] https://issues.apache.org/jira/browse/IGNITE-14204
> > >
> > > Best Regards,
> > > Igor
> > >
> > >
> > > On Thu, Feb 18, 2021 at 6:30 PM Max Timonin 
> wrote:
> > >
> > > > Hi! I've today found an issue [1], there is wrong handling of
> inlined POJO.
> > > > This bug appeared in 2.9.0 and makes it impossible to work with
> > > > multi-column indexes created on old AI versions that contain inlined
> POJO
> > > > keys in the middle.
> > > >
> > > > I'm working on the fix and asked Konstantin Orlov to review it. I
> think
> > > > that it will take only a couple of days to fix this issue. From my
> side, it
> > > > looks like a release blocker, but we've been living with that since
> 2.9.0.
> > > > WDYT if the release can wait for the fix?
> > > >
> > > > [1] https://issues.apache.org/jira/browse/IGNITE-14206
> > > >
> > > > On Thu, Feb 18, 2021 at 5:38 PM Maxim Muzafarov 
> wrote:
> > > >
> > > > > Folks,
> > > > >
> > > > >
> > > > > Do we have any estimations of how long does it take to fix the
> issue
> > > > > [1] in C++ thin client? The bug must be fixed for sure, however, I
> > > > > tend to continue with the release (if fixing the bug require a few
> > > > > weeks) and prepare a batch of fixes for the 2.10.1.
> > > > >
> > > > >
> > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14204
> > > > >
> > > > > On Thu, 18 Feb 2021 at 13:22, Ilya Kasnacheev <
> ilya.kasnach...@gmail.com
> > > > >
> > > > > wrote:
> > > > > >
> > > > > > Hello!
> > > > > >
> > > > > > There was a ticket filed about the new feature, transactions in
> C++
> > > > thin
> > > > > > client, making this feature unusable if there's more than one
> > > > connection
> > > > > > endpoint:
> > > > > > https://issues.apache.org/jira/browse/IGNITE-14204
> > > > > >
> > > > > > I don't think this is a genuine blocker for 2.10, since there is
> a
> > > > > > workaround (use just one endpoint), nevertheless it is a critical
> > > > crasher
> > > > > > bug, so I wonder if Igor could take a look at it promptly,
> include the
> > > > > fix
> > > > > > in 2.10.
> > > > > >
> > > > > > Regards,
> > > > > > --
> > > > > > Ilya Kasnacheev
> > > > > >
> > > > > >
> > > > > > чт, 18 февр. 2021 г. в 09:03, Zhenya Stanilovsky
> > > > >  > > > > > >:
> > > > > >
> > > > > > >
> > > > > > >
> > > > > > > I fill the ticket with drop problem, plz take a look [1]
> > > > > > >
> > > > > > > [1]  https://issues.apache.org/jira/browse/IGNITE-14205
> > > > > > >
> > > > > > > >Ilya,
> > > > > > > >
> > > > > > > >Thanks!
> > > > > > > >I've added this step to the Release Process wiki page also
> [1].
> > > > > > > >
> > > > > > > >[1]
> > > > > > >
> > > > >
> > > >
> https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-P1.2ImplementationandScopeFinalization
> > > > > > > >
> > > > > > > >On Wed, 17 Feb 2021 at 18:05, Ilya Kasnacheev <
> > > > > ilya.kasnach...@gmail.com
> > > > > > > > wrote:
> > > > > > > >>
> > > > > > > >> Hello!
> > > > > > > >>
> > > > > > > >> I have added ignite-2.10 to Nightly build triggering. I
> hope we
> > > > will
> > > > > > > have a
> > > > > > > >> 2.10 nightly tomorrow. Shame that I didn't do it earlier.
> > > > > > > >>
> > > > > > >
> > > > >
> > > >
> https://ci.ignite.apache.org/buildConfiguration/Releases_NightlyRelease_RunApacheIgniteNightlyRelease?branch=ignite-2.10=overview=builds
> > > > > > > >>
> > > > > > > >> Regards,
> > > > > > > >> --
> > > > > > > >> Ilya Kasnacheev
> > > > > > > >>
> > > > > > > >>
> > > > > > > >> ср, 17 февр. 2021 г. в 17:37, Maxim Muzafarov <
> mmu...@apache.org
> > > > > >:
> > > > > > > >>
> > > > > > > >> > Folks,
> > > > > > > >> >
> > > > > > > >> > There is a possible issue with the performance for 2.9.1
> vs
> > > > 2.10.
> > > > > I'm
> > > > > > > >> > trying to reproduce on a stress-testing environment.
> > > > > > > >> > [1]
> > > > > > > >> >
> > > > > > >
> > > > >
> > > >
> https://cwiki.apache.org/confluence/download/attachments/165224767/atomicPutRandomValueFullSync.jpg?api=v2
> > > > 

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

[Maxim Muzafarov]

Folks,


I'd like to cherry-pick to the release branch the following fixes:

Fix security context for JDBC bulk-load operations
https://issues.apache.org/jira/browse/IGNITE-13472

Fixed an issue that caused a deadlock when user cache was created in
parallel with TTL worker was in progress.
https://issues.apache.org/jira/browse/IGNITE-14078

On Thu, 18 Feb 2021 at 20:26, Maxim Muzafarov  wrote:
>
> Maxim, Igor,
>
> Thanks for sharing details.
> Let's wait for these fixes.
>
> [1] https://issues.apache.org/jira/browse/IGNITE-14206
> [2] https://issues.apache.org/jira/browse/IGNITE-14204
>
> On Thu, 18 Feb 2021 at 18:35, Igor Sapego  wrote:
> >
> > Maxim,
> >
> > I believe I could fix the ticket [1] by the end of the next week.
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-14204
> >
> > Best Regards,
> > Igor
> >
> >
> > On Thu, Feb 18, 2021 at 6:30 PM Max Timonin  wrote:
> >
> > > Hi! I've today found an issue [1], there is wrong handling of inlined 
> > > POJO.
> > > This bug appeared in 2.9.0 and makes it impossible to work with
> > > multi-column indexes created on old AI versions that contain inlined POJO
> > > keys in the middle.
> > >
> > > I'm working on the fix and asked Konstantin Orlov to review it. I think
> > > that it will take only a couple of days to fix this issue. From my side, 
> > > it
> > > looks like a release blocker, but we've been living with that since 2.9.0.
> > > WDYT if the release can wait for the fix?
> > >
> > > [1] https://issues.apache.org/jira/browse/IGNITE-14206
> > >
> > > On Thu, Feb 18, 2021 at 5:38 PM Maxim Muzafarov  wrote:
> > >
> > > > Folks,
> > > >
> > > >
> > > > Do we have any estimations of how long does it take to fix the issue
> > > > [1] in C++ thin client? The bug must be fixed for sure, however, I
> > > > tend to continue with the release (if fixing the bug require a few
> > > > weeks) and prepare a batch of fixes for the 2.10.1.
> > > >
> > > >
> > > > [1] https://issues.apache.org/jira/browse/IGNITE-14204
> > > >
> > > > On Thu, 18 Feb 2021 at 13:22, Ilya Kasnacheev  > > >
> > > > wrote:
> > > > >
> > > > > Hello!
> > > > >
> > > > > There was a ticket filed about the new feature, transactions in C++
> > > thin
> > > > > client, making this feature unusable if there's more than one
> > > connection
> > > > > endpoint:
> > > > > https://issues.apache.org/jira/browse/IGNITE-14204
> > > > >
> > > > > I don't think this is a genuine blocker for 2.10, since there is a
> > > > > workaround (use just one endpoint), nevertheless it is a critical
> > > crasher
> > > > > bug, so I wonder if Igor could take a look at it promptly, include the
> > > > fix
> > > > > in 2.10.
> > > > >
> > > > > Regards,
> > > > > --
> > > > > Ilya Kasnacheev
> > > > >
> > > > >
> > > > > чт, 18 февр. 2021 г. в 09:03, Zhenya Stanilovsky
> > > >  > > > > >:
> > > > >
> > > > > >
> > > > > >
> > > > > > I fill the ticket with drop problem, plz take a look [1]
> > > > > >
> > > > > > [1]  https://issues.apache.org/jira/browse/IGNITE-14205
> > > > > >
> > > > > > >Ilya,
> > > > > > >
> > > > > > >Thanks!
> > > > > > >I've added this step to the Release Process wiki page also [1].
> > > > > > >
> > > > > > >[1]
> > > > > >
> > > >
> > > https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-P1.2ImplementationandScopeFinalization
> > > > > > >
> > > > > > >On Wed, 17 Feb 2021 at 18:05, Ilya Kasnacheev <
> > > > ilya.kasnach...@gmail.com
> > > > > > > wrote:
> > > > > > >>
> > > > > > >> Hello!
> > > > > > >>
> > > > > > >> I have added ignite-2.10 to Nightly build triggering. I hope we
> > > will
> > > > > > have a
> > > > > > >> 2.10 nightly tomorrow. Shame that I didn't do it earlier.
> > > > > > >>
> > > > > >
> > > >
> > > https://ci.ignite.apache.org/buildConfiguration/Releases_NightlyRelease_RunApacheIgniteNightlyRelease?branch=ignite-2.10=overview=builds
> > > > > > >>
> > > > > > >> Regards,
> > > > > > >> --
> > > > > > >> Ilya Kasnacheev
> > > > > > >>
> > > > > > >>
> > > > > > >> ср, 17 февр. 2021 г. в 17:37, Maxim Muzafarov < mmu...@apache.org
> > > > >:
> > > > > > >>
> > > > > > >> > Folks,
> > > > > > >> >
> > > > > > >> > There is a possible issue with the performance for 2.9.1 vs
> > > 2.10.
> > > > I'm
> > > > > > >> > trying to reproduce on a stress-testing environment.
> > > > > > >> > [1]
> > > > > > >> >
> > > > > >
> > > >
> > > https://cwiki.apache.org/confluence/download/attachments/165224767/atomicPutRandomValueFullSync.jpg?api=v2
> > > > > > >> >
> > > > > > >> > On Fri, 12 Feb 2021 at 20:46, Maxim Muzafarov <
> > > mmu...@apache.org
> > > > >
> > > > > > wrote:
> > > > > > >> > >
> > > > > > >> > > Folks,
> > > > > > >> > >
> > > > > > >> > > I'm going to cherry-pick these issues to the release branch,
> > > any
> > > > > > >> > objections?
> > > > > > >> > >
> > > > > > >> > >
> > > > > > >> > > Checkpointer thread holds write lock too long
> > > > > > >> > >  https://issues.apache.org/jira/browse/IGNITE-14140
> > > > > > >> 

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

[Maxim Muzafarov]

Maxim, Igor,

Thanks for sharing details.
Let's wait for these fixes.

[1] https://issues.apache.org/jira/browse/IGNITE-14206
[2] https://issues.apache.org/jira/browse/IGNITE-14204

On Thu, 18 Feb 2021 at 18:35, Igor Sapego  wrote:
>
> Maxim,
>
> I believe I could fix the ticket [1] by the end of the next week.
>
> [1] https://issues.apache.org/jira/browse/IGNITE-14204
>
> Best Regards,
> Igor
>
>
> On Thu, Feb 18, 2021 at 6:30 PM Max Timonin  wrote:
>
> > Hi! I've today found an issue [1], there is wrong handling of inlined POJO.
> > This bug appeared in 2.9.0 and makes it impossible to work with
> > multi-column indexes created on old AI versions that contain inlined POJO
> > keys in the middle.
> >
> > I'm working on the fix and asked Konstantin Orlov to review it. I think
> > that it will take only a couple of days to fix this issue. From my side, it
> > looks like a release blocker, but we've been living with that since 2.9.0.
> > WDYT if the release can wait for the fix?
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-14206
> >
> > On Thu, Feb 18, 2021 at 5:38 PM Maxim Muzafarov  wrote:
> >
> > > Folks,
> > >
> > >
> > > Do we have any estimations of how long does it take to fix the issue
> > > [1] in C++ thin client? The bug must be fixed for sure, however, I
> > > tend to continue with the release (if fixing the bug require a few
> > > weeks) and prepare a batch of fixes for the 2.10.1.
> > >
> > >
> > > [1] https://issues.apache.org/jira/browse/IGNITE-14204
> > >
> > > On Thu, 18 Feb 2021 at 13:22, Ilya Kasnacheev  > >
> > > wrote:
> > > >
> > > > Hello!
> > > >
> > > > There was a ticket filed about the new feature, transactions in C++
> > thin
> > > > client, making this feature unusable if there's more than one
> > connection
> > > > endpoint:
> > > > https://issues.apache.org/jira/browse/IGNITE-14204
> > > >
> > > > I don't think this is a genuine blocker for 2.10, since there is a
> > > > workaround (use just one endpoint), nevertheless it is a critical
> > crasher
> > > > bug, so I wonder if Igor could take a look at it promptly, include the
> > > fix
> > > > in 2.10.
> > > >
> > > > Regards,
> > > > --
> > > > Ilya Kasnacheev
> > > >
> > > >
> > > > чт, 18 февр. 2021 г. в 09:03, Zhenya Stanilovsky
> > >  > > > >:
> > > >
> > > > >
> > > > >
> > > > > I fill the ticket with drop problem, plz take a look [1]
> > > > >
> > > > > [1]  https://issues.apache.org/jira/browse/IGNITE-14205
> > > > >
> > > > > >Ilya,
> > > > > >
> > > > > >Thanks!
> > > > > >I've added this step to the Release Process wiki page also [1].
> > > > > >
> > > > > >[1]
> > > > >
> > >
> > https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-P1.2ImplementationandScopeFinalization
> > > > > >
> > > > > >On Wed, 17 Feb 2021 at 18:05, Ilya Kasnacheev <
> > > ilya.kasnach...@gmail.com
> > > > > > wrote:
> > > > > >>
> > > > > >> Hello!
> > > > > >>
> > > > > >> I have added ignite-2.10 to Nightly build triggering. I hope we
> > will
> > > > > have a
> > > > > >> 2.10 nightly tomorrow. Shame that I didn't do it earlier.
> > > > > >>
> > > > >
> > >
> > https://ci.ignite.apache.org/buildConfiguration/Releases_NightlyRelease_RunApacheIgniteNightlyRelease?branch=ignite-2.10=overview=builds
> > > > > >>
> > > > > >> Regards,
> > > > > >> --
> > > > > >> Ilya Kasnacheev
> > > > > >>
> > > > > >>
> > > > > >> ср, 17 февр. 2021 г. в 17:37, Maxim Muzafarov < mmu...@apache.org
> > > >:
> > > > > >>
> > > > > >> > Folks,
> > > > > >> >
> > > > > >> > There is a possible issue with the performance for 2.9.1 vs
> > 2.10.
> > > I'm
> > > > > >> > trying to reproduce on a stress-testing environment.
> > > > > >> > [1]
> > > > > >> >
> > > > >
> > >
> > https://cwiki.apache.org/confluence/download/attachments/165224767/atomicPutRandomValueFullSync.jpg?api=v2
> > > > > >> >
> > > > > >> > On Fri, 12 Feb 2021 at 20:46, Maxim Muzafarov <
> > mmu...@apache.org
> > > >
> > > > > wrote:
> > > > > >> > >
> > > > > >> > > Folks,
> > > > > >> > >
> > > > > >> > > I'm going to cherry-pick these issues to the release branch,
> > any
> > > > > >> > objections?
> > > > > >> > >
> > > > > >> > >
> > > > > >> > > Checkpointer thread holds write lock too long
> > > > > >> > >  https://issues.apache.org/jira/browse/IGNITE-14140
> > > > > >> > >
> > > > > >> > > Incorrect initialize checkpoint-runner-cpu thread pool
> > > > > >> > >  https://issues.apache.org/jira/browse/IGNITE-14139
> > > > > >> > >
> > > > > >> > > On Wed, 10 Feb 2021 at 21:59, Maxim Muzafarov <
> > > mmu...@apache.org
> > > > > > wrote:
> > > > > >> > > >
> > > > > >> > > > Folks,
> > > > > >> > > >
> > > > > >> > > > Do we need any other critical issues from the master branch
> > > that
> > > > > need
> > > > > >> > > > to be cherry-picked picked from the master branch? I've
> > > marked the
> > > > > >> > > > latest select issues with patching version 2.10.
> > > > > >> > > >
> > > > > >> > > > - benchmarks completed (I'll do another one prior to
> > 

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

[Igor Sapego]

Maxim,

I believe I could fix the ticket [1] by the end of the next week.

[1] https://issues.apache.org/jira/browse/IGNITE-14204

Best Regards,
Igor


On Thu, Feb 18, 2021 at 6:30 PM Max Timonin  wrote:

> Hi! I've today found an issue [1], there is wrong handling of inlined POJO.
> This bug appeared in 2.9.0 and makes it impossible to work with
> multi-column indexes created on old AI versions that contain inlined POJO
> keys in the middle.
>
> I'm working on the fix and asked Konstantin Orlov to review it. I think
> that it will take only a couple of days to fix this issue. From my side, it
> looks like a release blocker, but we've been living with that since 2.9.0.
> WDYT if the release can wait for the fix?
>
> [1] https://issues.apache.org/jira/browse/IGNITE-14206
>
> On Thu, Feb 18, 2021 at 5:38 PM Maxim Muzafarov  wrote:
>
> > Folks,
> >
> >
> > Do we have any estimations of how long does it take to fix the issue
> > [1] in C++ thin client? The bug must be fixed for sure, however, I
> > tend to continue with the release (if fixing the bug require a few
> > weeks) and prepare a batch of fixes for the 2.10.1.
> >
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-14204
> >
> > On Thu, 18 Feb 2021 at 13:22, Ilya Kasnacheev  >
> > wrote:
> > >
> > > Hello!
> > >
> > > There was a ticket filed about the new feature, transactions in C++
> thin
> > > client, making this feature unusable if there's more than one
> connection
> > > endpoint:
> > > https://issues.apache.org/jira/browse/IGNITE-14204
> > >
> > > I don't think this is a genuine blocker for 2.10, since there is a
> > > workaround (use just one endpoint), nevertheless it is a critical
> crasher
> > > bug, so I wonder if Igor could take a look at it promptly, include the
> > fix
> > > in 2.10.
> > >
> > > Regards,
> > > --
> > > Ilya Kasnacheev
> > >
> > >
> > > чт, 18 февр. 2021 г. в 09:03, Zhenya Stanilovsky
> >  > > >:
> > >
> > > >
> > > >
> > > > I fill the ticket with drop problem, plz take a look [1]
> > > >
> > > > [1]  https://issues.apache.org/jira/browse/IGNITE-14205
> > > >
> > > > >Ilya,
> > > > >
> > > > >Thanks!
> > > > >I've added this step to the Release Process wiki page also [1].
> > > > >
> > > > >[1]
> > > >
> >
> https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-P1.2ImplementationandScopeFinalization
> > > > >
> > > > >On Wed, 17 Feb 2021 at 18:05, Ilya Kasnacheev <
> > ilya.kasnach...@gmail.com
> > > > > wrote:
> > > > >>
> > > > >> Hello!
> > > > >>
> > > > >> I have added ignite-2.10 to Nightly build triggering. I hope we
> will
> > > > have a
> > > > >> 2.10 nightly tomorrow. Shame that I didn't do it earlier.
> > > > >>
> > > >
> >
> https://ci.ignite.apache.org/buildConfiguration/Releases_NightlyRelease_RunApacheIgniteNightlyRelease?branch=ignite-2.10=overview=builds
> > > > >>
> > > > >> Regards,
> > > > >> --
> > > > >> Ilya Kasnacheev
> > > > >>
> > > > >>
> > > > >> ср, 17 февр. 2021 г. в 17:37, Maxim Muzafarov < mmu...@apache.org
> > >:
> > > > >>
> > > > >> > Folks,
> > > > >> >
> > > > >> > There is a possible issue with the performance for 2.9.1 vs
> 2.10.
> > I'm
> > > > >> > trying to reproduce on a stress-testing environment.
> > > > >> > [1]
> > > > >> >
> > > >
> >
> https://cwiki.apache.org/confluence/download/attachments/165224767/atomicPutRandomValueFullSync.jpg?api=v2
> > > > >> >
> > > > >> > On Fri, 12 Feb 2021 at 20:46, Maxim Muzafarov <
> mmu...@apache.org
> > >
> > > > wrote:
> > > > >> > >
> > > > >> > > Folks,
> > > > >> > >
> > > > >> > > I'm going to cherry-pick these issues to the release branch,
> any
> > > > >> > objections?
> > > > >> > >
> > > > >> > >
> > > > >> > > Checkpointer thread holds write lock too long
> > > > >> > >  https://issues.apache.org/jira/browse/IGNITE-14140
> > > > >> > >
> > > > >> > > Incorrect initialize checkpoint-runner-cpu thread pool
> > > > >> > >  https://issues.apache.org/jira/browse/IGNITE-14139
> > > > >> > >
> > > > >> > > On Wed, 10 Feb 2021 at 21:59, Maxim Muzafarov <
> > mmu...@apache.org
> > > > > wrote:
> > > > >> > > >
> > > > >> > > > Folks,
> > > > >> > > >
> > > > >> > > > Do we need any other critical issues from the master branch
> > that
> > > > need
> > > > >> > > > to be cherry-picked picked from the master branch? I've
> > marked the
> > > > >> > > > latest select issues with patching version 2.10.
> > > > >> > > >
> > > > >> > > > - benchmarks completed (I'll do another one prior to
> > preparing rc)
> > > > >> > > > - the release notes merged
> > > > >> > > > - cherry-picked issue (IGNITE-14073 Fixed transactions
> > failover)
> > > > >> > > > - most of the documentation pages also merged
> > > > >> > > >
> > > > >> > > > Hopefully, by Friday the 12th everything will be ready for
> the
> > > > >> > > > preparation of a release candidate.
> > > > >> > > >
> > > > >> > > > On Tue, 9 Feb 2021 at 05:09, Никита Сафонов <
> > > > vlasovpavel2...@gmail.com >
> > > > >> > wrote:
> > > > >> > > > >
> > > > >> 

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

[Max Timonin]

Hi! I've today found an issue [1], there is wrong handling of inlined POJO.
This bug appeared in 2.9.0 and makes it impossible to work with
multi-column indexes created on old AI versions that contain inlined POJO
keys in the middle.

I'm working on the fix and asked Konstantin Orlov to review it. I think
that it will take only a couple of days to fix this issue. From my side, it
looks like a release blocker, but we've been living with that since 2.9.0.
WDYT if the release can wait for the fix?

[1] https://issues.apache.org/jira/browse/IGNITE-14206

On Thu, Feb 18, 2021 at 5:38 PM Maxim Muzafarov  wrote:

> Folks,
>
>
> Do we have any estimations of how long does it take to fix the issue
> [1] in C++ thin client? The bug must be fixed for sure, however, I
> tend to continue with the release (if fixing the bug require a few
> weeks) and prepare a batch of fixes for the 2.10.1.
>
>
> [1] https://issues.apache.org/jira/browse/IGNITE-14204
>
> On Thu, 18 Feb 2021 at 13:22, Ilya Kasnacheev 
> wrote:
> >
> > Hello!
> >
> > There was a ticket filed about the new feature, transactions in C++ thin
> > client, making this feature unusable if there's more than one connection
> > endpoint:
> > https://issues.apache.org/jira/browse/IGNITE-14204
> >
> > I don't think this is a genuine blocker for 2.10, since there is a
> > workaround (use just one endpoint), nevertheless it is a critical crasher
> > bug, so I wonder if Igor could take a look at it promptly, include the
> fix
> > in 2.10.
> >
> > Regards,
> > --
> > Ilya Kasnacheev
> >
> >
> > чт, 18 февр. 2021 г. в 09:03, Zhenya Stanilovsky
>  > >:
> >
> > >
> > >
> > > I fill the ticket with drop problem, plz take a look [1]
> > >
> > > [1]  https://issues.apache.org/jira/browse/IGNITE-14205
> > >
> > > >Ilya,
> > > >
> > > >Thanks!
> > > >I've added this step to the Release Process wiki page also [1].
> > > >
> > > >[1]
> > >
> https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-P1.2ImplementationandScopeFinalization
> > > >
> > > >On Wed, 17 Feb 2021 at 18:05, Ilya Kasnacheev <
> ilya.kasnach...@gmail.com
> > > > wrote:
> > > >>
> > > >> Hello!
> > > >>
> > > >> I have added ignite-2.10 to Nightly build triggering. I hope we will
> > > have a
> > > >> 2.10 nightly tomorrow. Shame that I didn't do it earlier.
> > > >>
> > >
> https://ci.ignite.apache.org/buildConfiguration/Releases_NightlyRelease_RunApacheIgniteNightlyRelease?branch=ignite-2.10=overview=builds
> > > >>
> > > >> Regards,
> > > >> --
> > > >> Ilya Kasnacheev
> > > >>
> > > >>
> > > >> ср, 17 февр. 2021 г. в 17:37, Maxim Muzafarov < mmu...@apache.org
> >:
> > > >>
> > > >> > Folks,
> > > >> >
> > > >> > There is a possible issue with the performance for 2.9.1 vs 2.10.
> I'm
> > > >> > trying to reproduce on a stress-testing environment.
> > > >> > [1]
> > > >> >
> > >
> https://cwiki.apache.org/confluence/download/attachments/165224767/atomicPutRandomValueFullSync.jpg?api=v2
> > > >> >
> > > >> > On Fri, 12 Feb 2021 at 20:46, Maxim Muzafarov < mmu...@apache.org
> >
> > > wrote:
> > > >> > >
> > > >> > > Folks,
> > > >> > >
> > > >> > > I'm going to cherry-pick these issues to the release branch, any
> > > >> > objections?
> > > >> > >
> > > >> > >
> > > >> > > Checkpointer thread holds write lock too long
> > > >> > >  https://issues.apache.org/jira/browse/IGNITE-14140
> > > >> > >
> > > >> > > Incorrect initialize checkpoint-runner-cpu thread pool
> > > >> > >  https://issues.apache.org/jira/browse/IGNITE-14139
> > > >> > >
> > > >> > > On Wed, 10 Feb 2021 at 21:59, Maxim Muzafarov <
> mmu...@apache.org
> > > > wrote:
> > > >> > > >
> > > >> > > > Folks,
> > > >> > > >
> > > >> > > > Do we need any other critical issues from the master branch
> that
> > > need
> > > >> > > > to be cherry-picked picked from the master branch? I've
> marked the
> > > >> > > > latest select issues with patching version 2.10.
> > > >> > > >
> > > >> > > > - benchmarks completed (I'll do another one prior to
> preparing rc)
> > > >> > > > - the release notes merged
> > > >> > > > - cherry-picked issue (IGNITE-14073 Fixed transactions
> failover)
> > > >> > > > - most of the documentation pages also merged
> > > >> > > >
> > > >> > > > Hopefully, by Friday the 12th everything will be ready for the
> > > >> > > > preparation of a release candidate.
> > > >> > > >
> > > >> > > > On Tue, 9 Feb 2021 at 05:09, Никита Сафонов <
> > > vlasovpavel2...@gmail.com >
> > > >> > wrote:
> > > >> > > > >
> > > >> > > > > Hi everyone,
> > > >> > > > >
> > > >> > > > > Below are two lists of items representing all the remaining
> (and
> > > >> > completed)
> > > >> > > > > documentation tasks for the Ignite 2.10 release.
> > > >> > > > >
> > > >> > > > > The "*Improvements*" part includes PRs on reworked
> > > documentation.
> > > >> > > > > The "*Finished*" part includes PRs on newly added
> documentation.
> > > >> > > > >
> > > >> > > > > *Improvements:*
> > > >> > > > >
> > > >> > > > > Documentation for 

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

[Maxim Muzafarov]

Folks,


Do we have any estimations of how long does it take to fix the issue
[1] in C++ thin client? The bug must be fixed for sure, however, I
tend to continue with the release (if fixing the bug require a few
weeks) and prepare a batch of fixes for the 2.10.1.


[1] https://issues.apache.org/jira/browse/IGNITE-14204

On Thu, 18 Feb 2021 at 13:22, Ilya Kasnacheev  wrote:
>
> Hello!
>
> There was a ticket filed about the new feature, transactions in C++ thin
> client, making this feature unusable if there's more than one connection
> endpoint:
> https://issues.apache.org/jira/browse/IGNITE-14204
>
> I don't think this is a genuine blocker for 2.10, since there is a
> workaround (use just one endpoint), nevertheless it is a critical crasher
> bug, so I wonder if Igor could take a look at it promptly, include the fix
> in 2.10.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> чт, 18 февр. 2021 г. в 09:03, Zhenya Stanilovsky  >:
>
> >
> >
> > I fill the ticket with drop problem, plz take a look [1]
> >
> > [1]  https://issues.apache.org/jira/browse/IGNITE-14205
> >
> > >Ilya,
> > >
> > >Thanks!
> > >I've added this step to the Release Process wiki page also [1].
> > >
> > >[1]
> > https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-P1.2ImplementationandScopeFinalization
> > >
> > >On Wed, 17 Feb 2021 at 18:05, Ilya Kasnacheev < ilya.kasnach...@gmail.com
> > > wrote:
> > >>
> > >> Hello!
> > >>
> > >> I have added ignite-2.10 to Nightly build triggering. I hope we will
> > have a
> > >> 2.10 nightly tomorrow. Shame that I didn't do it earlier.
> > >>
> > https://ci.ignite.apache.org/buildConfiguration/Releases_NightlyRelease_RunApacheIgniteNightlyRelease?branch=ignite-2.10=overview=builds
> > >>
> > >> Regards,
> > >> --
> > >> Ilya Kasnacheev
> > >>
> > >>
> > >> ср, 17 февр. 2021 г. в 17:37, Maxim Muzafarov < mmu...@apache.org >:
> > >>
> > >> > Folks,
> > >> >
> > >> > There is a possible issue with the performance for 2.9.1 vs 2.10. I'm
> > >> > trying to reproduce on a stress-testing environment.
> > >> > [1]
> > >> >
> > https://cwiki.apache.org/confluence/download/attachments/165224767/atomicPutRandomValueFullSync.jpg?api=v2
> > >> >
> > >> > On Fri, 12 Feb 2021 at 20:46, Maxim Muzafarov < mmu...@apache.org >
> > wrote:
> > >> > >
> > >> > > Folks,
> > >> > >
> > >> > > I'm going to cherry-pick these issues to the release branch, any
> > >> > objections?
> > >> > >
> > >> > >
> > >> > > Checkpointer thread holds write lock too long
> > >> > >  https://issues.apache.org/jira/browse/IGNITE-14140
> > >> > >
> > >> > > Incorrect initialize checkpoint-runner-cpu thread pool
> > >> > >  https://issues.apache.org/jira/browse/IGNITE-14139
> > >> > >
> > >> > > On Wed, 10 Feb 2021 at 21:59, Maxim Muzafarov < mmu...@apache.org
> > > wrote:
> > >> > > >
> > >> > > > Folks,
> > >> > > >
> > >> > > > Do we need any other critical issues from the master branch that
> > need
> > >> > > > to be cherry-picked picked from the master branch? I've marked the
> > >> > > > latest select issues with patching version 2.10.
> > >> > > >
> > >> > > > - benchmarks completed (I'll do another one prior to preparing rc)
> > >> > > > - the release notes merged
> > >> > > > - cherry-picked issue (IGNITE-14073 Fixed transactions failover)
> > >> > > > - most of the documentation pages also merged
> > >> > > >
> > >> > > > Hopefully, by Friday the 12th everything will be ready for the
> > >> > > > preparation of a release candidate.
> > >> > > >
> > >> > > > On Tue, 9 Feb 2021 at 05:09, Никита Сафонов <
> > vlasovpavel2...@gmail.com >
> > >> > wrote:
> > >> > > > >
> > >> > > > > Hi everyone,
> > >> > > > >
> > >> > > > > Below are two lists of items representing all the remaining (and
> > >> > completed)
> > >> > > > > documentation tasks for the Ignite 2.10 release.
> > >> > > > >
> > >> > > > > The "*Improvements*" part includes PRs on reworked
> > documentation.
> > >> > > > > The "*Finished*" part includes PRs on newly added documentation.
> > >> > > > >
> > >> > > > > *Improvements:*
> > >> > > > >
> > >> > > > > Documentation for .NET thin client service invocation
> > >> > > > > [1]  https://issues.apache.org/jira/browse/IGNITE-14129
> > >> > > > > [2]  https://github.com/apache/ignite/pull/8756
> > >> > > > >
> > >> > > > > Documentation for cache warm-up strategy
> > >> > > > > [1]  https://issues.apache.org/jira/browse/IGNITE-13385
> > >> > > > > [2]  https://github.com/apache/ignite/pull/8703
> > >> > > > >
> > >> > > > > *Finished:*
> > >> > > > >
> > >> > > > > Document control.(sh|bin) command to get an arbitrary SystemView
> > >> > > > > [1]  https://issues.apache.org/jira/browse/IGNITE-14142
> > >> > > > > [2]  https://github.com/apache/ignite/pull/8775
> > >> > > > >
> > >> > > > > Document metric for processed keys when rebuilding indexes
> > >> > > > > [1]  https://issues.apache.org/jira/browse/IGNITE-14143
> > >> > > > > [2]  https://github.com/apache/ignite/pull/8776
> > >> > > > >
> > >> > 

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

[Ilya Kasnacheev]

Hello!

There was a ticket filed about the new feature, transactions in C++ thin
client, making this feature unusable if there's more than one connection
endpoint:
https://issues.apache.org/jira/browse/IGNITE-14204

I don't think this is a genuine blocker for 2.10, since there is a
workaround (use just one endpoint), nevertheless it is a critical crasher
bug, so I wonder if Igor could take a look at it promptly, include the fix
in 2.10.

Regards,
-- 
Ilya Kasnacheev


чт, 18 февр. 2021 г. в 09:03, Zhenya Stanilovsky :

>
>
> I fill the ticket with drop problem, plz take a look [1]
>
> [1]  https://issues.apache.org/jira/browse/IGNITE-14205
>
> >Ilya,
> >
> >Thanks!
> >I've added this step to the Release Process wiki page also [1].
> >
> >[1]
> https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-P1.2ImplementationandScopeFinalization
> >
> >On Wed, 17 Feb 2021 at 18:05, Ilya Kasnacheev < ilya.kasnach...@gmail.com
> > wrote:
> >>
> >> Hello!
> >>
> >> I have added ignite-2.10 to Nightly build triggering. I hope we will
> have a
> >> 2.10 nightly tomorrow. Shame that I didn't do it earlier.
> >>
> https://ci.ignite.apache.org/buildConfiguration/Releases_NightlyRelease_RunApacheIgniteNightlyRelease?branch=ignite-2.10=overview=builds
> >>
> >> Regards,
> >> --
> >> Ilya Kasnacheev
> >>
> >>
> >> ср, 17 февр. 2021 г. в 17:37, Maxim Muzafarov < mmu...@apache.org >:
> >>
> >> > Folks,
> >> >
> >> > There is a possible issue with the performance for 2.9.1 vs 2.10. I'm
> >> > trying to reproduce on a stress-testing environment.
> >> > [1]
> >> >
> https://cwiki.apache.org/confluence/download/attachments/165224767/atomicPutRandomValueFullSync.jpg?api=v2
> >> >
> >> > On Fri, 12 Feb 2021 at 20:46, Maxim Muzafarov < mmu...@apache.org >
> wrote:
> >> > >
> >> > > Folks,
> >> > >
> >> > > I'm going to cherry-pick these issues to the release branch, any
> >> > objections?
> >> > >
> >> > >
> >> > > Checkpointer thread holds write lock too long
> >> > >  https://issues.apache.org/jira/browse/IGNITE-14140
> >> > >
> >> > > Incorrect initialize checkpoint-runner-cpu thread pool
> >> > >  https://issues.apache.org/jira/browse/IGNITE-14139
> >> > >
> >> > > On Wed, 10 Feb 2021 at 21:59, Maxim Muzafarov < mmu...@apache.org
> > wrote:
> >> > > >
> >> > > > Folks,
> >> > > >
> >> > > > Do we need any other critical issues from the master branch that
> need
> >> > > > to be cherry-picked picked from the master branch? I've marked the
> >> > > > latest select issues with patching version 2.10.
> >> > > >
> >> > > > - benchmarks completed (I'll do another one prior to preparing rc)
> >> > > > - the release notes merged
> >> > > > - cherry-picked issue (IGNITE-14073 Fixed transactions failover)
> >> > > > - most of the documentation pages also merged
> >> > > >
> >> > > > Hopefully, by Friday the 12th everything will be ready for the
> >> > > > preparation of a release candidate.
> >> > > >
> >> > > > On Tue, 9 Feb 2021 at 05:09, Никита Сафонов <
> vlasovpavel2...@gmail.com >
> >> > wrote:
> >> > > > >
> >> > > > > Hi everyone,
> >> > > > >
> >> > > > > Below are two lists of items representing all the remaining (and
> >> > completed)
> >> > > > > documentation tasks for the Ignite 2.10 release.
> >> > > > >
> >> > > > > The "*Improvements*" part includes PRs on reworked
> documentation.
> >> > > > > The "*Finished*" part includes PRs on newly added documentation.
> >> > > > >
> >> > > > > *Improvements:*
> >> > > > >
> >> > > > > Documentation for .NET thin client service invocation
> >> > > > > [1]  https://issues.apache.org/jira/browse/IGNITE-14129
> >> > > > > [2]  https://github.com/apache/ignite/pull/8756
> >> > > > >
> >> > > > > Documentation for cache warm-up strategy
> >> > > > > [1]  https://issues.apache.org/jira/browse/IGNITE-13385
> >> > > > > [2]  https://github.com/apache/ignite/pull/8703
> >> > > > >
> >> > > > > *Finished:*
> >> > > > >
> >> > > > > Document control.(sh|bin) command to get an arbitrary SystemView
> >> > > > > [1]  https://issues.apache.org/jira/browse/IGNITE-14142
> >> > > > > [2]  https://github.com/apache/ignite/pull/8775
> >> > > > >
> >> > > > > Document metric for processed keys when rebuilding indexes
> >> > > > > [1]  https://issues.apache.org/jira/browse/IGNITE-14143
> >> > > > > [2]  https://github.com/apache/ignite/pull/8776
> >> > > > >
> >> > > > > Document C++ thin client transactions
> >> > > > > [1]  https://issues.apache.org/jira/browse/IGNITE-14144
> >> > > > > [2]  https://github.com/apache/ignite/pull/8777
> >> > > > >
> >> > > > > Please don't hesitate to ask me if you have any questions or
> >> > concerns.
> >> > > > >
> >> > > > > With best regards,
> >> > > > > Nikita
> >> > > > >
> >> > > > > сб, 6 февр. 2021 г. в 02:14, Никита Сафонов <
> >> >  vlasovpavel2...@gmail.com >:
> >> > > > >
> >> > > > > > Maxim,
> >> > > > > >
> >> > > > > > Thank you for being ready to help!
> >> > > > > >
> >> > > > > > As I mentioned before, I'm sharing the 

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

[Zhenya Stanilovsky]

I fill the ticket with drop problem, plz take a look [1]
 
[1]  https://issues.apache.org/jira/browse/IGNITE-14205
 
>Ilya,
>
>Thanks!
>I've added this step to the Release Process wiki page also [1].
>
>[1]  
>https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-P1.2ImplementationandScopeFinalization
>
>On Wed, 17 Feb 2021 at 18:05, Ilya Kasnacheev < ilya.kasnach...@gmail.com > 
>wrote:
>>
>> Hello!
>>
>> I have added ignite-2.10 to Nightly build triggering. I hope we will have a
>> 2.10 nightly tomorrow. Shame that I didn't do it earlier.
>>  
>> https://ci.ignite.apache.org/buildConfiguration/Releases_NightlyRelease_RunApacheIgniteNightlyRelease?branch=ignite-2.10=overview=builds
>>
>> Regards,
>> --
>> Ilya Kasnacheev
>>
>>
>> ср, 17 февр. 2021 г. в 17:37, Maxim Muzafarov < mmu...@apache.org >:
>>
>> > Folks,
>> >
>> > There is a possible issue with the performance for 2.9.1 vs 2.10. I'm
>> > trying to reproduce on a stress-testing environment.
>> > [1]
>> >  
>> > https://cwiki.apache.org/confluence/download/attachments/165224767/atomicPutRandomValueFullSync.jpg?api=v2
>> >
>> > On Fri, 12 Feb 2021 at 20:46, Maxim Muzafarov < mmu...@apache.org > wrote:
>> > >
>> > > Folks,
>> > >
>> > > I'm going to cherry-pick these issues to the release branch, any
>> > objections?
>> > >
>> > >
>> > > Checkpointer thread holds write lock too long
>> > >  https://issues.apache.org/jira/browse/IGNITE-14140
>> > >
>> > > Incorrect initialize checkpoint-runner-cpu thread pool
>> > >  https://issues.apache.org/jira/browse/IGNITE-14139
>> > >
>> > > On Wed, 10 Feb 2021 at 21:59, Maxim Muzafarov < mmu...@apache.org > 
>> > > wrote:
>> > > >
>> > > > Folks,
>> > > >
>> > > > Do we need any other critical issues from the master branch that need
>> > > > to be cherry-picked picked from the master branch? I've marked the
>> > > > latest select issues with patching version 2.10.
>> > > >
>> > > > - benchmarks completed (I'll do another one prior to preparing rc)
>> > > > - the release notes merged
>> > > > - cherry-picked issue (IGNITE-14073 Fixed transactions failover)
>> > > > - most of the documentation pages also merged
>> > > >
>> > > > Hopefully, by Friday the 12th everything will be ready for the
>> > > > preparation of a release candidate.
>> > > >
>> > > > On Tue, 9 Feb 2021 at 05:09, Никита Сафонов < 
>> > > > vlasovpavel2...@gmail.com >
>> > wrote:
>> > > > >
>> > > > > Hi everyone,
>> > > > >
>> > > > > Below are two lists of items representing all the remaining (and
>> > completed)
>> > > > > documentation tasks for the Ignite 2.10 release.
>> > > > >
>> > > > > The "*Improvements*" part includes PRs on reworked documentation.
>> > > > > The "*Finished*" part includes PRs on newly added documentation.
>> > > > >
>> > > > > *Improvements:*
>> > > > >
>> > > > > Documentation for .NET thin client service invocation
>> > > > > [1]  https://issues.apache.org/jira/browse/IGNITE-14129
>> > > > > [2]  https://github.com/apache/ignite/pull/8756
>> > > > >
>> > > > > Documentation for cache warm-up strategy
>> > > > > [1]  https://issues.apache.org/jira/browse/IGNITE-13385
>> > > > > [2]  https://github.com/apache/ignite/pull/8703
>> > > > >
>> > > > > *Finished:*
>> > > > >
>> > > > > Document control.(sh|bin) command to get an arbitrary SystemView
>> > > > > [1]  https://issues.apache.org/jira/browse/IGNITE-14142
>> > > > > [2]  https://github.com/apache/ignite/pull/8775
>> > > > >
>> > > > > Document metric for processed keys when rebuilding indexes
>> > > > > [1]  https://issues.apache.org/jira/browse/IGNITE-14143
>> > > > > [2]  https://github.com/apache/ignite/pull/8776
>> > > > >
>> > > > > Document C++ thin client transactions
>> > > > > [1]  https://issues.apache.org/jira/browse/IGNITE-14144
>> > > > > [2]  https://github.com/apache/ignite/pull/8777
>> > > > >
>> > > > > Please don't hesitate to ask me if you have any questions or
>> > concerns.
>> > > > >
>> > > > > With best regards,
>> > > > > Nikita
>> > > > >
>> > > > > сб, 6 февр. 2021 г. в 02:14, Никита Сафонов <
>> >  vlasovpavel2...@gmail.com >:
>> > > > >
>> > > > > > Maxim,
>> > > > > >
>> > > > > > Thank you for being ready to help!
>> > > > > >
>> > > > > > As I mentioned before, I'm sharing the completed doc items today.
>> > > > > > Below is the list of tickets with the prepared PR's:
>> > > > > >
>> > > > > > *- Documentation: SQL tracing.*
>> > > > > > [1]  https://issues.apache.org/jira/browse/IGNITE-13981
>> > > > > > [2]  https://github.com/apache/ignite/pull/8762
>> > > > > >
>> > > > > > *- Documentation for async API (Thin client Java API)*
>> > > > > > [1]  https://issues.apache.org/jira/browse/IGNITE-14128
>> > > > > > [2]  https://github.com/apache/ignite/pull/8753
>> > > > > >
>> > > > > > *- Documentation for .NET: Thin Client: Service invocation*
>> > > > > > [1]  https://issues.apache.org/jira/browse/IGNITE-14129
>> > > > > > [2]  https://github.com/apache/ignite/pull/8756
>> > > > > >
>> > > > > > *-