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
>> > > > > >
>> > > > > > *- 

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

[Maxim Muzafarov]

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  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 :
>
> > 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  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  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, Никита Сафонов 
> > 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
> > > > > >
> > > > > > *- Document cluster API implementation for CPP*
> > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14133
> > > > > > [2] https://github.com/apache/ignite/pull/8761
> > > > > >
> > > > > >
> > > > > > I still have some docs to finish/improve.
> > > > > > I do believe that I'll provide the rest of the remaining
> > documentation by
> > > > > > the end of Monday.
> > > > > >
> > > > > > Regards,
> > > > > > 

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

[Ilya Kasnacheev]

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 :

> 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  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  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, Никита Сафонов 
> 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
> > > > >
> > > > > *- Document cluster API implementation for CPP*
> > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14133
> > > > > [2] https://github.com/apache/ignite/pull/8761
> > > > >
> > > > >
> > > > > I still have some docs to finish/improve.
> > > > > I do believe that I'll provide the rest of the remaining
> documentation by
> > > > > the end of Monday.
> > > > >
> > > > > Regards,
> > > > > Nikita
> > > > >
> > > > > чт, 4 февр. 2021 г. в 21:45, Maxim Muzafarov :
> > > > >
> > > > >> Nikita,
> > > > >>
> > > > >> Thank you, I will be waiting for the review.
> > > > >>
> > > > >> > I'll give the precise estimate tomorrow as I'm still waiting
> for some
> > > > >> info
> > > > >> from the dev side.
> > > > >> Let me know if you need any kind of help.
> > > > >>
> > > > >> On Thu, 4 Feb 2021 at 20:07, Никита Сафонов <
> vlasovpavel2...@gmail.com>
> > > > >> wrote:
> > > > >> >
> > > > >> > Hi 

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

[Maxim Muzafarov]

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  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  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, Никита Сафонов  
> > 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, Никита Сафонов :
> > >
> > > > 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
> > > >
> > > > *- Document cluster API implementation for CPP*
> > > > [1] https://issues.apache.org/jira/browse/IGNITE-14133
> > > > [2] https://github.com/apache/ignite/pull/8761
> > > >
> > > >
> > > > I still have some docs to finish/improve.
> > > > I do believe that I'll provide the rest of the remaining documentation 
> > > > by
> > > > the end of Monday.
> > > >
> > > > Regards,
> > > > Nikita
> > > >
> > > > чт, 4 февр. 2021 г. в 21:45, Maxim Muzafarov :
> > > >
> > > >> Nikita,
> > > >>
> > > >> Thank you, I will be waiting for the review.
> > > >>
> > > >> > I'll give the precise estimate tomorrow as I'm still waiting for some
> > > >> info
> > > >> from the dev side.
> > > >> Let me know if you need any kind of help.
> > > >>
> > > >> On Thu, 4 Feb 2021 at 20:07, Никита Сафонов 
> > > >> wrote:
> > > >> >
> > > >> > Hi Maxim,
> > > >> >
> > > >> > I can take a look!
> > > >> >
> > > >> > Moreover, I'm finishing the work on the remaining documentation 
> > > >> > tickets.
> > > >> > I do believe that I'll be able to provide several PR's tomorrow and
> > > >> > complete the rest in a couple of days.
> > > >> > I'll give the precise estimate tomorrow as I'm still waiting for some
> > > >> info
> > > >> > from the dev side.
> > > >> >
> > > >> > Regards,
> > > >> > Nikita
> > > >> >
> > > >> > ср, 3 февр. 2021 г. в 22:40, Maxim Muzafarov :
> > > >> >
> > > >> > > Folks,
> > > >> > >
> > > >> > >
> > > >> > > I've prepared the RELEASE_NOTES.
> > > >> > > Would anyone 

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

[Maxim Muzafarov]

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  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, Никита Сафонов  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, Никита Сафонов :
> >
> > > 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
> > >
> > > *- Document cluster API implementation for CPP*
> > > [1] https://issues.apache.org/jira/browse/IGNITE-14133
> > > [2] https://github.com/apache/ignite/pull/8761
> > >
> > >
> > > I still have some docs to finish/improve.
> > > I do believe that I'll provide the rest of the remaining documentation by
> > > the end of Monday.
> > >
> > > Regards,
> > > Nikita
> > >
> > > чт, 4 февр. 2021 г. в 21:45, Maxim Muzafarov :
> > >
> > >> Nikita,
> > >>
> > >> Thank you, I will be waiting for the review.
> > >>
> > >> > I'll give the precise estimate tomorrow as I'm still waiting for some
> > >> info
> > >> from the dev side.
> > >> Let me know if you need any kind of help.
> > >>
> > >> On Thu, 4 Feb 2021 at 20:07, Никита Сафонов 
> > >> wrote:
> > >> >
> > >> > Hi Maxim,
> > >> >
> > >> > I can take a look!
> > >> >
> > >> > Moreover, I'm finishing the work on the remaining documentation 
> > >> > tickets.
> > >> > I do believe that I'll be able to provide several PR's tomorrow and
> > >> > complete the rest in a couple of days.
> > >> > I'll give the precise estimate tomorrow as I'm still waiting for some
> > >> info
> > >> > from the dev side.
> > >> >
> > >> > Regards,
> > >> > Nikita
> > >> >
> > >> > ср, 3 февр. 2021 г. в 22:40, Maxim Muzafarov :
> > >> >
> > >> > > Folks,
> > >> > >
> > >> > >
> > >> > > I've prepared the RELEASE_NOTES.
> > >> > > Would anyone take a look at the PR [2] [1]?
> > >> > >
> > >> > >
> > >> > > [1] https://issues.apache.org/jira/browse/IGNITE-14069
> > >> > > [2] https://github.com/apache/ignite/pull/8748/files
> > >> > >
> > >> > > On Tue, 2 Feb 2021 at 22:13, Maxim Muzafarov 
> > >> wrote:
> > >> > > >
> > >> > > > Folks,
> > >> > > >
> > >> > > > I've prepared first benchmarks comparing 2.9.1 vs 2.10 [1].
> > >> > > > Everything looks good at the first glance.
> > >> > > >
> > >> > > >
> > >> > >
> > >> 

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

[Maxim Muzafarov]

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, Никита Сафонов  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, Никита Сафонов :
>
> > 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
> >
> > *- Document cluster API implementation for CPP*
> > [1] https://issues.apache.org/jira/browse/IGNITE-14133
> > [2] https://github.com/apache/ignite/pull/8761
> >
> >
> > I still have some docs to finish/improve.
> > I do believe that I'll provide the rest of the remaining documentation by
> > the end of Monday.
> >
> > Regards,
> > Nikita
> >
> > чт, 4 февр. 2021 г. в 21:45, Maxim Muzafarov :
> >
> >> Nikita,
> >>
> >> Thank you, I will be waiting for the review.
> >>
> >> > I'll give the precise estimate tomorrow as I'm still waiting for some
> >> info
> >> from the dev side.
> >> Let me know if you need any kind of help.
> >>
> >> On Thu, 4 Feb 2021 at 20:07, Никита Сафонов 
> >> wrote:
> >> >
> >> > Hi Maxim,
> >> >
> >> > I can take a look!
> >> >
> >> > Moreover, I'm finishing the work on the remaining documentation tickets.
> >> > I do believe that I'll be able to provide several PR's tomorrow and
> >> > complete the rest in a couple of days.
> >> > I'll give the precise estimate tomorrow as I'm still waiting for some
> >> info
> >> > from the dev side.
> >> >
> >> > Regards,
> >> > Nikita
> >> >
> >> > ср, 3 февр. 2021 г. в 22:40, Maxim Muzafarov :
> >> >
> >> > > Folks,
> >> > >
> >> > >
> >> > > I've prepared the RELEASE_NOTES.
> >> > > Would anyone take a look at the PR [2] [1]?
> >> > >
> >> > >
> >> > > [1] https://issues.apache.org/jira/browse/IGNITE-14069
> >> > > [2] https://github.com/apache/ignite/pull/8748/files
> >> > >
> >> > > On Tue, 2 Feb 2021 at 22:13, Maxim Muzafarov 
> >> wrote:
> >> > > >
> >> > > > Folks,
> >> > > >
> >> > > > I've prepared first benchmarks comparing 2.9.1 vs 2.10 [1].
> >> > > > Everything looks good at the first glance.
> >> > > >
> >> > > >
> >> > >
> >> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.10#ApacheIgnite2.10-Benchmarks(2.9.1vs2.10)
> >> > > >
> >> > > > On Fri, 29 Jan 2021 at 18:32, Никита Сафонов <
> >> vlasovpavel2...@gmail.com>
> >> > > wrote:
> >> > > > >
> >> > > > > Hi Maxim,
> >> > > > >
> >> > > > > terrific!
> >> > > > >
> >> > > > > Then, I'll continue with the tasks on the list.
> >> > > > >
> >> > > > > Thank you,
> >> > > > > Nikita
> >> > > > >
> >> > > > > чт, 28 янв. 2021 г. в 22:44, Maxim Muzafarov :
> >> > > > >
> >> > > > > > Hello Nikita,
> >> > > > > >
> >> > > > > > Thank you for sharing the state.
> >> > > > > >
> >> > > > > > I think we can move on to the next stages of the release. There
> >> are a
> >> > > > > > few 

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

[Никита Сафонов]

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, Никита Сафонов :

> 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
>
> *- Document cluster API implementation for CPP*
> [1] https://issues.apache.org/jira/browse/IGNITE-14133
> [2] https://github.com/apache/ignite/pull/8761
>
>
> I still have some docs to finish/improve.
> I do believe that I'll provide the rest of the remaining documentation by
> the end of Monday.
>
> Regards,
> Nikita
>
> чт, 4 февр. 2021 г. в 21:45, Maxim Muzafarov :
>
>> Nikita,
>>
>> Thank you, I will be waiting for the review.
>>
>> > I'll give the precise estimate tomorrow as I'm still waiting for some
>> info
>> from the dev side.
>> Let me know if you need any kind of help.
>>
>> On Thu, 4 Feb 2021 at 20:07, Никита Сафонов 
>> wrote:
>> >
>> > Hi Maxim,
>> >
>> > I can take a look!
>> >
>> > Moreover, I'm finishing the work on the remaining documentation tickets.
>> > I do believe that I'll be able to provide several PR's tomorrow and
>> > complete the rest in a couple of days.
>> > I'll give the precise estimate tomorrow as I'm still waiting for some
>> info
>> > from the dev side.
>> >
>> > Regards,
>> > Nikita
>> >
>> > ср, 3 февр. 2021 г. в 22:40, Maxim Muzafarov :
>> >
>> > > Folks,
>> > >
>> > >
>> > > I've prepared the RELEASE_NOTES.
>> > > Would anyone take a look at the PR [2] [1]?
>> > >
>> > >
>> > > [1] https://issues.apache.org/jira/browse/IGNITE-14069
>> > > [2] https://github.com/apache/ignite/pull/8748/files
>> > >
>> > > On Tue, 2 Feb 2021 at 22:13, Maxim Muzafarov 
>> wrote:
>> > > >
>> > > > Folks,
>> > > >
>> > > > I've prepared first benchmarks comparing 2.9.1 vs 2.10 [1].
>> > > > Everything looks good at the first glance.
>> > > >
>> > > >
>> > >
>> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.10#ApacheIgnite2.10-Benchmarks(2.9.1vs2.10)
>> > > >
>> > > > On Fri, 29 Jan 2021 at 18:32, Никита Сафонов <
>> vlasovpavel2...@gmail.com>
>> > > wrote:
>> > > > >
>> > > > > Hi Maxim,
>> > > > >
>> > > > > terrific!
>> > > > >
>> > > > > Then, I'll continue with the tasks on the list.
>> > > > >
>> > > > > Thank you,
>> > > > > Nikita
>> > > > >
>> > > > > чт, 28 янв. 2021 г. в 22:44, Maxim Muzafarov :
>> > > > >
>> > > > > > Hello Nikita,
>> > > > > >
>> > > > > > Thank you for sharing the state.
>> > > > > >
>> > > > > > I think we can move on to the next stages of the release. There
>> are a
>> > > > > > few important steps left to do: release_notes, stress testing.
>> This
>> > > > > > may take some time, so we still have time to complete the rest
>> of the
>> > > > > > documentation tasks.
>> > > > > >
>> > > > > > On Thu, 28 Jan 2021 at 02:51, Никита Сафонов <
>> > > vlasovpavel2...@gmail.com>
>> > > > > > wrote:
>> > > > > > >
>> > > > > > > Hi Maxim et al,
>> > > > > > >
>> > > > > > > thank you!
>> > > > > > >
>> > > > > > > The rest of the documentation tasks for important features
>> are also
>> > > > > > > completed.
>> > > > > > >
>> > > > > > > Nevertheless, there are still some items (the ones on my list
>> that
>> > > do not
>> > > > > > > have any doc tasks) that can be done for the 2.10 release.
>> > > > > > > If you want them to be included, I will try to provide patches
>> > > ASAP. If
>> > > > > > > not, 

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

[Никита Сафонов]

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

*- Document cluster API implementation for CPP*
[1] https://issues.apache.org/jira/browse/IGNITE-14133
[2] https://github.com/apache/ignite/pull/8761


I still have some docs to finish/improve.
I do believe that I'll provide the rest of the remaining documentation by
the end of Monday.

Regards,
Nikita

чт, 4 февр. 2021 г. в 21:45, Maxim Muzafarov :

> Nikita,
>
> Thank you, I will be waiting for the review.
>
> > I'll give the precise estimate tomorrow as I'm still waiting for some
> info
> from the dev side.
> Let me know if you need any kind of help.
>
> On Thu, 4 Feb 2021 at 20:07, Никита Сафонов 
> wrote:
> >
> > Hi Maxim,
> >
> > I can take a look!
> >
> > Moreover, I'm finishing the work on the remaining documentation tickets.
> > I do believe that I'll be able to provide several PR's tomorrow and
> > complete the rest in a couple of days.
> > I'll give the precise estimate tomorrow as I'm still waiting for some
> info
> > from the dev side.
> >
> > Regards,
> > Nikita
> >
> > ср, 3 февр. 2021 г. в 22:40, Maxim Muzafarov :
> >
> > > Folks,
> > >
> > >
> > > I've prepared the RELEASE_NOTES.
> > > Would anyone take a look at the PR [2] [1]?
> > >
> > >
> > > [1] https://issues.apache.org/jira/browse/IGNITE-14069
> > > [2] https://github.com/apache/ignite/pull/8748/files
> > >
> > > On Tue, 2 Feb 2021 at 22:13, Maxim Muzafarov 
> wrote:
> > > >
> > > > Folks,
> > > >
> > > > I've prepared first benchmarks comparing 2.9.1 vs 2.10 [1].
> > > > Everything looks good at the first glance.
> > > >
> > > >
> > >
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.10#ApacheIgnite2.10-Benchmarks(2.9.1vs2.10)
> > > >
> > > > On Fri, 29 Jan 2021 at 18:32, Никита Сафонов <
> vlasovpavel2...@gmail.com>
> > > wrote:
> > > > >
> > > > > Hi Maxim,
> > > > >
> > > > > terrific!
> > > > >
> > > > > Then, I'll continue with the tasks on the list.
> > > > >
> > > > > Thank you,
> > > > > Nikita
> > > > >
> > > > > чт, 28 янв. 2021 г. в 22:44, Maxim Muzafarov :
> > > > >
> > > > > > Hello Nikita,
> > > > > >
> > > > > > Thank you for sharing the state.
> > > > > >
> > > > > > I think we can move on to the next stages of the release. There
> are a
> > > > > > few important steps left to do: release_notes, stress testing.
> This
> > > > > > may take some time, so we still have time to complete the rest
> of the
> > > > > > documentation tasks.
> > > > > >
> > > > > > On Thu, 28 Jan 2021 at 02:51, Никита Сафонов <
> > > vlasovpavel2...@gmail.com>
> > > > > > wrote:
> > > > > > >
> > > > > > > Hi Maxim et al,
> > > > > > >
> > > > > > > thank you!
> > > > > > >
> > > > > > > The rest of the documentation tasks for important features are
> also
> > > > > > > completed.
> > > > > > >
> > > > > > > Nevertheless, there are still some items (the ones on my list
> that
> > > do not
> > > > > > > have any doc tasks) that can be done for the 2.10 release.
> > > > > > > If you want them to be included, I will try to provide patches
> > > ASAP. If
> > > > > > > not, I am still ready to create the documentation for them and
> > > provide it
> > > > > > > later.
> > > > > > >
> > > > > > > So, I will fully rely on your decision.
> > > > > > >
> > > > > > > Regards,
> > > > > > >
> > > > > > > Nikita
> > > > > > >
> > > > > > > вт, 26 янв. 2021 г. в 23:08, Maxim Muzafarov <
> mmu...@apache.org>:
> > > > > > >
> > > > > > > > Nikita, Folks,
> > > > > > > >
> > > > > > > > All documentation tasks from the *[list #2]* [1] that you
> > > mentioned
> > > > > > > > above have been processed and merged to the release branch.
> > > > > > > >
> > > > > > > > [1]
> > > > > > > >
> > > > > >
> > >
> http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-Apache-Ignite-Release-2-10-time-scope-manager-tp50037p51061.html
> > > > > > > >
> > > > > > > > On Mon, 25 Jan 2021 at 18:59, Maxim Muzafarov <
> mmu...@apache.org
> > > >
> > > > > > wrote:
> > > > > > > > >
> > > > > > > > > Shiva,
> > > > > > > > >
> > > > > > > > > I've cherry-picked the issue to 2.10 branch.
> > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-13912
> > > > > > > > >
> > > > > > > > > Ilya,
> > > > > > > > >
> > > > > > > > > Thank you for preparing the patch. I've cherry-picked to
> 2.10
> > > it too.
> > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-14039
> > > > > > > > >
> > > > > > > > > On Mon, 25 Jan 2021 at 

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

[Maxim Muzafarov]

Nikita,

Thank you, I will be waiting for the review.

> I'll give the precise estimate tomorrow as I'm still waiting for some info
from the dev side.
Let me know if you need any kind of help.

On Thu, 4 Feb 2021 at 20:07, Никита Сафонов  wrote:
>
> Hi Maxim,
>
> I can take a look!
>
> Moreover, I'm finishing the work on the remaining documentation tickets.
> I do believe that I'll be able to provide several PR's tomorrow and
> complete the rest in a couple of days.
> I'll give the precise estimate tomorrow as I'm still waiting for some info
> from the dev side.
>
> Regards,
> Nikita
>
> ср, 3 февр. 2021 г. в 22:40, Maxim Muzafarov :
>
> > Folks,
> >
> >
> > I've prepared the RELEASE_NOTES.
> > Would anyone take a look at the PR [2] [1]?
> >
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-14069
> > [2] https://github.com/apache/ignite/pull/8748/files
> >
> > On Tue, 2 Feb 2021 at 22:13, Maxim Muzafarov  wrote:
> > >
> > > Folks,
> > >
> > > I've prepared first benchmarks comparing 2.9.1 vs 2.10 [1].
> > > Everything looks good at the first glance.
> > >
> > >
> > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.10#ApacheIgnite2.10-Benchmarks(2.9.1vs2.10)
> > >
> > > On Fri, 29 Jan 2021 at 18:32, Никита Сафонов 
> > wrote:
> > > >
> > > > Hi Maxim,
> > > >
> > > > terrific!
> > > >
> > > > Then, I'll continue with the tasks on the list.
> > > >
> > > > Thank you,
> > > > Nikita
> > > >
> > > > чт, 28 янв. 2021 г. в 22:44, Maxim Muzafarov :
> > > >
> > > > > Hello Nikita,
> > > > >
> > > > > Thank you for sharing the state.
> > > > >
> > > > > I think we can move on to the next stages of the release. There are a
> > > > > few important steps left to do: release_notes, stress testing. This
> > > > > may take some time, so we still have time to complete the rest of the
> > > > > documentation tasks.
> > > > >
> > > > > On Thu, 28 Jan 2021 at 02:51, Никита Сафонов <
> > vlasovpavel2...@gmail.com>
> > > > > wrote:
> > > > > >
> > > > > > Hi Maxim et al,
> > > > > >
> > > > > > thank you!
> > > > > >
> > > > > > The rest of the documentation tasks for important features are also
> > > > > > completed.
> > > > > >
> > > > > > Nevertheless, there are still some items (the ones on my list that
> > do not
> > > > > > have any doc tasks) that can be done for the 2.10 release.
> > > > > > If you want them to be included, I will try to provide patches
> > ASAP. If
> > > > > > not, I am still ready to create the documentation for them and
> > provide it
> > > > > > later.
> > > > > >
> > > > > > So, I will fully rely on your decision.
> > > > > >
> > > > > > Regards,
> > > > > >
> > > > > > Nikita
> > > > > >
> > > > > > вт, 26 янв. 2021 г. в 23:08, Maxim Muzafarov :
> > > > > >
> > > > > > > Nikita, Folks,
> > > > > > >
> > > > > > > All documentation tasks from the *[list #2]* [1] that you
> > mentioned
> > > > > > > above have been processed and merged to the release branch.
> > > > > > >
> > > > > > > [1]
> > > > > > >
> > > > >
> > http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-Apache-Ignite-Release-2-10-time-scope-manager-tp50037p51061.html
> > > > > > >
> > > > > > > On Mon, 25 Jan 2021 at 18:59, Maxim Muzafarov  > >
> > > > > wrote:
> > > > > > > >
> > > > > > > > Shiva,
> > > > > > > >
> > > > > > > > I've cherry-picked the issue to 2.10 branch.
> > > > > > > > https://issues.apache.org/jira/browse/IGNITE-13912
> > > > > > > >
> > > > > > > > Ilya,
> > > > > > > >
> > > > > > > > Thank you for preparing the patch. I've cherry-picked to 2.10
> > it too.
> > > > > > > > https://issues.apache.org/jira/browse/IGNITE-14039
> > > > > > > >
> > > > > > > > On Mon, 25 Jan 2021 at 17:50, Ilya Kasnacheev <
> > > > > ilya.kasnach...@gmail.com>
> > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > Hello!
> > > > > > > > >
> > > > > > > > > I have pushed the developer warning, javadoc warning and
> > > > > documentation
> > > > > > > > > update to https://issues.apache.org/jira/browse/IGNITE-14039
> > > > > about the
> > > > > > > > > dangers of WAL state change.
> > > > > > > > >
> > > > > > > > > Please cherry-pick it to 2.10 branch or mention me if it's
> > OK for
> > > > > me
> > > > > > > to do
> > > > > > > > > this.
> > > > > > > > >
> > > > > > > > > Regards,
> > > > > > > > > --
> > > > > > > > > Ilya Kasnacheev
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > пн, 25 янв. 2021 г. в 14:44, Никита Сафонов <
> > > > > vlasovpavel2...@gmail.com
> > > > > > > >:
> > > > > > > > >
> > > > > > > > > > Hi Denis,
> > > > > > > > > >
> > > > > > > > > > Thanks a lot!
> > > > > > > > > > I'll update my PR's accordingly.
> > > > > > > > > >
> > > > > > > > > > Regards,
> > > > > > > > > > Nikita
> > > > > > > > > >
> > > > > > > > > > сб, 23 янв. 2021 г. в 00:59, Denis Magda <
> > dma...@apache.org>:
> > > > > > > > > >
> > > > > > > > > > > Nikita, thanks. I reviewed those and shared some
> > suggestions.
> > > > > > > Please take
> > > > > > > > > > > them into 

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

[Никита Сафонов]

Hi Maxim,

I can take a look!

Moreover, I'm finishing the work on the remaining documentation tickets.
I do believe that I'll be able to provide several PR's tomorrow and
complete the rest in a couple of days.
I'll give the precise estimate tomorrow as I'm still waiting for some info
from the dev side.

Regards,
Nikita

ср, 3 февр. 2021 г. в 22:40, Maxim Muzafarov :

> Folks,
>
>
> I've prepared the RELEASE_NOTES.
> Would anyone take a look at the PR [2] [1]?
>
>
> [1] https://issues.apache.org/jira/browse/IGNITE-14069
> [2] https://github.com/apache/ignite/pull/8748/files
>
> On Tue, 2 Feb 2021 at 22:13, Maxim Muzafarov  wrote:
> >
> > Folks,
> >
> > I've prepared first benchmarks comparing 2.9.1 vs 2.10 [1].
> > Everything looks good at the first glance.
> >
> >
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.10#ApacheIgnite2.10-Benchmarks(2.9.1vs2.10)
> >
> > On Fri, 29 Jan 2021 at 18:32, Никита Сафонов 
> wrote:
> > >
> > > Hi Maxim,
> > >
> > > terrific!
> > >
> > > Then, I'll continue with the tasks on the list.
> > >
> > > Thank you,
> > > Nikita
> > >
> > > чт, 28 янв. 2021 г. в 22:44, Maxim Muzafarov :
> > >
> > > > Hello Nikita,
> > > >
> > > > Thank you for sharing the state.
> > > >
> > > > I think we can move on to the next stages of the release. There are a
> > > > few important steps left to do: release_notes, stress testing. This
> > > > may take some time, so we still have time to complete the rest of the
> > > > documentation tasks.
> > > >
> > > > On Thu, 28 Jan 2021 at 02:51, Никита Сафонов <
> vlasovpavel2...@gmail.com>
> > > > wrote:
> > > > >
> > > > > Hi Maxim et al,
> > > > >
> > > > > thank you!
> > > > >
> > > > > The rest of the documentation tasks for important features are also
> > > > > completed.
> > > > >
> > > > > Nevertheless, there are still some items (the ones on my list that
> do not
> > > > > have any doc tasks) that can be done for the 2.10 release.
> > > > > If you want them to be included, I will try to provide patches
> ASAP. If
> > > > > not, I am still ready to create the documentation for them and
> provide it
> > > > > later.
> > > > >
> > > > > So, I will fully rely on your decision.
> > > > >
> > > > > Regards,
> > > > >
> > > > > Nikita
> > > > >
> > > > > вт, 26 янв. 2021 г. в 23:08, Maxim Muzafarov :
> > > > >
> > > > > > Nikita, Folks,
> > > > > >
> > > > > > All documentation tasks from the *[list #2]* [1] that you
> mentioned
> > > > > > above have been processed and merged to the release branch.
> > > > > >
> > > > > > [1]
> > > > > >
> > > >
> http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-Apache-Ignite-Release-2-10-time-scope-manager-tp50037p51061.html
> > > > > >
> > > > > > On Mon, 25 Jan 2021 at 18:59, Maxim Muzafarov  >
> > > > wrote:
> > > > > > >
> > > > > > > Shiva,
> > > > > > >
> > > > > > > I've cherry-picked the issue to 2.10 branch.
> > > > > > > https://issues.apache.org/jira/browse/IGNITE-13912
> > > > > > >
> > > > > > > Ilya,
> > > > > > >
> > > > > > > Thank you for preparing the patch. I've cherry-picked to 2.10
> it too.
> > > > > > > https://issues.apache.org/jira/browse/IGNITE-14039
> > > > > > >
> > > > > > > On Mon, 25 Jan 2021 at 17:50, Ilya Kasnacheev <
> > > > ilya.kasnach...@gmail.com>
> > > > > > wrote:
> > > > > > > >
> > > > > > > > Hello!
> > > > > > > >
> > > > > > > > I have pushed the developer warning, javadoc warning and
> > > > documentation
> > > > > > > > update to https://issues.apache.org/jira/browse/IGNITE-14039
> > > > about the
> > > > > > > > dangers of WAL state change.
> > > > > > > >
> > > > > > > > Please cherry-pick it to 2.10 branch or mention me if it's
> OK for
> > > > me
> > > > > > to do
> > > > > > > > this.
> > > > > > > >
> > > > > > > > Regards,
> > > > > > > > --
> > > > > > > > Ilya Kasnacheev
> > > > > > > >
> > > > > > > >
> > > > > > > > пн, 25 янв. 2021 г. в 14:44, Никита Сафонов <
> > > > vlasovpavel2...@gmail.com
> > > > > > >:
> > > > > > > >
> > > > > > > > > Hi Denis,
> > > > > > > > >
> > > > > > > > > Thanks a lot!
> > > > > > > > > I'll update my PR's accordingly.
> > > > > > > > >
> > > > > > > > > Regards,
> > > > > > > > > Nikita
> > > > > > > > >
> > > > > > > > > сб, 23 янв. 2021 г. в 00:59, Denis Magda <
> dma...@apache.org>:
> > > > > > > > >
> > > > > > > > > > Nikita, thanks. I reviewed those and shared some
> suggestions.
> > > > > > Please take
> > > > > > > > > > them into consideration.
> > > > > > > > > >
> > > > > > > > > > -
> > > > > > > > > > Denis
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > On Fri, Jan 22, 2021 at 1:45 PM Никита Сафонов <
> > > > > > > > > vlasovpavel2...@gmail.com>
> > > > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > Hi everyone,
> > > > > > > > > > >
> > > > > > > > > > > The following documentation tasks for the important
> features
> > > > now
> > > > > > have
> > > > > > > > > > PATCH
> > > > > > > > > > > AVAILABLE status:
> > > > > > > > > > >
> > > > > > > > > > 

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

[Maxim Muzafarov]

Folks,


I've prepared the RELEASE_NOTES.
Would anyone take a look at the PR [2] [1]?


[1] https://issues.apache.org/jira/browse/IGNITE-14069
[2] https://github.com/apache/ignite/pull/8748/files

On Tue, 2 Feb 2021 at 22:13, Maxim Muzafarov  wrote:
>
> Folks,
>
> I've prepared first benchmarks comparing 2.9.1 vs 2.10 [1].
> Everything looks good at the first glance.
>
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.10#ApacheIgnite2.10-Benchmarks(2.9.1vs2.10)
>
> On Fri, 29 Jan 2021 at 18:32, Никита Сафонов  
> wrote:
> >
> > Hi Maxim,
> >
> > terrific!
> >
> > Then, I'll continue with the tasks on the list.
> >
> > Thank you,
> > Nikita
> >
> > чт, 28 янв. 2021 г. в 22:44, Maxim Muzafarov :
> >
> > > Hello Nikita,
> > >
> > > Thank you for sharing the state.
> > >
> > > I think we can move on to the next stages of the release. There are a
> > > few important steps left to do: release_notes, stress testing. This
> > > may take some time, so we still have time to complete the rest of the
> > > documentation tasks.
> > >
> > > On Thu, 28 Jan 2021 at 02:51, Никита Сафонов 
> > > wrote:
> > > >
> > > > Hi Maxim et al,
> > > >
> > > > thank you!
> > > >
> > > > The rest of the documentation tasks for important features are also
> > > > completed.
> > > >
> > > > Nevertheless, there are still some items (the ones on my list that do 
> > > > not
> > > > have any doc tasks) that can be done for the 2.10 release.
> > > > If you want them to be included, I will try to provide patches ASAP. If
> > > > not, I am still ready to create the documentation for them and provide 
> > > > it
> > > > later.
> > > >
> > > > So, I will fully rely on your decision.
> > > >
> > > > Regards,
> > > >
> > > > Nikita
> > > >
> > > > вт, 26 янв. 2021 г. в 23:08, Maxim Muzafarov :
> > > >
> > > > > Nikita, Folks,
> > > > >
> > > > > All documentation tasks from the *[list #2]* [1] that you mentioned
> > > > > above have been processed and merged to the release branch.
> > > > >
> > > > > [1]
> > > > >
> > > http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-Apache-Ignite-Release-2-10-time-scope-manager-tp50037p51061.html
> > > > >
> > > > > On Mon, 25 Jan 2021 at 18:59, Maxim Muzafarov 
> > > wrote:
> > > > > >
> > > > > > Shiva,
> > > > > >
> > > > > > I've cherry-picked the issue to 2.10 branch.
> > > > > > https://issues.apache.org/jira/browse/IGNITE-13912
> > > > > >
> > > > > > Ilya,
> > > > > >
> > > > > > Thank you for preparing the patch. I've cherry-picked to 2.10 it 
> > > > > > too.
> > > > > > https://issues.apache.org/jira/browse/IGNITE-14039
> > > > > >
> > > > > > On Mon, 25 Jan 2021 at 17:50, Ilya Kasnacheev <
> > > ilya.kasnach...@gmail.com>
> > > > > wrote:
> > > > > > >
> > > > > > > Hello!
> > > > > > >
> > > > > > > I have pushed the developer warning, javadoc warning and
> > > documentation
> > > > > > > update to https://issues.apache.org/jira/browse/IGNITE-14039
> > > about the
> > > > > > > dangers of WAL state change.
> > > > > > >
> > > > > > > Please cherry-pick it to 2.10 branch or mention me if it's OK for
> > > me
> > > > > to do
> > > > > > > this.
> > > > > > >
> > > > > > > Regards,
> > > > > > > --
> > > > > > > Ilya Kasnacheev
> > > > > > >
> > > > > > >
> > > > > > > пн, 25 янв. 2021 г. в 14:44, Никита Сафонов <
> > > vlasovpavel2...@gmail.com
> > > > > >:
> > > > > > >
> > > > > > > > Hi Denis,
> > > > > > > >
> > > > > > > > Thanks a lot!
> > > > > > > > I'll update my PR's accordingly.
> > > > > > > >
> > > > > > > > Regards,
> > > > > > > > Nikita
> > > > > > > >
> > > > > > > > сб, 23 янв. 2021 г. в 00:59, Denis Magda :
> > > > > > > >
> > > > > > > > > Nikita, thanks. I reviewed those and shared some suggestions.
> > > > > Please take
> > > > > > > > > them into consideration.
> > > > > > > > >
> > > > > > > > > -
> > > > > > > > > Denis
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On Fri, Jan 22, 2021 at 1:45 PM Никита Сафонов <
> > > > > > > > vlasovpavel2...@gmail.com>
> > > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > Hi everyone,
> > > > > > > > > >
> > > > > > > > > > The following documentation tasks for the important features
> > > now
> > > > > have
> > > > > > > > > PATCH
> > > > > > > > > > AVAILABLE status:
> > > > > > > > > >
> > > > > > > > > >- Caches warming up strategy -
> > > > > > > > > >
> > > > > https://issues.apache.org/jira/browse/IGNITE-13385?src=confmacro
> > > > > > > > > >- Update on JMX default configuration removal -
> > > > > > > > > >
> > > > > https://issues.apache.org/jira/browse/IGNITE-13606?src=confmacro
> > > > > > > > > >- Control.sh indexes manipulation commands -
> > > > > > > > > >
> > > > > https://issues.apache.org/jira/browse/IGNITE-13285?src=confmacro
> > > > > > > > > >
> > > > > > > > > > Please see the PR's attached to the tickets.
> > > > > > > > > >
> > > > > > > > > > Thank you!
> > > > > > > > > >
> > > > > > > > > > Regards,
> > > > > > > > > > Nikita
> > > > > > > > > >
> > 

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

[Maxim Muzafarov]

Folks,

I've prepared first benchmarks comparing 2.9.1 vs 2.10 [1].
Everything looks good at the first glance.

https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.10#ApacheIgnite2.10-Benchmarks(2.9.1vs2.10)

On Fri, 29 Jan 2021 at 18:32, Никита Сафонов  wrote:
>
> Hi Maxim,
>
> terrific!
>
> Then, I'll continue with the tasks on the list.
>
> Thank you,
> Nikita
>
> чт, 28 янв. 2021 г. в 22:44, Maxim Muzafarov :
>
> > Hello Nikita,
> >
> > Thank you for sharing the state.
> >
> > I think we can move on to the next stages of the release. There are a
> > few important steps left to do: release_notes, stress testing. This
> > may take some time, so we still have time to complete the rest of the
> > documentation tasks.
> >
> > On Thu, 28 Jan 2021 at 02:51, Никита Сафонов 
> > wrote:
> > >
> > > Hi Maxim et al,
> > >
> > > thank you!
> > >
> > > The rest of the documentation tasks for important features are also
> > > completed.
> > >
> > > Nevertheless, there are still some items (the ones on my list that do not
> > > have any doc tasks) that can be done for the 2.10 release.
> > > If you want them to be included, I will try to provide patches ASAP. If
> > > not, I am still ready to create the documentation for them and provide it
> > > later.
> > >
> > > So, I will fully rely on your decision.
> > >
> > > Regards,
> > >
> > > Nikita
> > >
> > > вт, 26 янв. 2021 г. в 23:08, Maxim Muzafarov :
> > >
> > > > Nikita, Folks,
> > > >
> > > > All documentation tasks from the *[list #2]* [1] that you mentioned
> > > > above have been processed and merged to the release branch.
> > > >
> > > > [1]
> > > >
> > http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-Apache-Ignite-Release-2-10-time-scope-manager-tp50037p51061.html
> > > >
> > > > On Mon, 25 Jan 2021 at 18:59, Maxim Muzafarov 
> > wrote:
> > > > >
> > > > > Shiva,
> > > > >
> > > > > I've cherry-picked the issue to 2.10 branch.
> > > > > https://issues.apache.org/jira/browse/IGNITE-13912
> > > > >
> > > > > Ilya,
> > > > >
> > > > > Thank you for preparing the patch. I've cherry-picked to 2.10 it too.
> > > > > https://issues.apache.org/jira/browse/IGNITE-14039
> > > > >
> > > > > On Mon, 25 Jan 2021 at 17:50, Ilya Kasnacheev <
> > ilya.kasnach...@gmail.com>
> > > > wrote:
> > > > > >
> > > > > > Hello!
> > > > > >
> > > > > > I have pushed the developer warning, javadoc warning and
> > documentation
> > > > > > update to https://issues.apache.org/jira/browse/IGNITE-14039
> > about the
> > > > > > dangers of WAL state change.
> > > > > >
> > > > > > Please cherry-pick it to 2.10 branch or mention me if it's OK for
> > me
> > > > to do
> > > > > > this.
> > > > > >
> > > > > > Regards,
> > > > > > --
> > > > > > Ilya Kasnacheev
> > > > > >
> > > > > >
> > > > > > пн, 25 янв. 2021 г. в 14:44, Никита Сафонов <
> > vlasovpavel2...@gmail.com
> > > > >:
> > > > > >
> > > > > > > Hi Denis,
> > > > > > >
> > > > > > > Thanks a lot!
> > > > > > > I'll update my PR's accordingly.
> > > > > > >
> > > > > > > Regards,
> > > > > > > Nikita
> > > > > > >
> > > > > > > сб, 23 янв. 2021 г. в 00:59, Denis Magda :
> > > > > > >
> > > > > > > > Nikita, thanks. I reviewed those and shared some suggestions.
> > > > Please take
> > > > > > > > them into consideration.
> > > > > > > >
> > > > > > > > -
> > > > > > > > Denis
> > > > > > > >
> > > > > > > >
> > > > > > > > On Fri, Jan 22, 2021 at 1:45 PM Никита Сафонов <
> > > > > > > vlasovpavel2...@gmail.com>
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > Hi everyone,
> > > > > > > > >
> > > > > > > > > The following documentation tasks for the important features
> > now
> > > > have
> > > > > > > > PATCH
> > > > > > > > > AVAILABLE status:
> > > > > > > > >
> > > > > > > > >- Caches warming up strategy -
> > > > > > > > >
> > > > https://issues.apache.org/jira/browse/IGNITE-13385?src=confmacro
> > > > > > > > >- Update on JMX default configuration removal -
> > > > > > > > >
> > > > https://issues.apache.org/jira/browse/IGNITE-13606?src=confmacro
> > > > > > > > >- Control.sh indexes manipulation commands -
> > > > > > > > >
> > > > https://issues.apache.org/jira/browse/IGNITE-13285?src=confmacro
> > > > > > > > >
> > > > > > > > > Please see the PR's attached to the tickets.
> > > > > > > > >
> > > > > > > > > Thank you!
> > > > > > > > >
> > > > > > > > > Regards,
> > > > > > > > > Nikita
> > > > > > > > >
> > > > > > > > > пт, 22 янв. 2021 г. в 18:03, shm :
> > > > > > > > >
> > > > > > > > > > Hi All,
> > > > > > > > > > Can you please also include a critical ticket
> > > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-13912
> > > > > > > > > >  to 2.10 In terms of functionality it is a blocker. Still
> > some
> > > > > > > > debugging
> > > > > > > > > is
> > > > > > > > > > going on related to this issue.
> > > > > > > > > >
> > > > > > > > > > Thanks,
> > > > > > > > > > Shiva
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > 

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

[Никита Сафонов]

Hi Maxim,

terrific!

Then, I'll continue with the tasks on the list.

Thank you,
Nikita

чт, 28 янв. 2021 г. в 22:44, Maxim Muzafarov :

> Hello Nikita,
>
> Thank you for sharing the state.
>
> I think we can move on to the next stages of the release. There are a
> few important steps left to do: release_notes, stress testing. This
> may take some time, so we still have time to complete the rest of the
> documentation tasks.
>
> On Thu, 28 Jan 2021 at 02:51, Никита Сафонов 
> wrote:
> >
> > Hi Maxim et al,
> >
> > thank you!
> >
> > The rest of the documentation tasks for important features are also
> > completed.
> >
> > Nevertheless, there are still some items (the ones on my list that do not
> > have any doc tasks) that can be done for the 2.10 release.
> > If you want them to be included, I will try to provide patches ASAP. If
> > not, I am still ready to create the documentation for them and provide it
> > later.
> >
> > So, I will fully rely on your decision.
> >
> > Regards,
> >
> > Nikita
> >
> > вт, 26 янв. 2021 г. в 23:08, Maxim Muzafarov :
> >
> > > Nikita, Folks,
> > >
> > > All documentation tasks from the *[list #2]* [1] that you mentioned
> > > above have been processed and merged to the release branch.
> > >
> > > [1]
> > >
> http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-Apache-Ignite-Release-2-10-time-scope-manager-tp50037p51061.html
> > >
> > > On Mon, 25 Jan 2021 at 18:59, Maxim Muzafarov 
> wrote:
> > > >
> > > > Shiva,
> > > >
> > > > I've cherry-picked the issue to 2.10 branch.
> > > > https://issues.apache.org/jira/browse/IGNITE-13912
> > > >
> > > > Ilya,
> > > >
> > > > Thank you for preparing the patch. I've cherry-picked to 2.10 it too.
> > > > https://issues.apache.org/jira/browse/IGNITE-14039
> > > >
> > > > On Mon, 25 Jan 2021 at 17:50, Ilya Kasnacheev <
> ilya.kasnach...@gmail.com>
> > > wrote:
> > > > >
> > > > > Hello!
> > > > >
> > > > > I have pushed the developer warning, javadoc warning and
> documentation
> > > > > update to https://issues.apache.org/jira/browse/IGNITE-14039
> about the
> > > > > dangers of WAL state change.
> > > > >
> > > > > Please cherry-pick it to 2.10 branch or mention me if it's OK for
> me
> > > to do
> > > > > this.
> > > > >
> > > > > Regards,
> > > > > --
> > > > > Ilya Kasnacheev
> > > > >
> > > > >
> > > > > пн, 25 янв. 2021 г. в 14:44, Никита Сафонов <
> vlasovpavel2...@gmail.com
> > > >:
> > > > >
> > > > > > Hi Denis,
> > > > > >
> > > > > > Thanks a lot!
> > > > > > I'll update my PR's accordingly.
> > > > > >
> > > > > > Regards,
> > > > > > Nikita
> > > > > >
> > > > > > сб, 23 янв. 2021 г. в 00:59, Denis Magda :
> > > > > >
> > > > > > > Nikita, thanks. I reviewed those and shared some suggestions.
> > > Please take
> > > > > > > them into consideration.
> > > > > > >
> > > > > > > -
> > > > > > > Denis
> > > > > > >
> > > > > > >
> > > > > > > On Fri, Jan 22, 2021 at 1:45 PM Никита Сафонов <
> > > > > > vlasovpavel2...@gmail.com>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Hi everyone,
> > > > > > > >
> > > > > > > > The following documentation tasks for the important features
> now
> > > have
> > > > > > > PATCH
> > > > > > > > AVAILABLE status:
> > > > > > > >
> > > > > > > >- Caches warming up strategy -
> > > > > > > >
> > > https://issues.apache.org/jira/browse/IGNITE-13385?src=confmacro
> > > > > > > >- Update on JMX default configuration removal -
> > > > > > > >
> > > https://issues.apache.org/jira/browse/IGNITE-13606?src=confmacro
> > > > > > > >- Control.sh indexes manipulation commands -
> > > > > > > >
> > > https://issues.apache.org/jira/browse/IGNITE-13285?src=confmacro
> > > > > > > >
> > > > > > > > Please see the PR's attached to the tickets.
> > > > > > > >
> > > > > > > > Thank you!
> > > > > > > >
> > > > > > > > Regards,
> > > > > > > > Nikita
> > > > > > > >
> > > > > > > > пт, 22 янв. 2021 г. в 18:03, shm :
> > > > > > > >
> > > > > > > > > Hi All,
> > > > > > > > > Can you please also include a critical ticket
> > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-13912
> > > > > > > > >  to 2.10 In terms of functionality it is a blocker. Still
> some
> > > > > > > debugging
> > > > > > > > is
> > > > > > > > > going on related to this issue.
> > > > > > > > >
> > > > > > > > > Thanks,
> > > > > > > > > Shiva
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > --
> > > > > > > > > Sent from:
> > > http://apache-ignite-developers.2346864.n4.nabble.com/
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > >
>

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

[Maxim Muzafarov]

Hello Nikita,

Thank you for sharing the state.

I think we can move on to the next stages of the release. There are a
few important steps left to do: release_notes, stress testing. This
may take some time, so we still have time to complete the rest of the
documentation tasks.

On Thu, 28 Jan 2021 at 02:51, Никита Сафонов  wrote:
>
> Hi Maxim et al,
>
> thank you!
>
> The rest of the documentation tasks for important features are also
> completed.
>
> Nevertheless, there are still some items (the ones on my list that do not
> have any doc tasks) that can be done for the 2.10 release.
> If you want them to be included, I will try to provide patches ASAP. If
> not, I am still ready to create the documentation for them and provide it
> later.
>
> So, I will fully rely on your decision.
>
> Regards,
>
> Nikita
>
> вт, 26 янв. 2021 г. в 23:08, Maxim Muzafarov :
>
> > Nikita, Folks,
> >
> > All documentation tasks from the *[list #2]* [1] that you mentioned
> > above have been processed and merged to the release branch.
> >
> > [1]
> > http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-Apache-Ignite-Release-2-10-time-scope-manager-tp50037p51061.html
> >
> > On Mon, 25 Jan 2021 at 18:59, Maxim Muzafarov  wrote:
> > >
> > > Shiva,
> > >
> > > I've cherry-picked the issue to 2.10 branch.
> > > https://issues.apache.org/jira/browse/IGNITE-13912
> > >
> > > Ilya,
> > >
> > > Thank you for preparing the patch. I've cherry-picked to 2.10 it too.
> > > https://issues.apache.org/jira/browse/IGNITE-14039
> > >
> > > On Mon, 25 Jan 2021 at 17:50, Ilya Kasnacheev 
> > wrote:
> > > >
> > > > Hello!
> > > >
> > > > I have pushed the developer warning, javadoc warning and documentation
> > > > update to https://issues.apache.org/jira/browse/IGNITE-14039 about the
> > > > dangers of WAL state change.
> > > >
> > > > Please cherry-pick it to 2.10 branch or mention me if it's OK for me
> > to do
> > > > this.
> > > >
> > > > Regards,
> > > > --
> > > > Ilya Kasnacheev
> > > >
> > > >
> > > > пн, 25 янв. 2021 г. в 14:44, Никита Сафонов  > >:
> > > >
> > > > > Hi Denis,
> > > > >
> > > > > Thanks a lot!
> > > > > I'll update my PR's accordingly.
> > > > >
> > > > > Regards,
> > > > > Nikita
> > > > >
> > > > > сб, 23 янв. 2021 г. в 00:59, Denis Magda :
> > > > >
> > > > > > Nikita, thanks. I reviewed those and shared some suggestions.
> > Please take
> > > > > > them into consideration.
> > > > > >
> > > > > > -
> > > > > > Denis
> > > > > >
> > > > > >
> > > > > > On Fri, Jan 22, 2021 at 1:45 PM Никита Сафонов <
> > > > > vlasovpavel2...@gmail.com>
> > > > > > wrote:
> > > > > >
> > > > > > > Hi everyone,
> > > > > > >
> > > > > > > The following documentation tasks for the important features now
> > have
> > > > > > PATCH
> > > > > > > AVAILABLE status:
> > > > > > >
> > > > > > >- Caches warming up strategy -
> > > > > > >
> > https://issues.apache.org/jira/browse/IGNITE-13385?src=confmacro
> > > > > > >- Update on JMX default configuration removal -
> > > > > > >
> > https://issues.apache.org/jira/browse/IGNITE-13606?src=confmacro
> > > > > > >- Control.sh indexes manipulation commands -
> > > > > > >
> > https://issues.apache.org/jira/browse/IGNITE-13285?src=confmacro
> > > > > > >
> > > > > > > Please see the PR's attached to the tickets.
> > > > > > >
> > > > > > > Thank you!
> > > > > > >
> > > > > > > Regards,
> > > > > > > Nikita
> > > > > > >
> > > > > > > пт, 22 янв. 2021 г. в 18:03, shm :
> > > > > > >
> > > > > > > > Hi All,
> > > > > > > > Can you please also include a critical ticket
> > > > > > > > https://issues.apache.org/jira/browse/IGNITE-13912
> > > > > > > >  to 2.10 In terms of functionality it is a blocker. Still some
> > > > > > debugging
> > > > > > > is
> > > > > > > > going on related to this issue.
> > > > > > > >
> > > > > > > > Thanks,
> > > > > > > > Shiva
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > --
> > > > > > > > Sent from:
> > http://apache-ignite-developers.2346864.n4.nabble.com/
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> >

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

[Никита Сафонов]

Hi Maxim et al,

thank you!

The rest of the documentation tasks for important features are also
completed.

Nevertheless, there are still some items (the ones on my list that do not
have any doc tasks) that can be done for the 2.10 release.
If you want them to be included, I will try to provide patches ASAP. If
not, I am still ready to create the documentation for them and provide it
later.

So, I will fully rely on your decision.

Regards,

Nikita

вт, 26 янв. 2021 г. в 23:08, Maxim Muzafarov :

> Nikita, Folks,
>
> All documentation tasks from the *[list #2]* [1] that you mentioned
> above have been processed and merged to the release branch.
>
> [1]
> http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-Apache-Ignite-Release-2-10-time-scope-manager-tp50037p51061.html
>
> On Mon, 25 Jan 2021 at 18:59, Maxim Muzafarov  wrote:
> >
> > Shiva,
> >
> > I've cherry-picked the issue to 2.10 branch.
> > https://issues.apache.org/jira/browse/IGNITE-13912
> >
> > Ilya,
> >
> > Thank you for preparing the patch. I've cherry-picked to 2.10 it too.
> > https://issues.apache.org/jira/browse/IGNITE-14039
> >
> > On Mon, 25 Jan 2021 at 17:50, Ilya Kasnacheev 
> wrote:
> > >
> > > Hello!
> > >
> > > I have pushed the developer warning, javadoc warning and documentation
> > > update to https://issues.apache.org/jira/browse/IGNITE-14039 about the
> > > dangers of WAL state change.
> > >
> > > Please cherry-pick it to 2.10 branch or mention me if it's OK for me
> to do
> > > this.
> > >
> > > Regards,
> > > --
> > > Ilya Kasnacheev
> > >
> > >
> > > пн, 25 янв. 2021 г. в 14:44, Никита Сафонов  >:
> > >
> > > > Hi Denis,
> > > >
> > > > Thanks a lot!
> > > > I'll update my PR's accordingly.
> > > >
> > > > Regards,
> > > > Nikita
> > > >
> > > > сб, 23 янв. 2021 г. в 00:59, Denis Magda :
> > > >
> > > > > Nikita, thanks. I reviewed those and shared some suggestions.
> Please take
> > > > > them into consideration.
> > > > >
> > > > > -
> > > > > Denis
> > > > >
> > > > >
> > > > > On Fri, Jan 22, 2021 at 1:45 PM Никита Сафонов <
> > > > vlasovpavel2...@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > Hi everyone,
> > > > > >
> > > > > > The following documentation tasks for the important features now
> have
> > > > > PATCH
> > > > > > AVAILABLE status:
> > > > > >
> > > > > >- Caches warming up strategy -
> > > > > >
> https://issues.apache.org/jira/browse/IGNITE-13385?src=confmacro
> > > > > >- Update on JMX default configuration removal -
> > > > > >
> https://issues.apache.org/jira/browse/IGNITE-13606?src=confmacro
> > > > > >- Control.sh indexes manipulation commands -
> > > > > >
> https://issues.apache.org/jira/browse/IGNITE-13285?src=confmacro
> > > > > >
> > > > > > Please see the PR's attached to the tickets.
> > > > > >
> > > > > > Thank you!
> > > > > >
> > > > > > Regards,
> > > > > > Nikita
> > > > > >
> > > > > > пт, 22 янв. 2021 г. в 18:03, shm :
> > > > > >
> > > > > > > Hi All,
> > > > > > > Can you please also include a critical ticket
> > > > > > > https://issues.apache.org/jira/browse/IGNITE-13912
> > > > > > >  to 2.10 In terms of functionality it is a blocker. Still some
> > > > > debugging
> > > > > > is
> > > > > > > going on related to this issue.
> > > > > > >
> > > > > > > Thanks,
> > > > > > > Shiva
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Sent from:
> http://apache-ignite-developers.2346864.n4.nabble.com/
> > > > > > >
> > > > > >
> > > > >
> > > >
>

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

[Maxim Muzafarov]

Nikita, Folks,

All documentation tasks from the *[list #2]* [1] that you mentioned
above have been processed and merged to the release branch.

[1] 
http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-Apache-Ignite-Release-2-10-time-scope-manager-tp50037p51061.html

On Mon, 25 Jan 2021 at 18:59, Maxim Muzafarov  wrote:
>
> Shiva,
>
> I've cherry-picked the issue to 2.10 branch.
> https://issues.apache.org/jira/browse/IGNITE-13912
>
> Ilya,
>
> Thank you for preparing the patch. I've cherry-picked to 2.10 it too.
> https://issues.apache.org/jira/browse/IGNITE-14039
>
> On Mon, 25 Jan 2021 at 17:50, Ilya Kasnacheev  
> wrote:
> >
> > Hello!
> >
> > I have pushed the developer warning, javadoc warning and documentation
> > update to https://issues.apache.org/jira/browse/IGNITE-14039 about the
> > dangers of WAL state change.
> >
> > Please cherry-pick it to 2.10 branch or mention me if it's OK for me to do
> > this.
> >
> > Regards,
> > --
> > Ilya Kasnacheev
> >
> >
> > пн, 25 янв. 2021 г. в 14:44, Никита Сафонов :
> >
> > > Hi Denis,
> > >
> > > Thanks a lot!
> > > I'll update my PR's accordingly.
> > >
> > > Regards,
> > > Nikita
> > >
> > > сб, 23 янв. 2021 г. в 00:59, Denis Magda :
> > >
> > > > Nikita, thanks. I reviewed those and shared some suggestions. Please 
> > > > take
> > > > them into consideration.
> > > >
> > > > -
> > > > Denis
> > > >
> > > >
> > > > On Fri, Jan 22, 2021 at 1:45 PM Никита Сафонов <
> > > vlasovpavel2...@gmail.com>
> > > > wrote:
> > > >
> > > > > Hi everyone,
> > > > >
> > > > > The following documentation tasks for the important features now have
> > > > PATCH
> > > > > AVAILABLE status:
> > > > >
> > > > >- Caches warming up strategy -
> > > > >https://issues.apache.org/jira/browse/IGNITE-13385?src=confmacro
> > > > >- Update on JMX default configuration removal -
> > > > >https://issues.apache.org/jira/browse/IGNITE-13606?src=confmacro
> > > > >- Control.sh indexes manipulation commands -
> > > > >https://issues.apache.org/jira/browse/IGNITE-13285?src=confmacro
> > > > >
> > > > > Please see the PR's attached to the tickets.
> > > > >
> > > > > Thank you!
> > > > >
> > > > > Regards,
> > > > > Nikita
> > > > >
> > > > > пт, 22 янв. 2021 г. в 18:03, shm :
> > > > >
> > > > > > Hi All,
> > > > > > Can you please also include a critical ticket
> > > > > > https://issues.apache.org/jira/browse/IGNITE-13912
> > > > > >  to 2.10 In terms of functionality it is a blocker. Still some
> > > > debugging
> > > > > is
> > > > > > going on related to this issue.
> > > > > >
> > > > > > Thanks,
> > > > > > Shiva
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
> > > > > >
> > > > >
> > > >
> > >

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

[Maxim Muzafarov]

Shiva,

I've cherry-picked the issue to 2.10 branch.
https://issues.apache.org/jira/browse/IGNITE-13912

Ilya,

Thank you for preparing the patch. I've cherry-picked to 2.10 it too.
https://issues.apache.org/jira/browse/IGNITE-14039

On Mon, 25 Jan 2021 at 17:50, Ilya Kasnacheev  wrote:
>
> Hello!
>
> I have pushed the developer warning, javadoc warning and documentation
> update to https://issues.apache.org/jira/browse/IGNITE-14039 about the
> dangers of WAL state change.
>
> Please cherry-pick it to 2.10 branch or mention me if it's OK for me to do
> this.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> пн, 25 янв. 2021 г. в 14:44, Никита Сафонов :
>
> > Hi Denis,
> >
> > Thanks a lot!
> > I'll update my PR's accordingly.
> >
> > Regards,
> > Nikita
> >
> > сб, 23 янв. 2021 г. в 00:59, Denis Magda :
> >
> > > Nikita, thanks. I reviewed those and shared some suggestions. Please take
> > > them into consideration.
> > >
> > > -
> > > Denis
> > >
> > >
> > > On Fri, Jan 22, 2021 at 1:45 PM Никита Сафонов <
> > vlasovpavel2...@gmail.com>
> > > wrote:
> > >
> > > > Hi everyone,
> > > >
> > > > The following documentation tasks for the important features now have
> > > PATCH
> > > > AVAILABLE status:
> > > >
> > > >- Caches warming up strategy -
> > > >https://issues.apache.org/jira/browse/IGNITE-13385?src=confmacro
> > > >- Update on JMX default configuration removal -
> > > >https://issues.apache.org/jira/browse/IGNITE-13606?src=confmacro
> > > >- Control.sh indexes manipulation commands -
> > > >https://issues.apache.org/jira/browse/IGNITE-13285?src=confmacro
> > > >
> > > > Please see the PR's attached to the tickets.
> > > >
> > > > Thank you!
> > > >
> > > > Regards,
> > > > Nikita
> > > >
> > > > пт, 22 янв. 2021 г. в 18:03, shm :
> > > >
> > > > > Hi All,
> > > > > Can you please also include a critical ticket
> > > > > https://issues.apache.org/jira/browse/IGNITE-13912
> > > > >  to 2.10 In terms of functionality it is a blocker. Still some
> > > debugging
> > > > is
> > > > > going on related to this issue.
> > > > >
> > > > > Thanks,
> > > > > Shiva
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
> > > > >
> > > >
> > >
> >

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

[Ilya Kasnacheev]

Hello!

I have pushed the developer warning, javadoc warning and documentation
update to https://issues.apache.org/jira/browse/IGNITE-14039 about the
dangers of WAL state change.

Please cherry-pick it to 2.10 branch or mention me if it's OK for me to do
this.

Regards,
-- 
Ilya Kasnacheev


пн, 25 янв. 2021 г. в 14:44, Никита Сафонов :

> Hi Denis,
>
> Thanks a lot!
> I'll update my PR's accordingly.
>
> Regards,
> Nikita
>
> сб, 23 янв. 2021 г. в 00:59, Denis Magda :
>
> > Nikita, thanks. I reviewed those and shared some suggestions. Please take
> > them into consideration.
> >
> > -
> > Denis
> >
> >
> > On Fri, Jan 22, 2021 at 1:45 PM Никита Сафонов <
> vlasovpavel2...@gmail.com>
> > wrote:
> >
> > > Hi everyone,
> > >
> > > The following documentation tasks for the important features now have
> > PATCH
> > > AVAILABLE status:
> > >
> > >- Caches warming up strategy -
> > >https://issues.apache.org/jira/browse/IGNITE-13385?src=confmacro
> > >- Update on JMX default configuration removal -
> > >https://issues.apache.org/jira/browse/IGNITE-13606?src=confmacro
> > >- Control.sh indexes manipulation commands -
> > >https://issues.apache.org/jira/browse/IGNITE-13285?src=confmacro
> > >
> > > Please see the PR's attached to the tickets.
> > >
> > > Thank you!
> > >
> > > Regards,
> > > Nikita
> > >
> > > пт, 22 янв. 2021 г. в 18:03, shm :
> > >
> > > > Hi All,
> > > > Can you please also include a critical ticket
> > > > https://issues.apache.org/jira/browse/IGNITE-13912
> > > >  to 2.10 In terms of functionality it is a blocker. Still some
> > debugging
> > > is
> > > > going on related to this issue.
> > > >
> > > > Thanks,
> > > > Shiva
> > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
> > > >
> > >
> >
>

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

[Никита Сафонов]

Hi Denis,

Thanks a lot!
I'll update my PR's accordingly.

Regards,
Nikita

сб, 23 янв. 2021 г. в 00:59, Denis Magda :

> Nikita, thanks. I reviewed those and shared some suggestions. Please take
> them into consideration.
>
> -
> Denis
>
>
> On Fri, Jan 22, 2021 at 1:45 PM Никита Сафонов 
> wrote:
>
> > Hi everyone,
> >
> > The following documentation tasks for the important features now have
> PATCH
> > AVAILABLE status:
> >
> >- Caches warming up strategy -
> >https://issues.apache.org/jira/browse/IGNITE-13385?src=confmacro
> >- Update on JMX default configuration removal -
> >https://issues.apache.org/jira/browse/IGNITE-13606?src=confmacro
> >- Control.sh indexes manipulation commands -
> >https://issues.apache.org/jira/browse/IGNITE-13285?src=confmacro
> >
> > Please see the PR's attached to the tickets.
> >
> > Thank you!
> >
> > Regards,
> > Nikita
> >
> > пт, 22 янв. 2021 г. в 18:03, shm :
> >
> > > Hi All,
> > > Can you please also include a critical ticket
> > > https://issues.apache.org/jira/browse/IGNITE-13912
> > >  to 2.10 In terms of functionality it is a blocker. Still some
> debugging
> > is
> > > going on related to this issue.
> > >
> > > Thanks,
> > > Shiva
> > >
> > >
> > >
> > >
> > > --
> > > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
> > >
> >
>

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

[Denis Magda]

Nikita, thanks. I reviewed those and shared some suggestions. Please take
them into consideration.

-
Denis


On Fri, Jan 22, 2021 at 1:45 PM Никита Сафонов 
wrote:

> Hi everyone,
>
> The following documentation tasks for the important features now have PATCH
> AVAILABLE status:
>
>- Caches warming up strategy -
>https://issues.apache.org/jira/browse/IGNITE-13385?src=confmacro
>- Update on JMX default configuration removal -
>https://issues.apache.org/jira/browse/IGNITE-13606?src=confmacro
>- Control.sh indexes manipulation commands -
>https://issues.apache.org/jira/browse/IGNITE-13285?src=confmacro
>
> Please see the PR's attached to the tickets.
>
> Thank you!
>
> Regards,
> Nikita
>
> пт, 22 янв. 2021 г. в 18:03, shm :
>
> > Hi All,
> > Can you please also include a critical ticket
> > https://issues.apache.org/jira/browse/IGNITE-13912
> >  to 2.10 In terms of functionality it is a blocker. Still some debugging
> is
> > going on related to this issue.
> >
> > Thanks,
> > Shiva
> >
> >
> >
> >
> > --
> > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
> >
>

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

[Никита Сафонов]

Hi everyone,

The following documentation tasks for the important features now have PATCH
AVAILABLE status:

   - Caches warming up strategy -
   https://issues.apache.org/jira/browse/IGNITE-13385?src=confmacro
   - Update on JMX default configuration removal -
   https://issues.apache.org/jira/browse/IGNITE-13606?src=confmacro
   - Control.sh indexes manipulation commands -
   https://issues.apache.org/jira/browse/IGNITE-13285?src=confmacro

Please see the PR's attached to the tickets.

Thank you!

Regards,
Nikita

пт, 22 янв. 2021 г. в 18:03, shm :

> Hi All,
> Can you please also include a critical ticket
> https://issues.apache.org/jira/browse/IGNITE-13912
>  to 2.10 In terms of functionality it is a blocker. Still some debugging is
> going on related to this issue.
>
> Thanks,
> Shiva
>
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>

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

[shm]

Hi All,
Can you please also include a critical ticket
https://issues.apache.org/jira/browse/IGNITE-13912
 to 2.10 In terms of functionality it is a blocker. Still some debugging is
going on related to this issue.

Thanks,
Shiva




--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

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

[Никита Сафонов]

Hi everyone,

I'm finishing my work on the documentation tasks for the following
important features:


   - Caches warming up strategy -
   https://issues.apache.org/jira/browse/IGNITE-13385?src=confmacro
   - Update on JMX default configuration removal -
   https://issues.apache.org/jira/browse/IGNITE-13606?src=confmacro
   - Control.sh indexes manipulation commands -
   https://issues.apache.org/jira/browse/IGNITE-13285?src=confmacro


I will provide PR's to these and some other features a bit later today.
Please be ready to review the latest changes.

Thank you!

Regards,
Nikita

чт, 21 янв. 2021 г. в 22:09, Maxim Muzafarov :

> Folks,
>
>
> This is the list of bugs which I've cherry-picked to the ignite-2.10
> branch:
>
>
> Starvation in mgmt pool caused by MetadataTask execution
> https://issues.apache.org/jira/browse/IGNITE-13960
>
> .NET: LINQ provider emits incorrect table alias for queries with JOIN
> and GROUP BY combined
> https://issues.apache.org/jira/browse/IGNITE-13754
>
> Query cancellation freezes on local lazy queries
> https://issues.apache.org/jira/browse/IGNITE-13964
>
> SQL: REPLICATED cache cannot be left-joined to PARTITIONED
> https://issues.apache.org/jira/browse/IGNITE-8732
>
> .NET: logger throws KeyNotFound on creating cache with nullable 'sbyte?'
> field
> https://issues.apache.org/jira/browse/IGNITE-12090
>
> Possible deadlock between methods from GridEncryptionManager
> https://issues.apache.org/jira/browse/IGNITE-13906
>
> OOM on creating rebalance iterator while rebalancing cache with large
> values.
> https://issues.apache.org/jira/browse/IGNITE-14003
>
> On Mon, 18 Jan 2021 at 17:20, Pavel Tupitsyn  wrote:
> >
> > Maxim,
> >
> > No objections for .NET-related cherry-picks.
> >
> > Thank you!
> >
> > On Mon, Jan 18, 2021 at 4:52 PM Никита Сафонов <
> vlasovpavel2...@gmail.com>
> > wrote:
> >
> > > Hi Maxim et al,
> > >
> > > Thank you very much!
> > > I do appreciate your help!
> > >
> > > Regards,
> > > Nikita
> > >
> > > пн, 18 янв. 2021 г. в 16:16, Maxim Muzafarov :
> > >
> > > > Folks,
> > > >
> > > > I'd like to cherry-pick these bugs to the ignite-2.10 branch.
> > > > Do you have any objections?
> > > >
> > > >
> > > > Starvation in mgmt pool caused by MetadataTask execution
> > > > https://issues.apache.org/jira/browse/IGNITE-13960
> > > >
> > > > .NET: LINQ provider emits incorrect table alias for queries with JOIN
> > > > and GROUP BY combined
> > > > https://issues.apache.org/jira/browse/IGNITE-13754
> > > >
> > > > Query cancellation freezes on local lazy queries
> > > > https://issues.apache.org/jira/browse/IGNITE-13964
> > > >
> > > > SQL: REPLICATED cache cannot be left-joined to PARTITIONED
> > > > https://issues.apache.org/jira/browse/IGNITE-8732
> > > >
> > > > .NET: logger throws KeyNotFound on creating cache with nullable
> 'sbyte?'
> > > > field
> > > > https://issues.apache.org/jira/browse/IGNITE-12090
> > > >
> > > > Possible deadlock between methods from GridEncryptionManager
> > > > https://issues.apache.org/jira/browse/IGNITE-13906
> > > >
> > > > On Mon, 18 Jan 2021 at 11:05, Maxim Muzafarov 
> wrote:
> > > > >
> > > > > Nikita,
> > > > >
> > > > > Thank you for sharing the progress. I will check all the PRs you
> > > > > reviewed and merge them if need. I will help you with the *[list
> #3]*
> > > > > issues (some of them already complete and merged to the 2.10
> branch).
> > > > >
> > > > > On Fri, 15 Jan 2021 at 22:43, Никита Сафонов <
> > > vlasovpavel2...@gmail.com>
> > > > wrote:
> > > > > >
> > > > > > Hi Maxim et al,
> > > > > >
> > > > > >
> > > > > > I’d like to share my interim status on Ignite 2.10 documentation
> > > work.
> > > > > >
> > > > > >
> > > > > >
> > > > > >- The following PR’s  *[list #1]* are reviewed and, when the
> > > > changes are
> > > > > >accepted, ready to be merged, including 4 important features.
> > > > > >
> > > > > >
> > > > > >
> > > > > >- I’m pretty sure that I’ll collect and put together
> information
> > > for
> > > > > >most of the following tasks *[list #2] *by the end of the next
> > > week,
> > > > > >including 3 important features.
> > > > > >
> > > > > >
> > > > > >
> > > > > >- I’d kindly ask your help with the following items *[list
> #3]*,
> > > > > >including 2 important features.
> > > > > >
> > > > > >
> > > > > > So, for the sake of documentation completeness, I suggest
> finalizing
> > > > our
> > > > > > doc work next week.
> > > > > >
> > > > > > Regards,
> > > > > > Nikita
> > > > > >
> > > > > >
> > > > > > *[list #1]:*
> > > > > >
> > > > > >
> > > > > > * IGNITE-13968 Add snapshot events documentation pages
> > > > > >
> > > > > > https://issues.apache.org/jira/browse/IGNITE-13968
> > > > > >
> > > > > > https://github.com/apache/ignite/pull/8642
> > > > > >
> > > > > >
> > > > > >
> > > > > > * Add documentation for new checkpoint, cluster and cache metrics
> > > > > >
> > > > > > https://issues.apache.org/jira/browse/IGNITE-13982
> > > > > >
> > > > > 

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

[Maxim Muzafarov]

Folks,


This is the list of bugs which I've cherry-picked to the ignite-2.10 branch:


Starvation in mgmt pool caused by MetadataTask execution
https://issues.apache.org/jira/browse/IGNITE-13960

.NET: LINQ provider emits incorrect table alias for queries with JOIN
and GROUP BY combined
https://issues.apache.org/jira/browse/IGNITE-13754

Query cancellation freezes on local lazy queries
https://issues.apache.org/jira/browse/IGNITE-13964

SQL: REPLICATED cache cannot be left-joined to PARTITIONED
https://issues.apache.org/jira/browse/IGNITE-8732

.NET: logger throws KeyNotFound on creating cache with nullable 'sbyte?' field
https://issues.apache.org/jira/browse/IGNITE-12090

Possible deadlock between methods from GridEncryptionManager
https://issues.apache.org/jira/browse/IGNITE-13906

OOM on creating rebalance iterator while rebalancing cache with large values.
https://issues.apache.org/jira/browse/IGNITE-14003

On Mon, 18 Jan 2021 at 17:20, Pavel Tupitsyn  wrote:
>
> Maxim,
>
> No objections for .NET-related cherry-picks.
>
> Thank you!
>
> On Mon, Jan 18, 2021 at 4:52 PM Никита Сафонов 
> wrote:
>
> > Hi Maxim et al,
> >
> > Thank you very much!
> > I do appreciate your help!
> >
> > Regards,
> > Nikita
> >
> > пн, 18 янв. 2021 г. в 16:16, Maxim Muzafarov :
> >
> > > Folks,
> > >
> > > I'd like to cherry-pick these bugs to the ignite-2.10 branch.
> > > Do you have any objections?
> > >
> > >
> > > Starvation in mgmt pool caused by MetadataTask execution
> > > https://issues.apache.org/jira/browse/IGNITE-13960
> > >
> > > .NET: LINQ provider emits incorrect table alias for queries with JOIN
> > > and GROUP BY combined
> > > https://issues.apache.org/jira/browse/IGNITE-13754
> > >
> > > Query cancellation freezes on local lazy queries
> > > https://issues.apache.org/jira/browse/IGNITE-13964
> > >
> > > SQL: REPLICATED cache cannot be left-joined to PARTITIONED
> > > https://issues.apache.org/jira/browse/IGNITE-8732
> > >
> > > .NET: logger throws KeyNotFound on creating cache with nullable 'sbyte?'
> > > field
> > > https://issues.apache.org/jira/browse/IGNITE-12090
> > >
> > > Possible deadlock between methods from GridEncryptionManager
> > > https://issues.apache.org/jira/browse/IGNITE-13906
> > >
> > > On Mon, 18 Jan 2021 at 11:05, Maxim Muzafarov  wrote:
> > > >
> > > > Nikita,
> > > >
> > > > Thank you for sharing the progress. I will check all the PRs you
> > > > reviewed and merge them if need. I will help you with the *[list #3]*
> > > > issues (some of them already complete and merged to the 2.10 branch).
> > > >
> > > > On Fri, 15 Jan 2021 at 22:43, Никита Сафонов <
> > vlasovpavel2...@gmail.com>
> > > wrote:
> > > > >
> > > > > Hi Maxim et al,
> > > > >
> > > > >
> > > > > I’d like to share my interim status on Ignite 2.10 documentation
> > work.
> > > > >
> > > > >
> > > > >
> > > > >- The following PR’s  *[list #1]* are reviewed and, when the
> > > changes are
> > > > >accepted, ready to be merged, including 4 important features.
> > > > >
> > > > >
> > > > >
> > > > >- I’m pretty sure that I’ll collect and put together information
> > for
> > > > >most of the following tasks *[list #2] *by the end of the next
> > week,
> > > > >including 3 important features.
> > > > >
> > > > >
> > > > >
> > > > >- I’d kindly ask your help with the following items *[list #3]*,
> > > > >including 2 important features.
> > > > >
> > > > >
> > > > > So, for the sake of documentation completeness, I suggest finalizing
> > > our
> > > > > doc work next week.
> > > > >
> > > > > Regards,
> > > > > Nikita
> > > > >
> > > > >
> > > > > *[list #1]:*
> > > > >
> > > > >
> > > > > * IGNITE-13968 Add snapshot events documentation pages
> > > > >
> > > > > https://issues.apache.org/jira/browse/IGNITE-13968
> > > > >
> > > > > https://github.com/apache/ignite/pull/8642
> > > > >
> > > > >
> > > > >
> > > > > * Add documentation for new checkpoint, cluster and cache metrics
> > > > >
> > > > > https://issues.apache.org/jira/browse/IGNITE-13982
> > > > >
> > > > >
> > https://github.com/apache/ignite/pull/8652#pullrequestreview-567256761
> > > > >
> > > > >
> > > > >
> > > > > * Update docs and examples for kubernetes module [IMPORTANT FEATURE]
> > > > >
> > > > > https://issues.apache.org/jira/browse/IGNITE-13796?src=confmacro
> > > > >
> > > > > https://github.com/apache/ignite/pull/8532
> > > > >
> > > > >
> > > > >
> > > > > * TDE - Phase 3. Documentation [IMPORTANT FEATURE]
> > > > >
> > > > > https://issues.apache.org/jira/browse/IGNITE-13659?src=confmacro
> > > > >
> > > > > https://github.com/apache/ignite/pull/8446
> > > > >
> > > > >
> > > > >
> > > > > * Add documentation for the cluster performance profiling tool
> > > [IMPORTANT
> > > > > FEATURE]
> > > > >
> > > > > https://issues.apache.org/jira/browse/IGNITE-13854?src=confmacro
> > > > >
> > > > > https://github.com/apache/ignite/pull/8663/files
> > > > >
> > > > >
> > > > >
> > > > > * Document Persistent store defragmentation 

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

[Pavel Tupitsyn]

Maxim,

No objections for .NET-related cherry-picks.

Thank you!

On Mon, Jan 18, 2021 at 4:52 PM Никита Сафонов 
wrote:

> Hi Maxim et al,
>
> Thank you very much!
> I do appreciate your help!
>
> Regards,
> Nikita
>
> пн, 18 янв. 2021 г. в 16:16, Maxim Muzafarov :
>
> > Folks,
> >
> > I'd like to cherry-pick these bugs to the ignite-2.10 branch.
> > Do you have any objections?
> >
> >
> > Starvation in mgmt pool caused by MetadataTask execution
> > https://issues.apache.org/jira/browse/IGNITE-13960
> >
> > .NET: LINQ provider emits incorrect table alias for queries with JOIN
> > and GROUP BY combined
> > https://issues.apache.org/jira/browse/IGNITE-13754
> >
> > Query cancellation freezes on local lazy queries
> > https://issues.apache.org/jira/browse/IGNITE-13964
> >
> > SQL: REPLICATED cache cannot be left-joined to PARTITIONED
> > https://issues.apache.org/jira/browse/IGNITE-8732
> >
> > .NET: logger throws KeyNotFound on creating cache with nullable 'sbyte?'
> > field
> > https://issues.apache.org/jira/browse/IGNITE-12090
> >
> > Possible deadlock between methods from GridEncryptionManager
> > https://issues.apache.org/jira/browse/IGNITE-13906
> >
> > On Mon, 18 Jan 2021 at 11:05, Maxim Muzafarov  wrote:
> > >
> > > Nikita,
> > >
> > > Thank you for sharing the progress. I will check all the PRs you
> > > reviewed and merge them if need. I will help you with the *[list #3]*
> > > issues (some of them already complete and merged to the 2.10 branch).
> > >
> > > On Fri, 15 Jan 2021 at 22:43, Никита Сафонов <
> vlasovpavel2...@gmail.com>
> > wrote:
> > > >
> > > > Hi Maxim et al,
> > > >
> > > >
> > > > I’d like to share my interim status on Ignite 2.10 documentation
> work.
> > > >
> > > >
> > > >
> > > >- The following PR’s  *[list #1]* are reviewed and, when the
> > changes are
> > > >accepted, ready to be merged, including 4 important features.
> > > >
> > > >
> > > >
> > > >- I’m pretty sure that I’ll collect and put together information
> for
> > > >most of the following tasks *[list #2] *by the end of the next
> week,
> > > >including 3 important features.
> > > >
> > > >
> > > >
> > > >- I’d kindly ask your help with the following items *[list #3]*,
> > > >including 2 important features.
> > > >
> > > >
> > > > So, for the sake of documentation completeness, I suggest finalizing
> > our
> > > > doc work next week.
> > > >
> > > > Regards,
> > > > Nikita
> > > >
> > > >
> > > > *[list #1]:*
> > > >
> > > >
> > > > * IGNITE-13968 Add snapshot events documentation pages
> > > >
> > > > https://issues.apache.org/jira/browse/IGNITE-13968
> > > >
> > > > https://github.com/apache/ignite/pull/8642
> > > >
> > > >
> > > >
> > > > * Add documentation for new checkpoint, cluster and cache metrics
> > > >
> > > > https://issues.apache.org/jira/browse/IGNITE-13982
> > > >
> > > >
> https://github.com/apache/ignite/pull/8652#pullrequestreview-567256761
> > > >
> > > >
> > > >
> > > > * Update docs and examples for kubernetes module [IMPORTANT FEATURE]
> > > >
> > > > https://issues.apache.org/jira/browse/IGNITE-13796?src=confmacro
> > > >
> > > > https://github.com/apache/ignite/pull/8532
> > > >
> > > >
> > > >
> > > > * TDE - Phase 3. Documentation [IMPORTANT FEATURE]
> > > >
> > > > https://issues.apache.org/jira/browse/IGNITE-13659?src=confmacro
> > > >
> > > > https://github.com/apache/ignite/pull/8446
> > > >
> > > >
> > > >
> > > > * Add documentation for the cluster performance profiling tool
> > [IMPORTANT
> > > > FEATURE]
> > > >
> > > > https://issues.apache.org/jira/browse/IGNITE-13854?src=confmacro
> > > >
> > > > https://github.com/apache/ignite/pull/8663/files
> > > >
> > > >
> > > >
> > > > * Document Persistent store defragmentation [IMPORTANT FEATURE]
> > > >
> > > > https://issues.apache.org/jira/browse/IGNITE-13674?src=confmacro
> > > >
> > > > https://github.com/apache/ignite/pull/8465
> > > >
> > > >
> > > >
> > > > *[list #2]:*
> > > >
> > > >
> > > >
> > > > * Documentation of cache warm-up strategy [IMPORTANT FEATURE]
> > > >
> > > > https://issues.apache.org/jira/browse/IGNITE-13385?src=confmacro
> > > >
> > > >
> > > > * Documentation update on JMX default configuration removal
> [IMPORTANT
> > > > FEATURE]
> > > >
> > > > https://issues.apache.org/jira/browse/IGNITE-13606?src=confmacro
> > > >
> > > > * Document control.sh indexes manipulation commands [IMPORTANT
> FEATURE]
> > > >
> > > > https://issues.apache.org/jira/browse/IGNITE-13285?src=confmacro
> > > >
> > > >
> > > >
> > > > * Add command to control.(sh|bin) to get an arbitrary SystemView
> > > >
> > > > https://issues.apache.org/jira/browse/IGNITE-13426
> > > >
> > > >
> > > >
> > > > * Add a metric for processed keys when rebuilding indexes
> > > >
> > > > https://issues.apache.org/jira/browse/IGNITE-13327
> > > >
> > > >
> > > >
> > > > * Add tracing of SQL queries.
> > > >
> > > > https://issues.apache.org/jira/browse/IGNITE-13310
> > > >
> > > >
> > > > * CPP: Implement Cluster API
> > > 

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

[Никита Сафонов]

Hi Maxim et al,

Thank you very much!
I do appreciate your help!

Regards,
Nikita

пн, 18 янв. 2021 г. в 16:16, Maxim Muzafarov :

> Folks,
>
> I'd like to cherry-pick these bugs to the ignite-2.10 branch.
> Do you have any objections?
>
>
> Starvation in mgmt pool caused by MetadataTask execution
> https://issues.apache.org/jira/browse/IGNITE-13960
>
> .NET: LINQ provider emits incorrect table alias for queries with JOIN
> and GROUP BY combined
> https://issues.apache.org/jira/browse/IGNITE-13754
>
> Query cancellation freezes on local lazy queries
> https://issues.apache.org/jira/browse/IGNITE-13964
>
> SQL: REPLICATED cache cannot be left-joined to PARTITIONED
> https://issues.apache.org/jira/browse/IGNITE-8732
>
> .NET: logger throws KeyNotFound on creating cache with nullable 'sbyte?'
> field
> https://issues.apache.org/jira/browse/IGNITE-12090
>
> Possible deadlock between methods from GridEncryptionManager
> https://issues.apache.org/jira/browse/IGNITE-13906
>
> On Mon, 18 Jan 2021 at 11:05, Maxim Muzafarov  wrote:
> >
> > Nikita,
> >
> > Thank you for sharing the progress. I will check all the PRs you
> > reviewed and merge them if need. I will help you with the *[list #3]*
> > issues (some of them already complete and merged to the 2.10 branch).
> >
> > On Fri, 15 Jan 2021 at 22:43, Никита Сафонов 
> wrote:
> > >
> > > Hi Maxim et al,
> > >
> > >
> > > I’d like to share my interim status on Ignite 2.10 documentation work.
> > >
> > >
> > >
> > >- The following PR’s  *[list #1]* are reviewed and, when the
> changes are
> > >accepted, ready to be merged, including 4 important features.
> > >
> > >
> > >
> > >- I’m pretty sure that I’ll collect and put together information for
> > >most of the following tasks *[list #2] *by the end of the next week,
> > >including 3 important features.
> > >
> > >
> > >
> > >- I’d kindly ask your help with the following items *[list #3]*,
> > >including 2 important features.
> > >
> > >
> > > So, for the sake of documentation completeness, I suggest finalizing
> our
> > > doc work next week.
> > >
> > > Regards,
> > > Nikita
> > >
> > >
> > > *[list #1]:*
> > >
> > >
> > > * IGNITE-13968 Add snapshot events documentation pages
> > >
> > > https://issues.apache.org/jira/browse/IGNITE-13968
> > >
> > > https://github.com/apache/ignite/pull/8642
> > >
> > >
> > >
> > > * Add documentation for new checkpoint, cluster and cache metrics
> > >
> > > https://issues.apache.org/jira/browse/IGNITE-13982
> > >
> > > https://github.com/apache/ignite/pull/8652#pullrequestreview-567256761
> > >
> > >
> > >
> > > * Update docs and examples for kubernetes module [IMPORTANT FEATURE]
> > >
> > > https://issues.apache.org/jira/browse/IGNITE-13796?src=confmacro
> > >
> > > https://github.com/apache/ignite/pull/8532
> > >
> > >
> > >
> > > * TDE - Phase 3. Documentation [IMPORTANT FEATURE]
> > >
> > > https://issues.apache.org/jira/browse/IGNITE-13659?src=confmacro
> > >
> > > https://github.com/apache/ignite/pull/8446
> > >
> > >
> > >
> > > * Add documentation for the cluster performance profiling tool
> [IMPORTANT
> > > FEATURE]
> > >
> > > https://issues.apache.org/jira/browse/IGNITE-13854?src=confmacro
> > >
> > > https://github.com/apache/ignite/pull/8663/files
> > >
> > >
> > >
> > > * Document Persistent store defragmentation [IMPORTANT FEATURE]
> > >
> > > https://issues.apache.org/jira/browse/IGNITE-13674?src=confmacro
> > >
> > > https://github.com/apache/ignite/pull/8465
> > >
> > >
> > >
> > > *[list #2]:*
> > >
> > >
> > >
> > > * Documentation of cache warm-up strategy [IMPORTANT FEATURE]
> > >
> > > https://issues.apache.org/jira/browse/IGNITE-13385?src=confmacro
> > >
> > >
> > > * Documentation update on JMX default configuration removal [IMPORTANT
> > > FEATURE]
> > >
> > > https://issues.apache.org/jira/browse/IGNITE-13606?src=confmacro
> > >
> > > * Document control.sh indexes manipulation commands [IMPORTANT FEATURE]
> > >
> > > https://issues.apache.org/jira/browse/IGNITE-13285?src=confmacro
> > >
> > >
> > >
> > > * Add command to control.(sh|bin) to get an arbitrary SystemView
> > >
> > > https://issues.apache.org/jira/browse/IGNITE-13426
> > >
> > >
> > >
> > > * Add a metric for processed keys when rebuilding indexes
> > >
> > > https://issues.apache.org/jira/browse/IGNITE-13327
> > >
> > >
> > >
> > > * Add tracing of SQL queries.
> > >
> > > https://issues.apache.org/jira/browse/IGNITE-13310
> > >
> > >
> > > * CPP: Implement Cluster API
> > >
> > > https://issues.apache.org/jira/browse/IGNITE-11731
> > >
> > >
> > >
> > > * C++: Thin client transactions
> > >
> > > https://issues.apache.org/jira/browse/IGNITE-13308
> > >
> > >
> > >
> > > * .NET: Thin Client: Service invocation
> > >
> > > https://issues.apache.org/jira/browse/IGNITE-12754
> > >
> > >
> > >
> > > * Thin client Java API - async API
> > >
> > > https://issues.apache.org/jira/browse/IGNITE-7623
> > >
> > >
> > >
> > >
> > >
> > > *[list #3]:*
> > >
> > > * Document 

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

[Maxim Muzafarov]

Folks,

I'd like to cherry-pick these bugs to the ignite-2.10 branch.
Do you have any objections?


Starvation in mgmt pool caused by MetadataTask execution
https://issues.apache.org/jira/browse/IGNITE-13960

.NET: LINQ provider emits incorrect table alias for queries with JOIN
and GROUP BY combined
https://issues.apache.org/jira/browse/IGNITE-13754

Query cancellation freezes on local lazy queries
https://issues.apache.org/jira/browse/IGNITE-13964

SQL: REPLICATED cache cannot be left-joined to PARTITIONED
https://issues.apache.org/jira/browse/IGNITE-8732

.NET: logger throws KeyNotFound on creating cache with nullable 'sbyte?' field
https://issues.apache.org/jira/browse/IGNITE-12090

Possible deadlock between methods from GridEncryptionManager
https://issues.apache.org/jira/browse/IGNITE-13906

On Mon, 18 Jan 2021 at 11:05, Maxim Muzafarov  wrote:
>
> Nikita,
>
> Thank you for sharing the progress. I will check all the PRs you
> reviewed and merge them if need. I will help you with the *[list #3]*
> issues (some of them already complete and merged to the 2.10 branch).
>
> On Fri, 15 Jan 2021 at 22:43, Никита Сафонов  
> wrote:
> >
> > Hi Maxim et al,
> >
> >
> > I’d like to share my interim status on Ignite 2.10 documentation work.
> >
> >
> >
> >- The following PR’s  *[list #1]* are reviewed and, when the changes are
> >accepted, ready to be merged, including 4 important features.
> >
> >
> >
> >- I’m pretty sure that I’ll collect and put together information for
> >most of the following tasks *[list #2] *by the end of the next week,
> >including 3 important features.
> >
> >
> >
> >- I’d kindly ask your help with the following items *[list #3]*,
> >including 2 important features.
> >
> >
> > So, for the sake of documentation completeness, I suggest finalizing our
> > doc work next week.
> >
> > Regards,
> > Nikita
> >
> >
> > *[list #1]:*
> >
> >
> > * IGNITE-13968 Add snapshot events documentation pages
> >
> > https://issues.apache.org/jira/browse/IGNITE-13968
> >
> > https://github.com/apache/ignite/pull/8642
> >
> >
> >
> > * Add documentation for new checkpoint, cluster and cache metrics
> >
> > https://issues.apache.org/jira/browse/IGNITE-13982
> >
> > https://github.com/apache/ignite/pull/8652#pullrequestreview-567256761
> >
> >
> >
> > * Update docs and examples for kubernetes module [IMPORTANT FEATURE]
> >
> > https://issues.apache.org/jira/browse/IGNITE-13796?src=confmacro
> >
> > https://github.com/apache/ignite/pull/8532
> >
> >
> >
> > * TDE - Phase 3. Documentation [IMPORTANT FEATURE]
> >
> > https://issues.apache.org/jira/browse/IGNITE-13659?src=confmacro
> >
> > https://github.com/apache/ignite/pull/8446
> >
> >
> >
> > * Add documentation for the cluster performance profiling tool [IMPORTANT
> > FEATURE]
> >
> > https://issues.apache.org/jira/browse/IGNITE-13854?src=confmacro
> >
> > https://github.com/apache/ignite/pull/8663/files
> >
> >
> >
> > * Document Persistent store defragmentation [IMPORTANT FEATURE]
> >
> > https://issues.apache.org/jira/browse/IGNITE-13674?src=confmacro
> >
> > https://github.com/apache/ignite/pull/8465
> >
> >
> >
> > *[list #2]:*
> >
> >
> >
> > * Documentation of cache warm-up strategy [IMPORTANT FEATURE]
> >
> > https://issues.apache.org/jira/browse/IGNITE-13385?src=confmacro
> >
> >
> > * Documentation update on JMX default configuration removal [IMPORTANT
> > FEATURE]
> >
> > https://issues.apache.org/jira/browse/IGNITE-13606?src=confmacro
> >
> > * Document control.sh indexes manipulation commands [IMPORTANT FEATURE]
> >
> > https://issues.apache.org/jira/browse/IGNITE-13285?src=confmacro
> >
> >
> >
> > * Add command to control.(sh|bin) to get an arbitrary SystemView
> >
> > https://issues.apache.org/jira/browse/IGNITE-13426
> >
> >
> >
> > * Add a metric for processed keys when rebuilding indexes
> >
> > https://issues.apache.org/jira/browse/IGNITE-13327
> >
> >
> >
> > * Add tracing of SQL queries.
> >
> > https://issues.apache.org/jira/browse/IGNITE-13310
> >
> >
> > * CPP: Implement Cluster API
> >
> > https://issues.apache.org/jira/browse/IGNITE-11731
> >
> >
> >
> > * C++: Thin client transactions
> >
> > https://issues.apache.org/jira/browse/IGNITE-13308
> >
> >
> >
> > * .NET: Thin Client: Service invocation
> >
> > https://issues.apache.org/jira/browse/IGNITE-12754
> >
> >
> >
> > * Thin client Java API - async API
> >
> > https://issues.apache.org/jira/browse/IGNITE-7623
> >
> >
> >
> >
> >
> > *[list #3]:*
> >
> > * Document --tx control script commands [IMPORTANT FEATURE]
> >
> > https://issues.apache.org/jira/browse/IGNITE-11747?src=confmacro
> >
> > * Document a new command control.sh --cache check_index_inline_sizes
> > [IMPORTANT FEATURE]
> >
> > https://issues.apache.org/jira/browse/IGNITE-12955?src=confmacro
> >
> >
> >
> > * Add command to control.(sh|bin) to get an arbitrary Metric
> >
> > https://issues.apache.org/jira/browse/IGNITE-13488
> >
> >
> >
> > * Add events for snapshot operation state
> >

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

[Maxim Muzafarov]

Nikita,

Thank you for sharing the progress. I will check all the PRs you
reviewed and merge them if need. I will help you with the *[list #3]*
issues (some of them already complete and merged to the 2.10 branch).

On Fri, 15 Jan 2021 at 22:43, Никита Сафонов  wrote:
>
> Hi Maxim et al,
>
>
> I’d like to share my interim status on Ignite 2.10 documentation work.
>
>
>
>- The following PR’s  *[list #1]* are reviewed and, when the changes are
>accepted, ready to be merged, including 4 important features.
>
>
>
>- I’m pretty sure that I’ll collect and put together information for
>most of the following tasks *[list #2] *by the end of the next week,
>including 3 important features.
>
>
>
>- I’d kindly ask your help with the following items *[list #3]*,
>including 2 important features.
>
>
> So, for the sake of documentation completeness, I suggest finalizing our
> doc work next week.
>
> Regards,
> Nikita
>
>
> *[list #1]:*
>
>
> * IGNITE-13968 Add snapshot events documentation pages
>
> https://issues.apache.org/jira/browse/IGNITE-13968
>
> https://github.com/apache/ignite/pull/8642
>
>
>
> * Add documentation for new checkpoint, cluster and cache metrics
>
> https://issues.apache.org/jira/browse/IGNITE-13982
>
> https://github.com/apache/ignite/pull/8652#pullrequestreview-567256761
>
>
>
> * Update docs and examples for kubernetes module [IMPORTANT FEATURE]
>
> https://issues.apache.org/jira/browse/IGNITE-13796?src=confmacro
>
> https://github.com/apache/ignite/pull/8532
>
>
>
> * TDE - Phase 3. Documentation [IMPORTANT FEATURE]
>
> https://issues.apache.org/jira/browse/IGNITE-13659?src=confmacro
>
> https://github.com/apache/ignite/pull/8446
>
>
>
> * Add documentation for the cluster performance profiling tool [IMPORTANT
> FEATURE]
>
> https://issues.apache.org/jira/browse/IGNITE-13854?src=confmacro
>
> https://github.com/apache/ignite/pull/8663/files
>
>
>
> * Document Persistent store defragmentation [IMPORTANT FEATURE]
>
> https://issues.apache.org/jira/browse/IGNITE-13674?src=confmacro
>
> https://github.com/apache/ignite/pull/8465
>
>
>
> *[list #2]:*
>
>
>
> * Documentation of cache warm-up strategy [IMPORTANT FEATURE]
>
> https://issues.apache.org/jira/browse/IGNITE-13385?src=confmacro
>
>
> * Documentation update on JMX default configuration removal [IMPORTANT
> FEATURE]
>
> https://issues.apache.org/jira/browse/IGNITE-13606?src=confmacro
>
> * Document control.sh indexes manipulation commands [IMPORTANT FEATURE]
>
> https://issues.apache.org/jira/browse/IGNITE-13285?src=confmacro
>
>
>
> * Add command to control.(sh|bin) to get an arbitrary SystemView
>
> https://issues.apache.org/jira/browse/IGNITE-13426
>
>
>
> * Add a metric for processed keys when rebuilding indexes
>
> https://issues.apache.org/jira/browse/IGNITE-13327
>
>
>
> * Add tracing of SQL queries.
>
> https://issues.apache.org/jira/browse/IGNITE-13310
>
>
> * CPP: Implement Cluster API
>
> https://issues.apache.org/jira/browse/IGNITE-11731
>
>
>
> * C++: Thin client transactions
>
> https://issues.apache.org/jira/browse/IGNITE-13308
>
>
>
> * .NET: Thin Client: Service invocation
>
> https://issues.apache.org/jira/browse/IGNITE-12754
>
>
>
> * Thin client Java API - async API
>
> https://issues.apache.org/jira/browse/IGNITE-7623
>
>
>
>
>
> *[list #3]:*
>
> * Document --tx control script commands [IMPORTANT FEATURE]
>
> https://issues.apache.org/jira/browse/IGNITE-11747?src=confmacro
>
> * Document a new command control.sh --cache check_index_inline_sizes
> [IMPORTANT FEATURE]
>
> https://issues.apache.org/jira/browse/IGNITE-12955?src=confmacro
>
>
>
> * Add command to control.(sh|bin) to get an arbitrary Metric
>
> https://issues.apache.org/jira/browse/IGNITE-13488
>
>
>
> * Add events for snapshot operation state
>
> https://issues.apache.org/jira/browse/IGNITE-13467
>
>
>
> * Support cluster snapshot security permissions
>
> https://issues.apache.org/jira/browse/IGNITE-13535
>
>
>
> * Add event for node validation failure.
>
> https://issues.apache.org/jira/browse/IGNITE-12380
>
>
>
> * Output IgniteSystemProperties via ignite.sh
>
> https://issues.apache.org/jira/browse/IGNITE-13380
>
> вт, 12 янв. 2021 г. в 17:56, Никита Сафонов :
>
> > Hi Maxim,
> >
> > Sure, I'll check these ones too.
> >
> > Thanks,
> > Nikita
> >
> > вт, 12 янв. 2021 г. в 14:14, Maxim Muzafarov :
> >
> >> Nikita,
> >>
> >> I've also prepared the docs [1][2].
> >> Can you please check this small patch?
> >>
> >>
> >> [1] https://issues.apache.org/jira/browse/IGNITE-13968
> >> [2] https://github.com/apache/ignite/pull/8642
> >>
> >> On Mon, 11 Jan 2021 at 20:38, Никита Сафонов 
> >> wrote:
> >> >
> >> > Hi everyone,
> >> >
> >> > I'm finally back and ready to continue the work, sorry for this delay.
> >> > Maxim, thanks once again for preparing a list of important documentation
> >> > issues.
> >> >
> >> > Regards,
> >> > Nikita
> >> >
> >> > чт, 7 янв. 2021 г. в 13:47, Nikolay Izhikov :
> >> >
> >> > > Hello.
> >> > >
> >> > > I 

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

[Никита Сафонов]

Hi Maxim et al,


I’d like to share my interim status on Ignite 2.10 documentation work.



   - The following PR’s  *[list #1]* are reviewed and, when the changes are
   accepted, ready to be merged, including 4 important features.



   - I’m pretty sure that I’ll collect and put together information for
   most of the following tasks *[list #2] *by the end of the next week,
   including 3 important features.



   - I’d kindly ask your help with the following items *[list #3]*,
   including 2 important features.


So, for the sake of documentation completeness, I suggest finalizing our
doc work next week.

Regards,
Nikita


*[list #1]:*


* IGNITE-13968 Add snapshot events documentation pages

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

https://github.com/apache/ignite/pull/8642



* Add documentation for new checkpoint, cluster and cache metrics

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

https://github.com/apache/ignite/pull/8652#pullrequestreview-567256761



* Update docs and examples for kubernetes module [IMPORTANT FEATURE]

https://issues.apache.org/jira/browse/IGNITE-13796?src=confmacro

https://github.com/apache/ignite/pull/8532



* TDE - Phase 3. Documentation [IMPORTANT FEATURE]

https://issues.apache.org/jira/browse/IGNITE-13659?src=confmacro

https://github.com/apache/ignite/pull/8446



* Add documentation for the cluster performance profiling tool [IMPORTANT
FEATURE]

https://issues.apache.org/jira/browse/IGNITE-13854?src=confmacro

https://github.com/apache/ignite/pull/8663/files



* Document Persistent store defragmentation [IMPORTANT FEATURE]

https://issues.apache.org/jira/browse/IGNITE-13674?src=confmacro

https://github.com/apache/ignite/pull/8465



*[list #2]:*



* Documentation of cache warm-up strategy [IMPORTANT FEATURE]

https://issues.apache.org/jira/browse/IGNITE-13385?src=confmacro


* Documentation update on JMX default configuration removal [IMPORTANT
FEATURE]

https://issues.apache.org/jira/browse/IGNITE-13606?src=confmacro

* Document control.sh indexes manipulation commands [IMPORTANT FEATURE]

https://issues.apache.org/jira/browse/IGNITE-13285?src=confmacro



* Add command to control.(sh|bin) to get an arbitrary SystemView

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



* Add a metric for processed keys when rebuilding indexes

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



* Add tracing of SQL queries.

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


* CPP: Implement Cluster API

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



* C++: Thin client transactions

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



* .NET: Thin Client: Service invocation

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



* Thin client Java API - async API

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





*[list #3]:*

* Document --tx control script commands [IMPORTANT FEATURE]

https://issues.apache.org/jira/browse/IGNITE-11747?src=confmacro

* Document a new command control.sh --cache check_index_inline_sizes
[IMPORTANT FEATURE]

https://issues.apache.org/jira/browse/IGNITE-12955?src=confmacro



* Add command to control.(sh|bin) to get an arbitrary Metric

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



* Add events for snapshot operation state

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



* Support cluster snapshot security permissions

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



* Add event for node validation failure.

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



* Output IgniteSystemProperties via ignite.sh

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

вт, 12 янв. 2021 г. в 17:56, Никита Сафонов :

> Hi Maxim,
>
> Sure, I'll check these ones too.
>
> Thanks,
> Nikita
>
> вт, 12 янв. 2021 г. в 14:14, Maxim Muzafarov :
>
>> Nikita,
>>
>> I've also prepared the docs [1][2].
>> Can you please check this small patch?
>>
>>
>> [1] https://issues.apache.org/jira/browse/IGNITE-13968
>> [2] https://github.com/apache/ignite/pull/8642
>>
>> On Mon, 11 Jan 2021 at 20:38, Никита Сафонов 
>> wrote:
>> >
>> > Hi everyone,
>> >
>> > I'm finally back and ready to continue the work, sorry for this delay.
>> > Maxim, thanks once again for preparing a list of important documentation
>> > issues.
>> >
>> > Regards,
>> > Nikita
>> >
>> > чт, 7 янв. 2021 г. в 13:47, Nikolay Izhikov :
>> >
>> > > Hello.
>> > >
>> > > I prepared docs [1] for the following tickets
>> > >
>> > > Denis, can you, please, take a look?
>> > >
>> > > > https://issues.apache.org/jira/browse/IGNITE-13488 - Add command to
>> > > control.(sh|bin) to get an arbitrary Metric
>> > > > https://issues.apache.org/jira/browse/IGNITE-13426 - Add command to
>> > > control.(sh|bin) to get an arbitrary SystemView
>> > > > https://issues.apache.org/jira/browse/IGNITE-13380 - Output
>> > > IgniteSystemProperties via ignite.sh
>> > >
>> > > [1] https://github.com/apache/ignite/pull/8630
>> > >
>> > > > 29 дек. 2020 г., в 21:42, Denis Magda 
>> 

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

[Никита Сафонов]

Hi Maxim,

Sure, I'll check these ones too.

Thanks,
Nikita

вт, 12 янв. 2021 г. в 14:14, Maxim Muzafarov :

> Nikita,
>
> I've also prepared the docs [1][2].
> Can you please check this small patch?
>
>
> [1] https://issues.apache.org/jira/browse/IGNITE-13968
> [2] https://github.com/apache/ignite/pull/8642
>
> On Mon, 11 Jan 2021 at 20:38, Никита Сафонов 
> wrote:
> >
> > Hi everyone,
> >
> > I'm finally back and ready to continue the work, sorry for this delay.
> > Maxim, thanks once again for preparing a list of important documentation
> > issues.
> >
> > Regards,
> > Nikita
> >
> > чт, 7 янв. 2021 г. в 13:47, Nikolay Izhikov :
> >
> > > Hello.
> > >
> > > I prepared docs [1] for the following tickets
> > >
> > > Denis, can you, please, take a look?
> > >
> > > > https://issues.apache.org/jira/browse/IGNITE-13488 - Add command to
> > > control.(sh|bin) to get an arbitrary Metric
> > > > https://issues.apache.org/jira/browse/IGNITE-13426 - Add command to
> > > control.(sh|bin) to get an arbitrary SystemView
> > > > https://issues.apache.org/jira/browse/IGNITE-13380 - Output
> > > IgniteSystemProperties via ignite.sh
> > >
> > > [1] https://github.com/apache/ignite/pull/8630
> > >
> > > > 29 дек. 2020 г., в 21:42, Denis Magda 
> написал(а):
> > > >
> > > > Thanks, Maksim,
> > > >
> > > > Considering that most of the contributors will be on holidays
> through Jan
> > > > 10th, it's highly unlikely that all documentation tickets will be
> ready
> > > by
> > > > Jan 18th (the vote date).
> > > >
> > > > Anyway, Nikita confirmed that he'll be actively working on the
> tickets
> > > > starting Jan 11th. As for me, unfortunately, I have no time for
> > > > contributions in January.
> > > >
> > > > Special thanks for preparing a list of resolved but undocumented
> > > features.
> > > > Most of those just need to be donated from the GridGain documentation
> > > page.
> > > > I'll take care of those.
> > > >
> > > > -
> > > > Denis
> > > >
> > > >
> > > > On Tue, Dec 29, 2020 at 12:43 AM Maxim Muzafarov 
> > > wrote:
> > > >
> > > >> Folks,
> > > >>
> > > >> 1.
> > > >> I've prepared the list of unhandled important documentation issues
> for
> > > >> the 2.10 release, please check the wiki page link [1]. Note, that
> some
> > > >> of the important (from my point of view) documentation issues even
> not
> > > >> created.
> > > >>
> > > >> 2.
> > > >> Here is the list of resolved issues which seems to be documented,
> but
> > > >> an appropriate documentation task doesn't exist. Should we create
> > > >> appropriate documentation issues for them? Check the list [3].
> > > >>
> > > >> 3.
> > > >> Some of the documentation pages must be completed prior to 2.10
> > > >> release or removed, right? Check the [2] page for example.
> > > >>
> > > >>
> > > >> Denis, Nikita
> > > >>
> > > >>> So we should probably allocate more time for this work.
> > > >> Let's start the work, track the progress and looks at how it goes.
> > > >> I'll try to ask some folks for the help with documentation and also
> > > >> plan to help with the issues by myself. We can shift the dates if
> it's
> > > >> necessary, but currently, I see no reasons.
> > > >>
> > > >>
> > > >> [1]
> > > >>
> > >
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.10#ApacheIgnite2.10-Documentationtasksforimportantfeatures
> > > >> [2] https://ignite.apache.org/docs/latest/cpp-specific/
> > > >> [3] The list of issues without documentation tasks :
> > > >>
> > > >> https://issues.apache.org/jira/browse/IGNITE-13488
> > > >> Add command to control.(sh|bin) to get an arbitrary Metric
> > > >>
> > > >> https://issues.apache.org/jira/browse/IGNITE-13467
> > > >> Add events for snapshot operation state
> > > >>
> > > >> https://issues.apache.org/jira/browse/IGNITE-13535
> > > >> Support cluster snapshot security permissions
> > > >>
> > > >> https://issues.apache.org/jira/browse/IGNITE-13426
> > > >> Add command to control.(sh|bin) to get an arbitrary SystemView
> > > >>
> > > >> https://issues.apache.org/jira/browse/IGNITE-13327
> > > >> Add a metric for processed keys when rebuilding indexes.
> > > >>
> > > >> https://issues.apache.org/jira/browse/IGNITE-13310
> > > >> Add tracing of SQL queries.
> > > >>
> > > >> https://issues.apache.org/jira/browse/IGNITE-12380
> > > >> Add event for node validation failure.
> > > >>
> > > >> https://issues.apache.org/jira/browse/IGNITE-7623
> > > >> Thin client Java API - async API
> > > >>
> > > >> https://issues.apache.org/jira/browse/IGNITE-13380
> > > >> Output IgniteSystemProperties via ignite.sh
> > > >>
> > > >> https://issues.apache.org/jira/browse/IGNITE-11731
> > > >> CPP: Implement Cluster API
> > > >>
> > > >> https://issues.apache.org/jira/browse/IGNITE-13308
> > > >> C++: Thin client transactions
> > > >>
> > > >> https://issues.apache.org/jira/browse/IGNITE-12754
> > > >> .NET: Thin Client: Service invocation
> > > >>
> > > >> On Fri, 25 Dec 2020 at 22:43, Никита Сафонов <
> 

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

[Maxim Muzafarov]

Nikita,

I've also prepared the docs [1][2].
Can you please check this small patch?


[1] https://issues.apache.org/jira/browse/IGNITE-13968
[2] https://github.com/apache/ignite/pull/8642

On Mon, 11 Jan 2021 at 20:38, Никита Сафонов  wrote:
>
> Hi everyone,
>
> I'm finally back and ready to continue the work, sorry for this delay.
> Maxim, thanks once again for preparing a list of important documentation
> issues.
>
> Regards,
> Nikita
>
> чт, 7 янв. 2021 г. в 13:47, Nikolay Izhikov :
>
> > Hello.
> >
> > I prepared docs [1] for the following tickets
> >
> > Denis, can you, please, take a look?
> >
> > > https://issues.apache.org/jira/browse/IGNITE-13488 - Add command to
> > control.(sh|bin) to get an arbitrary Metric
> > > https://issues.apache.org/jira/browse/IGNITE-13426 - Add command to
> > control.(sh|bin) to get an arbitrary SystemView
> > > https://issues.apache.org/jira/browse/IGNITE-13380 - Output
> > IgniteSystemProperties via ignite.sh
> >
> > [1] https://github.com/apache/ignite/pull/8630
> >
> > > 29 дек. 2020 г., в 21:42, Denis Magda  написал(а):
> > >
> > > Thanks, Maksim,
> > >
> > > Considering that most of the contributors will be on holidays through Jan
> > > 10th, it's highly unlikely that all documentation tickets will be ready
> > by
> > > Jan 18th (the vote date).
> > >
> > > Anyway, Nikita confirmed that he'll be actively working on the tickets
> > > starting Jan 11th. As for me, unfortunately, I have no time for
> > > contributions in January.
> > >
> > > Special thanks for preparing a list of resolved but undocumented
> > features.
> > > Most of those just need to be donated from the GridGain documentation
> > page.
> > > I'll take care of those.
> > >
> > > -
> > > Denis
> > >
> > >
> > > On Tue, Dec 29, 2020 at 12:43 AM Maxim Muzafarov 
> > wrote:
> > >
> > >> Folks,
> > >>
> > >> 1.
> > >> I've prepared the list of unhandled important documentation issues for
> > >> the 2.10 release, please check the wiki page link [1]. Note, that some
> > >> of the important (from my point of view) documentation issues even not
> > >> created.
> > >>
> > >> 2.
> > >> Here is the list of resolved issues which seems to be documented, but
> > >> an appropriate documentation task doesn't exist. Should we create
> > >> appropriate documentation issues for them? Check the list [3].
> > >>
> > >> 3.
> > >> Some of the documentation pages must be completed prior to 2.10
> > >> release or removed, right? Check the [2] page for example.
> > >>
> > >>
> > >> Denis, Nikita
> > >>
> > >>> So we should probably allocate more time for this work.
> > >> Let's start the work, track the progress and looks at how it goes.
> > >> I'll try to ask some folks for the help with documentation and also
> > >> plan to help with the issues by myself. We can shift the dates if it's
> > >> necessary, but currently, I see no reasons.
> > >>
> > >>
> > >> [1]
> > >>
> > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.10#ApacheIgnite2.10-Documentationtasksforimportantfeatures
> > >> [2] https://ignite.apache.org/docs/latest/cpp-specific/
> > >> [3] The list of issues without documentation tasks :
> > >>
> > >> https://issues.apache.org/jira/browse/IGNITE-13488
> > >> Add command to control.(sh|bin) to get an arbitrary Metric
> > >>
> > >> https://issues.apache.org/jira/browse/IGNITE-13467
> > >> Add events for snapshot operation state
> > >>
> > >> https://issues.apache.org/jira/browse/IGNITE-13535
> > >> Support cluster snapshot security permissions
> > >>
> > >> https://issues.apache.org/jira/browse/IGNITE-13426
> > >> Add command to control.(sh|bin) to get an arbitrary SystemView
> > >>
> > >> https://issues.apache.org/jira/browse/IGNITE-13327
> > >> Add a metric for processed keys when rebuilding indexes.
> > >>
> > >> https://issues.apache.org/jira/browse/IGNITE-13310
> > >> Add tracing of SQL queries.
> > >>
> > >> https://issues.apache.org/jira/browse/IGNITE-12380
> > >> Add event for node validation failure.
> > >>
> > >> https://issues.apache.org/jira/browse/IGNITE-7623
> > >> Thin client Java API - async API
> > >>
> > >> https://issues.apache.org/jira/browse/IGNITE-13380
> > >> Output IgniteSystemProperties via ignite.sh
> > >>
> > >> https://issues.apache.org/jira/browse/IGNITE-11731
> > >> CPP: Implement Cluster API
> > >>
> > >> https://issues.apache.org/jira/browse/IGNITE-13308
> > >> C++: Thin client transactions
> > >>
> > >> https://issues.apache.org/jira/browse/IGNITE-12754
> > >> .NET: Thin Client: Service invocation
> > >>
> > >> On Fri, 25 Dec 2020 at 22:43, Никита Сафонов  > >
> > >> wrote:
> > >>>
> > >>> Hi Denis, Maxim,
> > >>>
> > >>> I'd like to clarify that I'm pretty sure to complete the tasks below
> > >> before
> > >>> the voting date:
> > >>>
> > >>> https://issues.apache.org/jira/browse/IGNITE-13659
> > >>> https://issues.apache.org/jira/browse/IGNITE-13796
> > >>>
> > >>> I'll start to work on them right after the long Russian NY holidays.
> > >>> But I'm not quite sure 

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

[Никита Сафонов]

Hi everyone,

I'm finally back and ready to continue the work, sorry for this delay.
Maxim, thanks once again for preparing a list of important documentation
issues.

Regards,
Nikita

чт, 7 янв. 2021 г. в 13:47, Nikolay Izhikov :

> Hello.
>
> I prepared docs [1] for the following tickets
>
> Denis, can you, please, take a look?
>
> > https://issues.apache.org/jira/browse/IGNITE-13488 - Add command to
> control.(sh|bin) to get an arbitrary Metric
> > https://issues.apache.org/jira/browse/IGNITE-13426 - Add command to
> control.(sh|bin) to get an arbitrary SystemView
> > https://issues.apache.org/jira/browse/IGNITE-13380 - Output
> IgniteSystemProperties via ignite.sh
>
> [1] https://github.com/apache/ignite/pull/8630
>
> > 29 дек. 2020 г., в 21:42, Denis Magda  написал(а):
> >
> > Thanks, Maksim,
> >
> > Considering that most of the contributors will be on holidays through Jan
> > 10th, it's highly unlikely that all documentation tickets will be ready
> by
> > Jan 18th (the vote date).
> >
> > Anyway, Nikita confirmed that he'll be actively working on the tickets
> > starting Jan 11th. As for me, unfortunately, I have no time for
> > contributions in January.
> >
> > Special thanks for preparing a list of resolved but undocumented
> features.
> > Most of those just need to be donated from the GridGain documentation
> page.
> > I'll take care of those.
> >
> > -
> > Denis
> >
> >
> > On Tue, Dec 29, 2020 at 12:43 AM Maxim Muzafarov 
> wrote:
> >
> >> Folks,
> >>
> >> 1.
> >> I've prepared the list of unhandled important documentation issues for
> >> the 2.10 release, please check the wiki page link [1]. Note, that some
> >> of the important (from my point of view) documentation issues even not
> >> created.
> >>
> >> 2.
> >> Here is the list of resolved issues which seems to be documented, but
> >> an appropriate documentation task doesn't exist. Should we create
> >> appropriate documentation issues for them? Check the list [3].
> >>
> >> 3.
> >> Some of the documentation pages must be completed prior to 2.10
> >> release or removed, right? Check the [2] page for example.
> >>
> >>
> >> Denis, Nikita
> >>
> >>> So we should probably allocate more time for this work.
> >> Let's start the work, track the progress and looks at how it goes.
> >> I'll try to ask some folks for the help with documentation and also
> >> plan to help with the issues by myself. We can shift the dates if it's
> >> necessary, but currently, I see no reasons.
> >>
> >>
> >> [1]
> >>
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.10#ApacheIgnite2.10-Documentationtasksforimportantfeatures
> >> [2] https://ignite.apache.org/docs/latest/cpp-specific/
> >> [3] The list of issues without documentation tasks :
> >>
> >> https://issues.apache.org/jira/browse/IGNITE-13488
> >> Add command to control.(sh|bin) to get an arbitrary Metric
> >>
> >> https://issues.apache.org/jira/browse/IGNITE-13467
> >> Add events for snapshot operation state
> >>
> >> https://issues.apache.org/jira/browse/IGNITE-13535
> >> Support cluster snapshot security permissions
> >>
> >> https://issues.apache.org/jira/browse/IGNITE-13426
> >> Add command to control.(sh|bin) to get an arbitrary SystemView
> >>
> >> https://issues.apache.org/jira/browse/IGNITE-13327
> >> Add a metric for processed keys when rebuilding indexes.
> >>
> >> https://issues.apache.org/jira/browse/IGNITE-13310
> >> Add tracing of SQL queries.
> >>
> >> https://issues.apache.org/jira/browse/IGNITE-12380
> >> Add event for node validation failure.
> >>
> >> https://issues.apache.org/jira/browse/IGNITE-7623
> >> Thin client Java API - async API
> >>
> >> https://issues.apache.org/jira/browse/IGNITE-13380
> >> Output IgniteSystemProperties via ignite.sh
> >>
> >> https://issues.apache.org/jira/browse/IGNITE-11731
> >> CPP: Implement Cluster API
> >>
> >> https://issues.apache.org/jira/browse/IGNITE-13308
> >> C++: Thin client transactions
> >>
> >> https://issues.apache.org/jira/browse/IGNITE-12754
> >> .NET: Thin Client: Service invocation
> >>
> >> On Fri, 25 Dec 2020 at 22:43, Никита Сафонов  >
> >> wrote:
> >>>
> >>> Hi Denis, Maxim,
> >>>
> >>> I'd like to clarify that I'm pretty sure to complete the tasks below
> >> before
> >>> the voting date:
> >>>
> >>> https://issues.apache.org/jira/browse/IGNITE-13659
> >>> https://issues.apache.org/jira/browse/IGNITE-13796
> >>>
> >>> I'll start to work on them right after the long Russian NY holidays.
> >>> But I'm not quite sure that we'll meet the deadline with other tickets
> >>> that should be on the list.
> >>> So we should probably allocate more time for this work.
> >>>
> >>> I'd be glad to get your opinion on this.
> >>>
> >>> Regards,
> >>> Nikita
> >>>
> >>> сб, 19 дек. 2020 г. в 11:39, Maxim Muzafarov :
> >>>
>  Denis, Nikita
> 
>  Yes, the list of important documentation issues will be ready prior to
>  the scope freeze date. I'll prepare it.
> 
>  I mean if we want to start working right now on 

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

[Nikolay Izhikov]

Hello.

I prepared docs [1] for the following tickets

Denis, can you, please, take a look?

> https://issues.apache.org/jira/browse/IGNITE-13488 - Add command to 
> control.(sh|bin) to get an arbitrary Metric
> https://issues.apache.org/jira/browse/IGNITE-13426 - Add command to 
> control.(sh|bin) to get an arbitrary SystemView
> https://issues.apache.org/jira/browse/IGNITE-13380 - Output 
> IgniteSystemProperties via ignite.sh

[1] https://github.com/apache/ignite/pull/8630

> 29 дек. 2020 г., в 21:42, Denis Magda  написал(а):
> 
> Thanks, Maksim,
> 
> Considering that most of the contributors will be on holidays through Jan
> 10th, it's highly unlikely that all documentation tickets will be ready by
> Jan 18th (the vote date).
> 
> Anyway, Nikita confirmed that he'll be actively working on the tickets
> starting Jan 11th. As for me, unfortunately, I have no time for
> contributions in January.
> 
> Special thanks for preparing a list of resolved but undocumented features.
> Most of those just need to be donated from the GridGain documentation page.
> I'll take care of those.
> 
> -
> Denis
> 
> 
> On Tue, Dec 29, 2020 at 12:43 AM Maxim Muzafarov  wrote:
> 
>> Folks,
>> 
>> 1.
>> I've prepared the list of unhandled important documentation issues for
>> the 2.10 release, please check the wiki page link [1]. Note, that some
>> of the important (from my point of view) documentation issues even not
>> created.
>> 
>> 2.
>> Here is the list of resolved issues which seems to be documented, but
>> an appropriate documentation task doesn't exist. Should we create
>> appropriate documentation issues for them? Check the list [3].
>> 
>> 3.
>> Some of the documentation pages must be completed prior to 2.10
>> release or removed, right? Check the [2] page for example.
>> 
>> 
>> Denis, Nikita
>> 
>>> So we should probably allocate more time for this work.
>> Let's start the work, track the progress and looks at how it goes.
>> I'll try to ask some folks for the help with documentation and also
>> plan to help with the issues by myself. We can shift the dates if it's
>> necessary, but currently, I see no reasons.
>> 
>> 
>> [1]
>> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.10#ApacheIgnite2.10-Documentationtasksforimportantfeatures
>> [2] https://ignite.apache.org/docs/latest/cpp-specific/
>> [3] The list of issues without documentation tasks :
>> 
>> https://issues.apache.org/jira/browse/IGNITE-13488
>> Add command to control.(sh|bin) to get an arbitrary Metric
>> 
>> https://issues.apache.org/jira/browse/IGNITE-13467
>> Add events for snapshot operation state
>> 
>> https://issues.apache.org/jira/browse/IGNITE-13535
>> Support cluster snapshot security permissions
>> 
>> https://issues.apache.org/jira/browse/IGNITE-13426
>> Add command to control.(sh|bin) to get an arbitrary SystemView
>> 
>> https://issues.apache.org/jira/browse/IGNITE-13327
>> Add a metric for processed keys when rebuilding indexes.
>> 
>> https://issues.apache.org/jira/browse/IGNITE-13310
>> Add tracing of SQL queries.
>> 
>> https://issues.apache.org/jira/browse/IGNITE-12380
>> Add event for node validation failure.
>> 
>> https://issues.apache.org/jira/browse/IGNITE-7623
>> Thin client Java API - async API
>> 
>> https://issues.apache.org/jira/browse/IGNITE-13380
>> Output IgniteSystemProperties via ignite.sh
>> 
>> https://issues.apache.org/jira/browse/IGNITE-11731
>> CPP: Implement Cluster API
>> 
>> https://issues.apache.org/jira/browse/IGNITE-13308
>> C++: Thin client transactions
>> 
>> https://issues.apache.org/jira/browse/IGNITE-12754
>> .NET: Thin Client: Service invocation
>> 
>> On Fri, 25 Dec 2020 at 22:43, Никита Сафонов 
>> wrote:
>>> 
>>> Hi Denis, Maxim,
>>> 
>>> I'd like to clarify that I'm pretty sure to complete the tasks below
>> before
>>> the voting date:
>>> 
>>> https://issues.apache.org/jira/browse/IGNITE-13659
>>> https://issues.apache.org/jira/browse/IGNITE-13796
>>> 
>>> I'll start to work on them right after the long Russian NY holidays.
>>> But I'm not quite sure that we'll meet the deadline with other tickets
>>> that should be on the list.
>>> So we should probably allocate more time for this work.
>>> 
>>> I'd be glad to get your opinion on this.
>>> 
>>> Regards,
>>> Nikita
>>> 
>>> сб, 19 дек. 2020 г. в 11:39, Maxim Muzafarov :
>>> 
 Denis, Nikita
 
 Yes, the list of important documentation issues will be ready prior to
 the scope freeze date. I'll prepare it.
 
 I mean if we want to start working right now on some documentation
 task we can choose any important from those list of opened tasks.
 
 On Fri, 18 Dec 2020 at 19:55, Denis Magda  wrote:
> 
> Maxim,
> 
> Presently, there are 70 documentation tickets. Probably, these are
>> all
 the
> tickets that we are moving from a release to a release. Could you
>> help to
> prepare a list of 2.10-specific tickets (features, enhancements,
>> required
> updates due to a 

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

[Denis Magda]

Thanks, Maksim,

Considering that most of the contributors will be on holidays through Jan
10th, it's highly unlikely that all documentation tickets will be ready by
Jan 18th (the vote date).

Anyway, Nikita confirmed that he'll be actively working on the tickets
starting Jan 11th. As for me, unfortunately, I have no time for
contributions in January.

Special thanks for preparing a list of resolved but undocumented features.
Most of those just need to be donated from the GridGain documentation page.
I'll take care of those.

-
Denis


On Tue, Dec 29, 2020 at 12:43 AM Maxim Muzafarov  wrote:

> Folks,
>
> 1.
> I've prepared the list of unhandled important documentation issues for
> the 2.10 release, please check the wiki page link [1]. Note, that some
> of the important (from my point of view) documentation issues even not
> created.
>
> 2.
> Here is the list of resolved issues which seems to be documented, but
> an appropriate documentation task doesn't exist. Should we create
> appropriate documentation issues for them? Check the list [3].
>
> 3.
> Some of the documentation pages must be completed prior to 2.10
> release or removed, right? Check the [2] page for example.
>
>
> Denis, Nikita
>
> > So we should probably allocate more time for this work.
> Let's start the work, track the progress and looks at how it goes.
> I'll try to ask some folks for the help with documentation and also
> plan to help with the issues by myself. We can shift the dates if it's
> necessary, but currently, I see no reasons.
>
>
> [1]
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.10#ApacheIgnite2.10-Documentationtasksforimportantfeatures
> [2] https://ignite.apache.org/docs/latest/cpp-specific/
> [3] The list of issues without documentation tasks :
>
> https://issues.apache.org/jira/browse/IGNITE-13488
> Add command to control.(sh|bin) to get an arbitrary Metric
>
> https://issues.apache.org/jira/browse/IGNITE-13467
> Add events for snapshot operation state
>
> https://issues.apache.org/jira/browse/IGNITE-13535
> Support cluster snapshot security permissions
>
> https://issues.apache.org/jira/browse/IGNITE-13426
> Add command to control.(sh|bin) to get an arbitrary SystemView
>
> https://issues.apache.org/jira/browse/IGNITE-13327
> Add a metric for processed keys when rebuilding indexes.
>
> https://issues.apache.org/jira/browse/IGNITE-13310
> Add tracing of SQL queries.
>
> https://issues.apache.org/jira/browse/IGNITE-12380
> Add event for node validation failure.
>
> https://issues.apache.org/jira/browse/IGNITE-7623
> Thin client Java API - async API
>
> https://issues.apache.org/jira/browse/IGNITE-13380
> Output IgniteSystemProperties via ignite.sh
>
> https://issues.apache.org/jira/browse/IGNITE-11731
> CPP: Implement Cluster API
>
> https://issues.apache.org/jira/browse/IGNITE-13308
> C++: Thin client transactions
>
> https://issues.apache.org/jira/browse/IGNITE-12754
> .NET: Thin Client: Service invocation
>
> On Fri, 25 Dec 2020 at 22:43, Никита Сафонов 
> wrote:
> >
> > Hi Denis, Maxim,
> >
> > I'd like to clarify that I'm pretty sure to complete the tasks below
> before
> > the voting date:
> >
> > https://issues.apache.org/jira/browse/IGNITE-13659
> > https://issues.apache.org/jira/browse/IGNITE-13796
> >
> > I'll start to work on them right after the long Russian NY holidays.
> > But I'm not quite sure that we'll meet the deadline with other tickets
> > that should be on the list.
> > So we should probably allocate more time for this work.
> >
> > I'd be glad to get your opinion on this.
> >
> > Regards,
> > Nikita
> >
> > сб, 19 дек. 2020 г. в 11:39, Maxim Muzafarov :
> >
> > > Denis, Nikita
> > >
> > > Yes, the list of important documentation issues will be ready prior to
> > > the scope freeze date. I'll prepare it.
> > >
> > > I mean if we want to start working right now on some documentation
> > > task we can choose any important from those list of opened tasks.
> > >
> > > On Fri, 18 Dec 2020 at 19:55, Denis Magda  wrote:
> > > >
> > > > Maxim,
> > > >
> > > > Presently, there are 70 documentation tickets. Probably, these are
> all
> > > the
> > > > tickets that we are moving from a release to a release. Could you
> help to
> > > > prepare a list of 2.10-specific tickets (features, enhancements,
> required
> > > > updates due to a change in the behavior)? As before, we can track
> these
> > > > important 2.10-specific tickets under the "Documentation tasks for
> > > > important tasks" features:
> > > >
> > >
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.10#ApacheIgnite2.10-Documentationtasksforimportantfeatures
> > > >
> > > >
> > > > -
> > > > Denis
> > > >
> > > >
> > > > On Fri, Dec 18, 2020 at 8:14 AM Maxim Muzafarov 
> > > wrote:
> > > >
> > > > > Hello Nikita,
> > > > >
> > > > > Thanks for your support.
> > > > >
> > > > > You can find the 2.10 related documentation issues on the release
> wiki
> > > > > page [1]. Currently, some of the important issues 

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

[Maxim Muzafarov]

Folks,

The branch `ignite-2.10` for the release has been created.

The list of issues related to 2.10 release [1]. If I excluded your
issue you are working on from the release feel free to set the
`fixVersion` back.


[1]  https://s.apache.org/qa6kk

On Tue, 29 Dec 2020 at 11:43, Maxim Muzafarov  wrote:
>
> Folks,
>
> 1.
> I've prepared the list of unhandled important documentation issues for
> the 2.10 release, please check the wiki page link [1]. Note, that some
> of the important (from my point of view) documentation issues even not
> created.
>
> 2.
> Here is the list of resolved issues which seems to be documented, but
> an appropriate documentation task doesn't exist. Should we create
> appropriate documentation issues for them? Check the list [3].
>
> 3.
> Some of the documentation pages must be completed prior to 2.10
> release or removed, right? Check the [2] page for example.
>
>
> Denis, Nikita
>
> > So we should probably allocate more time for this work.
> Let's start the work, track the progress and looks at how it goes.
> I'll try to ask some folks for the help with documentation and also
> plan to help with the issues by myself. We can shift the dates if it's
> necessary, but currently, I see no reasons.
>
>
> [1] 
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.10#ApacheIgnite2.10-Documentationtasksforimportantfeatures
> [2] https://ignite.apache.org/docs/latest/cpp-specific/
> [3] The list of issues without documentation tasks :
>
> https://issues.apache.org/jira/browse/IGNITE-13488
> Add command to control.(sh|bin) to get an arbitrary Metric
>
> https://issues.apache.org/jira/browse/IGNITE-13467
> Add events for snapshot operation state
>
> https://issues.apache.org/jira/browse/IGNITE-13535
> Support cluster snapshot security permissions
>
> https://issues.apache.org/jira/browse/IGNITE-13426
> Add command to control.(sh|bin) to get an arbitrary SystemView
>
> https://issues.apache.org/jira/browse/IGNITE-13327
> Add a metric for processed keys when rebuilding indexes.
>
> https://issues.apache.org/jira/browse/IGNITE-13310
> Add tracing of SQL queries.
>
> https://issues.apache.org/jira/browse/IGNITE-12380
> Add event for node validation failure.
>
> https://issues.apache.org/jira/browse/IGNITE-7623
> Thin client Java API - async API
>
> https://issues.apache.org/jira/browse/IGNITE-13380
> Output IgniteSystemProperties via ignite.sh
>
> https://issues.apache.org/jira/browse/IGNITE-11731
> CPP: Implement Cluster API
>
> https://issues.apache.org/jira/browse/IGNITE-13308
> C++: Thin client transactions
>
> https://issues.apache.org/jira/browse/IGNITE-12754
> .NET: Thin Client: Service invocation
>
> On Fri, 25 Dec 2020 at 22:43, Никита Сафонов  
> wrote:
> >
> > Hi Denis, Maxim,
> >
> > I'd like to clarify that I'm pretty sure to complete the tasks below before
> > the voting date:
> >
> > https://issues.apache.org/jira/browse/IGNITE-13659
> > https://issues.apache.org/jira/browse/IGNITE-13796
> >
> > I'll start to work on them right after the long Russian NY holidays.
> > But I'm not quite sure that we'll meet the deadline with other tickets
> > that should be on the list.
> > So we should probably allocate more time for this work.
> >
> > I'd be glad to get your opinion on this.
> >
> > Regards,
> > Nikita
> >
> > сб, 19 дек. 2020 г. в 11:39, Maxim Muzafarov :
> >
> > > Denis, Nikita
> > >
> > > Yes, the list of important documentation issues will be ready prior to
> > > the scope freeze date. I'll prepare it.
> > >
> > > I mean if we want to start working right now on some documentation
> > > task we can choose any important from those list of opened tasks.
> > >
> > > On Fri, 18 Dec 2020 at 19:55, Denis Magda  wrote:
> > > >
> > > > Maxim,
> > > >
> > > > Presently, there are 70 documentation tickets. Probably, these are all
> > > the
> > > > tickets that we are moving from a release to a release. Could you help 
> > > > to
> > > > prepare a list of 2.10-specific tickets (features, enhancements, 
> > > > required
> > > > updates due to a change in the behavior)? As before, we can track these
> > > > important 2.10-specific tickets under the "Documentation tasks for
> > > > important tasks" features:
> > > >
> > > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.10#ApacheIgnite2.10-Documentationtasksforimportantfeatures
> > > >
> > > >
> > > > -
> > > > Denis
> > > >
> > > >
> > > > On Fri, Dec 18, 2020 at 8:14 AM Maxim Muzafarov 
> > > wrote:
> > > >
> > > > > Hello Nikita,
> > > > >
> > > > > Thanks for your support.
> > > > >
> > > > > You can find the 2.10 related documentation issues on the release wiki
> > > > > page [1]. Currently, some of the important issues don't have the right
> > > > > priorities, so it's better to sort them first.
> > > > >
> > > > > As for the time estimates, we've previously agreed that documentation
> > > > > should be ready prior to the release voting date. You can find the
> > > > > actual release dates here [2].
> 

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

[Maxim Muzafarov]

Folks,

1.
I've prepared the list of unhandled important documentation issues for
the 2.10 release, please check the wiki page link [1]. Note, that some
of the important (from my point of view) documentation issues even not
created.

2.
Here is the list of resolved issues which seems to be documented, but
an appropriate documentation task doesn't exist. Should we create
appropriate documentation issues for them? Check the list [3].

3.
Some of the documentation pages must be completed prior to 2.10
release or removed, right? Check the [2] page for example.


Denis, Nikita

> So we should probably allocate more time for this work.
Let's start the work, track the progress and looks at how it goes.
I'll try to ask some folks for the help with documentation and also
plan to help with the issues by myself. We can shift the dates if it's
necessary, but currently, I see no reasons.


[1] 
https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.10#ApacheIgnite2.10-Documentationtasksforimportantfeatures
[2] https://ignite.apache.org/docs/latest/cpp-specific/
[3] The list of issues without documentation tasks :

https://issues.apache.org/jira/browse/IGNITE-13488
Add command to control.(sh|bin) to get an arbitrary Metric

https://issues.apache.org/jira/browse/IGNITE-13467
Add events for snapshot operation state

https://issues.apache.org/jira/browse/IGNITE-13535
Support cluster snapshot security permissions

https://issues.apache.org/jira/browse/IGNITE-13426
Add command to control.(sh|bin) to get an arbitrary SystemView

https://issues.apache.org/jira/browse/IGNITE-13327
Add a metric for processed keys when rebuilding indexes.

https://issues.apache.org/jira/browse/IGNITE-13310
Add tracing of SQL queries.

https://issues.apache.org/jira/browse/IGNITE-12380
Add event for node validation failure.

https://issues.apache.org/jira/browse/IGNITE-7623
Thin client Java API - async API

https://issues.apache.org/jira/browse/IGNITE-13380
Output IgniteSystemProperties via ignite.sh

https://issues.apache.org/jira/browse/IGNITE-11731
CPP: Implement Cluster API

https://issues.apache.org/jira/browse/IGNITE-13308
C++: Thin client transactions

https://issues.apache.org/jira/browse/IGNITE-12754
.NET: Thin Client: Service invocation

On Fri, 25 Dec 2020 at 22:43, Никита Сафонов  wrote:
>
> Hi Denis, Maxim,
>
> I'd like to clarify that I'm pretty sure to complete the tasks below before
> the voting date:
>
> https://issues.apache.org/jira/browse/IGNITE-13659
> https://issues.apache.org/jira/browse/IGNITE-13796
>
> I'll start to work on them right after the long Russian NY holidays.
> But I'm not quite sure that we'll meet the deadline with other tickets
> that should be on the list.
> So we should probably allocate more time for this work.
>
> I'd be glad to get your opinion on this.
>
> Regards,
> Nikita
>
> сб, 19 дек. 2020 г. в 11:39, Maxim Muzafarov :
>
> > Denis, Nikita
> >
> > Yes, the list of important documentation issues will be ready prior to
> > the scope freeze date. I'll prepare it.
> >
> > I mean if we want to start working right now on some documentation
> > task we can choose any important from those list of opened tasks.
> >
> > On Fri, 18 Dec 2020 at 19:55, Denis Magda  wrote:
> > >
> > > Maxim,
> > >
> > > Presently, there are 70 documentation tickets. Probably, these are all
> > the
> > > tickets that we are moving from a release to a release. Could you help to
> > > prepare a list of 2.10-specific tickets (features, enhancements, required
> > > updates due to a change in the behavior)? As before, we can track these
> > > important 2.10-specific tickets under the "Documentation tasks for
> > > important tasks" features:
> > >
> > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.10#ApacheIgnite2.10-Documentationtasksforimportantfeatures
> > >
> > >
> > > -
> > > Denis
> > >
> > >
> > > On Fri, Dec 18, 2020 at 8:14 AM Maxim Muzafarov 
> > wrote:
> > >
> > > > Hello Nikita,
> > > >
> > > > Thanks for your support.
> > > >
> > > > You can find the 2.10 related documentation issues on the release wiki
> > > > page [1]. Currently, some of the important issues don't have the right
> > > > priorities, so it's better to sort them first.
> > > >
> > > > As for the time estimates, we've previously agreed that documentation
> > > > should be ready prior to the release voting date. You can find the
> > > > actual release dates here [2].
> > > >
> > > > [1]
> > > >
> > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.10#ApacheIgnite2.10-Allunresolveddocumentationtasks
> > > > [2]
> > > >
> > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.10#ApacheIgnite2.10-Releasephases
> > > >
> > > > On Fri, 18 Dec 2020 at 18:48, Никита Сафонов <
> > vlasovpavel2...@gmail.com>
> > > > wrote:
> > > > >
> > > > > Hi guys,
> > > > >
> > > > > I'd be more than happy to support the 2.10 release and contribute to
> > the
> > > > > documentation.
> > > > > So could you please give 

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

[Никита Сафонов]

Hi Denis, Maxim,

I'd like to clarify that I'm pretty sure to complete the tasks below before
the voting date:

https://issues.apache.org/jira/browse/IGNITE-13659
https://issues.apache.org/jira/browse/IGNITE-13796

I'll start to work on them right after the long Russian NY holidays.
But I'm not quite sure that we'll meet the deadline with other tickets
that should be on the list.
So we should probably allocate more time for this work.

I'd be glad to get your opinion on this.

Regards,
Nikita

сб, 19 дек. 2020 г. в 11:39, Maxim Muzafarov :

> Denis, Nikita
>
> Yes, the list of important documentation issues will be ready prior to
> the scope freeze date. I'll prepare it.
>
> I mean if we want to start working right now on some documentation
> task we can choose any important from those list of opened tasks.
>
> On Fri, 18 Dec 2020 at 19:55, Denis Magda  wrote:
> >
> > Maxim,
> >
> > Presently, there are 70 documentation tickets. Probably, these are all
> the
> > tickets that we are moving from a release to a release. Could you help to
> > prepare a list of 2.10-specific tickets (features, enhancements, required
> > updates due to a change in the behavior)? As before, we can track these
> > important 2.10-specific tickets under the "Documentation tasks for
> > important tasks" features:
> >
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.10#ApacheIgnite2.10-Documentationtasksforimportantfeatures
> >
> >
> > -
> > Denis
> >
> >
> > On Fri, Dec 18, 2020 at 8:14 AM Maxim Muzafarov 
> wrote:
> >
> > > Hello Nikita,
> > >
> > > Thanks for your support.
> > >
> > > You can find the 2.10 related documentation issues on the release wiki
> > > page [1]. Currently, some of the important issues don't have the right
> > > priorities, so it's better to sort them first.
> > >
> > > As for the time estimates, we've previously agreed that documentation
> > > should be ready prior to the release voting date. You can find the
> > > actual release dates here [2].
> > >
> > > [1]
> > >
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.10#ApacheIgnite2.10-Allunresolveddocumentationtasks
> > > [2]
> > >
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.10#ApacheIgnite2.10-Releasephases
> > >
> > > On Fri, 18 Dec 2020 at 18:48, Никита Сафонов <
> vlasovpavel2...@gmail.com>
> > > wrote:
> > > >
> > > > Hi guys,
> > > >
> > > > I'd be more than happy to support the 2.10 release and contribute to
> the
> > > > documentation.
> > > > So could you please give me a scope of documentation tasks for 2.10
> with
> > > > the approximate time estimates?
> > > >
> > > > Regards,
> > > > Nikita
> > > >
> > > > пн, 7 дек. 2020 г. в 16:23, Alexey Zinoviev  >:
> > > >
> > > > > Support it
> > > > >
> > > > > пн, 7 дек. 2020 г. в 14:03, Maxim Muzafarov :
> > > > >
> > > > > > Folks,
> > > > > >
> > > > > >
> > > > > > I propose to shift a bit the release date since 2.9.1 has not
> > > released
> > > > > yet.
> > > > > >
> > > > > >
> > > > > > Scope Freeze: December 28, 2020
> > > > > > Code Freeze: December 28, 2020
> > > > > > Voting Date: January 25, 2021
> > > > > > Release Date: February 1, 2021
> > > > > >
> > > > > > WDYT?
> > > > > >
> > > > > > On Tue, 17 Nov 2020 at 12:59, Maxim Muzafarov  >
> > > wrote:
> > > > > > >
> > > > > > > Folks,
> > > > > > >
> > > > > > > I've marked all the valuable features of 2.10 release with an
> > > > > > > appropriate label. Please, let me know if I've missed anything.
> > > > > > >
> > > > > > > Here is the link to the JIRA:
> > > > > > > https://s.apache.org/1hyfu
> > > > > > >
> > > > > > >
> > > > > > > On Thu, 12 Nov 2020 at 12:28, Anton Vinogradov 
> > > wrote:
> > > > > > > >
> > > > > > > > > - Distributed environment tests [2] (Nikolay Izhikov, Anton
> > > > > > > > > Vinogradov, Ivan Daschinskiy)
> > > > > > > > > Will all related issues be included in the 2.10?
> > > > > > > > We're at the final preparations phase. Going to start the
> merge
> > > > > > discussion
> > > > > > > > soon.
> > > > > > > >
> > > > > > > > On Wed, Nov 11, 2020 at 4:48 PM Alexey Zinoviev <
> > > > > > zaleslaw@gmail.com>
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > Yes, Model Export/Import for ML will be finished, now it's
> > > ready,
> > > > > > but under
> > > > > > > > > testing on my side.
> > > > > > > > >
> > > > > > > > > ср, 11 нояб. 2020 г. в 16:08, Nikolay Izhikov <
> > > nizhi...@apache.org
> > > > > >:
> > > > > > > > >
> > > > > > > > > > I suggest to include CDC feature to the 2.10 scope.
> > > > > > > > > >
> > > > > > > > > > > 11 нояб. 2020 г., в 16:06, Maxim Muzafarov <
> > > mmu...@apache.org>
> > > > > > > > > > написал(а):
> > > > > > > > > > >
> > > > > > > > > > > Igniters,
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > Can you clarify the issue statuses according to the
> Apache
> > > > > Ignite
> > > > > > > > > > > Roadmap [1] and the 2.10 Apache Ignite Release? Here
> are
> > > some
> > > > > > 

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

[Maxim Muzafarov]

Igniters,

I'm going to create the `ignite-2.10` release branch on Monday 28-th
December. Please, keep this in mind when merging issues to the master
branch.

I'll also exclude all issues with `Open`, `In progress` states from
the release. As for the `Patch Available` issues, we will discuss this
list on dev-list. Please, let me know what we definitely must include
to the 2.10 release and review.

On Sat, 19 Dec 2020 at 11:39, Maxim Muzafarov  wrote:
>
> Denis, Nikita
>
> Yes, the list of important documentation issues will be ready prior to
> the scope freeze date. I'll prepare it.
>
> I mean if we want to start working right now on some documentation
> task we can choose any important from those list of opened tasks.
>
> On Fri, 18 Dec 2020 at 19:55, Denis Magda  wrote:
> >
> > Maxim,
> >
> > Presently, there are 70 documentation tickets. Probably, these are all the
> > tickets that we are moving from a release to a release. Could you help to
> > prepare a list of 2.10-specific tickets (features, enhancements, required
> > updates due to a change in the behavior)? As before, we can track these
> > important 2.10-specific tickets under the "Documentation tasks for
> > important tasks" features:
> > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.10#ApacheIgnite2.10-Documentationtasksforimportantfeatures
> >
> >
> > -
> > Denis
> >
> >
> > On Fri, Dec 18, 2020 at 8:14 AM Maxim Muzafarov  wrote:
> >
> > > Hello Nikita,
> > >
> > > Thanks for your support.
> > >
> > > You can find the 2.10 related documentation issues on the release wiki
> > > page [1]. Currently, some of the important issues don't have the right
> > > priorities, so it's better to sort them first.
> > >
> > > As for the time estimates, we've previously agreed that documentation
> > > should be ready prior to the release voting date. You can find the
> > > actual release dates here [2].
> > >
> > > [1]
> > > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.10#ApacheIgnite2.10-Allunresolveddocumentationtasks
> > > [2]
> > > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.10#ApacheIgnite2.10-Releasephases
> > >
> > > On Fri, 18 Dec 2020 at 18:48, Никита Сафонов 
> > > wrote:
> > > >
> > > > Hi guys,
> > > >
> > > > I'd be more than happy to support the 2.10 release and contribute to the
> > > > documentation.
> > > > So could you please give me a scope of documentation tasks for 2.10 with
> > > > the approximate time estimates?
> > > >
> > > > Regards,
> > > > Nikita
> > > >
> > > > пн, 7 дек. 2020 г. в 16:23, Alexey Zinoviev :
> > > >
> > > > > Support it
> > > > >
> > > > > пн, 7 дек. 2020 г. в 14:03, Maxim Muzafarov :
> > > > >
> > > > > > Folks,
> > > > > >
> > > > > >
> > > > > > I propose to shift a bit the release date since 2.9.1 has not
> > > released
> > > > > yet.
> > > > > >
> > > > > >
> > > > > > Scope Freeze: December 28, 2020
> > > > > > Code Freeze: December 28, 2020
> > > > > > Voting Date: January 25, 2021
> > > > > > Release Date: February 1, 2021
> > > > > >
> > > > > > WDYT?
> > > > > >
> > > > > > On Tue, 17 Nov 2020 at 12:59, Maxim Muzafarov 
> > > wrote:
> > > > > > >
> > > > > > > Folks,
> > > > > > >
> > > > > > > I've marked all the valuable features of 2.10 release with an
> > > > > > > appropriate label. Please, let me know if I've missed anything.
> > > > > > >
> > > > > > > Here is the link to the JIRA:
> > > > > > > https://s.apache.org/1hyfu
> > > > > > >
> > > > > > >
> > > > > > > On Thu, 12 Nov 2020 at 12:28, Anton Vinogradov 
> > > wrote:
> > > > > > > >
> > > > > > > > > - Distributed environment tests [2] (Nikolay Izhikov, Anton
> > > > > > > > > Vinogradov, Ivan Daschinskiy)
> > > > > > > > > Will all related issues be included in the 2.10?
> > > > > > > > We're at the final preparations phase. Going to start the merge
> > > > > > discussion
> > > > > > > > soon.
> > > > > > > >
> > > > > > > > On Wed, Nov 11, 2020 at 4:48 PM Alexey Zinoviev <
> > > > > > zaleslaw@gmail.com>
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > Yes, Model Export/Import for ML will be finished, now it's
> > > ready,
> > > > > > but under
> > > > > > > > > testing on my side.
> > > > > > > > >
> > > > > > > > > ср, 11 нояб. 2020 г. в 16:08, Nikolay Izhikov <
> > > nizhi...@apache.org
> > > > > >:
> > > > > > > > >
> > > > > > > > > > I suggest to include CDC feature to the 2.10 scope.
> > > > > > > > > >
> > > > > > > > > > > 11 нояб. 2020 г., в 16:06, Maxim Muzafarov <
> > > mmu...@apache.org>
> > > > > > > > > > написал(а):
> > > > > > > > > > >
> > > > > > > > > > > Igniters,
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > Can you clarify the issue statuses according to the Apache
> > > > > Ignite
> > > > > > > > > > > Roadmap [1] and the 2.10 Apache Ignite Release? Here are
> > > some
> > > > > > major
> > > > > > > > > > > issues which are expected to be included in 2.10 with the
> > > > > unknown
> > > > > > > > > > > status:
> > > > > 

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

[Maxim Muzafarov]

Denis, Nikita

Yes, the list of important documentation issues will be ready prior to
the scope freeze date. I'll prepare it.

I mean if we want to start working right now on some documentation
task we can choose any important from those list of opened tasks.

On Fri, 18 Dec 2020 at 19:55, Denis Magda  wrote:
>
> Maxim,
>
> Presently, there are 70 documentation tickets. Probably, these are all the
> tickets that we are moving from a release to a release. Could you help to
> prepare a list of 2.10-specific tickets (features, enhancements, required
> updates due to a change in the behavior)? As before, we can track these
> important 2.10-specific tickets under the "Documentation tasks for
> important tasks" features:
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.10#ApacheIgnite2.10-Documentationtasksforimportantfeatures
>
>
> -
> Denis
>
>
> On Fri, Dec 18, 2020 at 8:14 AM Maxim Muzafarov  wrote:
>
> > Hello Nikita,
> >
> > Thanks for your support.
> >
> > You can find the 2.10 related documentation issues on the release wiki
> > page [1]. Currently, some of the important issues don't have the right
> > priorities, so it's better to sort them first.
> >
> > As for the time estimates, we've previously agreed that documentation
> > should be ready prior to the release voting date. You can find the
> > actual release dates here [2].
> >
> > [1]
> > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.10#ApacheIgnite2.10-Allunresolveddocumentationtasks
> > [2]
> > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.10#ApacheIgnite2.10-Releasephases
> >
> > On Fri, 18 Dec 2020 at 18:48, Никита Сафонов 
> > wrote:
> > >
> > > Hi guys,
> > >
> > > I'd be more than happy to support the 2.10 release and contribute to the
> > > documentation.
> > > So could you please give me a scope of documentation tasks for 2.10 with
> > > the approximate time estimates?
> > >
> > > Regards,
> > > Nikita
> > >
> > > пн, 7 дек. 2020 г. в 16:23, Alexey Zinoviev :
> > >
> > > > Support it
> > > >
> > > > пн, 7 дек. 2020 г. в 14:03, Maxim Muzafarov :
> > > >
> > > > > Folks,
> > > > >
> > > > >
> > > > > I propose to shift a bit the release date since 2.9.1 has not
> > released
> > > > yet.
> > > > >
> > > > >
> > > > > Scope Freeze: December 28, 2020
> > > > > Code Freeze: December 28, 2020
> > > > > Voting Date: January 25, 2021
> > > > > Release Date: February 1, 2021
> > > > >
> > > > > WDYT?
> > > > >
> > > > > On Tue, 17 Nov 2020 at 12:59, Maxim Muzafarov 
> > wrote:
> > > > > >
> > > > > > Folks,
> > > > > >
> > > > > > I've marked all the valuable features of 2.10 release with an
> > > > > > appropriate label. Please, let me know if I've missed anything.
> > > > > >
> > > > > > Here is the link to the JIRA:
> > > > > > https://s.apache.org/1hyfu
> > > > > >
> > > > > >
> > > > > > On Thu, 12 Nov 2020 at 12:28, Anton Vinogradov 
> > wrote:
> > > > > > >
> > > > > > > > - Distributed environment tests [2] (Nikolay Izhikov, Anton
> > > > > > > > Vinogradov, Ivan Daschinskiy)
> > > > > > > > Will all related issues be included in the 2.10?
> > > > > > > We're at the final preparations phase. Going to start the merge
> > > > > discussion
> > > > > > > soon.
> > > > > > >
> > > > > > > On Wed, Nov 11, 2020 at 4:48 PM Alexey Zinoviev <
> > > > > zaleslaw@gmail.com>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Yes, Model Export/Import for ML will be finished, now it's
> > ready,
> > > > > but under
> > > > > > > > testing on my side.
> > > > > > > >
> > > > > > > > ср, 11 нояб. 2020 г. в 16:08, Nikolay Izhikov <
> > nizhi...@apache.org
> > > > >:
> > > > > > > >
> > > > > > > > > I suggest to include CDC feature to the 2.10 scope.
> > > > > > > > >
> > > > > > > > > > 11 нояб. 2020 г., в 16:06, Maxim Muzafarov <
> > mmu...@apache.org>
> > > > > > > > > написал(а):
> > > > > > > > > >
> > > > > > > > > > Igniters,
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Can you clarify the issue statuses according to the Apache
> > > > Ignite
> > > > > > > > > > Roadmap [1] and the 2.10 Apache Ignite Release? Here are
> > some
> > > > > major
> > > > > > > > > > issues which are expected to be included in 2.10 with the
> > > > unknown
> > > > > > > > > > status:
> > > > > > > > > >
> > > > > > > > > > - Distributed environment tests [2] (Nikolay Izhikov, Anton
> > > > > > > > > > Vinogradov, Ivan Daschinskiy)
> > > > > > > > > > Will all related issues be included in the 2.10?
> > > > > > > > > >
> > > > > > > > > > - Native persistence defragmentation [6][7] (Anton
> > Kalashnikov,
> > > > > Sergey
> > > > > > > > > Chugunov)
> > > > > > > > > > Are we on the last mile with this for 2.10?
> > > > > > > > > >
> > > > > > > > > > - Consistency-related improvements for atomic caches [3]
> > > > (Alexey
> > > > > > > > > Scherbakov)
> > > > > > > > > > Do we have the JIRA issue? Will the issue be included in
> > 2.10?
> > > > > > > > > >
> > > > > > > > > > - Tombstone 

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

[Denis Magda]

Maxim,

Presently, there are 70 documentation tickets. Probably, these are all the
tickets that we are moving from a release to a release. Could you help to
prepare a list of 2.10-specific tickets (features, enhancements, required
updates due to a change in the behavior)? As before, we can track these
important 2.10-specific tickets under the "Documentation tasks for
important tasks" features:
https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.10#ApacheIgnite2.10-Documentationtasksforimportantfeatures


-
Denis


On Fri, Dec 18, 2020 at 8:14 AM Maxim Muzafarov  wrote:

> Hello Nikita,
>
> Thanks for your support.
>
> You can find the 2.10 related documentation issues on the release wiki
> page [1]. Currently, some of the important issues don't have the right
> priorities, so it's better to sort them first.
>
> As for the time estimates, we've previously agreed that documentation
> should be ready prior to the release voting date. You can find the
> actual release dates here [2].
>
> [1]
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.10#ApacheIgnite2.10-Allunresolveddocumentationtasks
> [2]
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.10#ApacheIgnite2.10-Releasephases
>
> On Fri, 18 Dec 2020 at 18:48, Никита Сафонов 
> wrote:
> >
> > Hi guys,
> >
> > I'd be more than happy to support the 2.10 release and contribute to the
> > documentation.
> > So could you please give me a scope of documentation tasks for 2.10 with
> > the approximate time estimates?
> >
> > Regards,
> > Nikita
> >
> > пн, 7 дек. 2020 г. в 16:23, Alexey Zinoviev :
> >
> > > Support it
> > >
> > > пн, 7 дек. 2020 г. в 14:03, Maxim Muzafarov :
> > >
> > > > Folks,
> > > >
> > > >
> > > > I propose to shift a bit the release date since 2.9.1 has not
> released
> > > yet.
> > > >
> > > >
> > > > Scope Freeze: December 28, 2020
> > > > Code Freeze: December 28, 2020
> > > > Voting Date: January 25, 2021
> > > > Release Date: February 1, 2021
> > > >
> > > > WDYT?
> > > >
> > > > On Tue, 17 Nov 2020 at 12:59, Maxim Muzafarov 
> wrote:
> > > > >
> > > > > Folks,
> > > > >
> > > > > I've marked all the valuable features of 2.10 release with an
> > > > > appropriate label. Please, let me know if I've missed anything.
> > > > >
> > > > > Here is the link to the JIRA:
> > > > > https://s.apache.org/1hyfu
> > > > >
> > > > >
> > > > > On Thu, 12 Nov 2020 at 12:28, Anton Vinogradov 
> wrote:
> > > > > >
> > > > > > > - Distributed environment tests [2] (Nikolay Izhikov, Anton
> > > > > > > Vinogradov, Ivan Daschinskiy)
> > > > > > > Will all related issues be included in the 2.10?
> > > > > > We're at the final preparations phase. Going to start the merge
> > > > discussion
> > > > > > soon.
> > > > > >
> > > > > > On Wed, Nov 11, 2020 at 4:48 PM Alexey Zinoviev <
> > > > zaleslaw@gmail.com>
> > > > > > wrote:
> > > > > >
> > > > > > > Yes, Model Export/Import for ML will be finished, now it's
> ready,
> > > > but under
> > > > > > > testing on my side.
> > > > > > >
> > > > > > > ср, 11 нояб. 2020 г. в 16:08, Nikolay Izhikov <
> nizhi...@apache.org
> > > >:
> > > > > > >
> > > > > > > > I suggest to include CDC feature to the 2.10 scope.
> > > > > > > >
> > > > > > > > > 11 нояб. 2020 г., в 16:06, Maxim Muzafarov <
> mmu...@apache.org>
> > > > > > > > написал(а):
> > > > > > > > >
> > > > > > > > > Igniters,
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Can you clarify the issue statuses according to the Apache
> > > Ignite
> > > > > > > > > Roadmap [1] and the 2.10 Apache Ignite Release? Here are
> some
> > > > major
> > > > > > > > > issues which are expected to be included in 2.10 with the
> > > unknown
> > > > > > > > > status:
> > > > > > > > >
> > > > > > > > > - Distributed environment tests [2] (Nikolay Izhikov, Anton
> > > > > > > > > Vinogradov, Ivan Daschinskiy)
> > > > > > > > > Will all related issues be included in the 2.10?
> > > > > > > > >
> > > > > > > > > - Native persistence defragmentation [6][7] (Anton
> Kalashnikov,
> > > > Sergey
> > > > > > > > Chugunov)
> > > > > > > > > Are we on the last mile with this for 2.10?
> > > > > > > > >
> > > > > > > > > - Consistency-related improvements for atomic caches [3]
> > > (Alexey
> > > > > > > > Scherbakov)
> > > > > > > > > Do we have the JIRA issue? Will the issue be included in
> 2.10?
> > > > > > > > >
> > > > > > > > > - Tombstone objects during rebalancing [4] (Alexey
> Scherbakov)
> > > > > > > > > The issue [4] is in progress state. Will it be finished
> prior
> > > to
> > > > code
> > > > > > > > freeze?
> > > > > > > > >
> > > > > > > > > - SQL runtime statistics (Konstantin Orlov)
> > > > > > > > > Do we have an IEP for this or JIRA issue?
> > > > > > > > >
> > > > > > > > > - ML Model export/import [5] (Alexey Zinoviev)
> > > > > > > > > - Will the issue be finished?
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > [1]
> > > > > > > >
> > > >
> 

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

[Maxim Muzafarov]

Hello Nikita,

Thanks for your support.

You can find the 2.10 related documentation issues on the release wiki
page [1]. Currently, some of the important issues don't have the right
priorities, so it's better to sort them first.

As for the time estimates, we've previously agreed that documentation
should be ready prior to the release voting date. You can find the
actual release dates here [2].

[1] 
https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.10#ApacheIgnite2.10-Allunresolveddocumentationtasks
[2] 
https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.10#ApacheIgnite2.10-Releasephases

On Fri, 18 Dec 2020 at 18:48, Никита Сафонов  wrote:
>
> Hi guys,
>
> I'd be more than happy to support the 2.10 release and contribute to the
> documentation.
> So could you please give me a scope of documentation tasks for 2.10 with
> the approximate time estimates?
>
> Regards,
> Nikita
>
> пн, 7 дек. 2020 г. в 16:23, Alexey Zinoviev :
>
> > Support it
> >
> > пн, 7 дек. 2020 г. в 14:03, Maxim Muzafarov :
> >
> > > Folks,
> > >
> > >
> > > I propose to shift a bit the release date since 2.9.1 has not released
> > yet.
> > >
> > >
> > > Scope Freeze: December 28, 2020
> > > Code Freeze: December 28, 2020
> > > Voting Date: January 25, 2021
> > > Release Date: February 1, 2021
> > >
> > > WDYT?
> > >
> > > On Tue, 17 Nov 2020 at 12:59, Maxim Muzafarov  wrote:
> > > >
> > > > Folks,
> > > >
> > > > I've marked all the valuable features of 2.10 release with an
> > > > appropriate label. Please, let me know if I've missed anything.
> > > >
> > > > Here is the link to the JIRA:
> > > > https://s.apache.org/1hyfu
> > > >
> > > >
> > > > On Thu, 12 Nov 2020 at 12:28, Anton Vinogradov  wrote:
> > > > >
> > > > > > - Distributed environment tests [2] (Nikolay Izhikov, Anton
> > > > > > Vinogradov, Ivan Daschinskiy)
> > > > > > Will all related issues be included in the 2.10?
> > > > > We're at the final preparations phase. Going to start the merge
> > > discussion
> > > > > soon.
> > > > >
> > > > > On Wed, Nov 11, 2020 at 4:48 PM Alexey Zinoviev <
> > > zaleslaw@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > Yes, Model Export/Import for ML will be finished, now it's ready,
> > > but under
> > > > > > testing on my side.
> > > > > >
> > > > > > ср, 11 нояб. 2020 г. в 16:08, Nikolay Izhikov  > >:
> > > > > >
> > > > > > > I suggest to include CDC feature to the 2.10 scope.
> > > > > > >
> > > > > > > > 11 нояб. 2020 г., в 16:06, Maxim Muzafarov 
> > > > > > > написал(а):
> > > > > > > >
> > > > > > > > Igniters,
> > > > > > > >
> > > > > > > >
> > > > > > > > Can you clarify the issue statuses according to the Apache
> > Ignite
> > > > > > > > Roadmap [1] and the 2.10 Apache Ignite Release? Here are some
> > > major
> > > > > > > > issues which are expected to be included in 2.10 with the
> > unknown
> > > > > > > > status:
> > > > > > > >
> > > > > > > > - Distributed environment tests [2] (Nikolay Izhikov, Anton
> > > > > > > > Vinogradov, Ivan Daschinskiy)
> > > > > > > > Will all related issues be included in the 2.10?
> > > > > > > >
> > > > > > > > - Native persistence defragmentation [6][7] (Anton Kalashnikov,
> > > Sergey
> > > > > > > Chugunov)
> > > > > > > > Are we on the last mile with this for 2.10?
> > > > > > > >
> > > > > > > > - Consistency-related improvements for atomic caches [3]
> > (Alexey
> > > > > > > Scherbakov)
> > > > > > > > Do we have the JIRA issue? Will the issue be included in 2.10?
> > > > > > > >
> > > > > > > > - Tombstone objects during rebalancing [4] (Alexey Scherbakov)
> > > > > > > > The issue [4] is in progress state. Will it be finished prior
> > to
> > > code
> > > > > > > freeze?
> > > > > > > >
> > > > > > > > - SQL runtime statistics (Konstantin Orlov)
> > > > > > > > Do we have an IEP for this or JIRA issue?
> > > > > > > >
> > > > > > > > - ML Model export/import [5] (Alexey Zinoviev)
> > > > > > > > - Will the issue be finished?
> > > > > > > >
> > > > > > > >
> > > > > > > > [1]
> > > > > > >
> > > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+Roadmap
> > > > > > > > [2]
> > > > > > >
> > > > > >
> > >
> > https://cwiki.apache.org/confluence/display/IGNITE/IEP-56%3A+Distributed+environment+tests
> > > > > > > > [3]
> > > > > > >
> > > > > >
> > >
> > https://cwiki.apache.org/confluence/display/IGNITE/IEP-12+Make+ATOMIC+Caches+Consistent+Again
> > > > > > > > [4] https://issues.apache.org/jira/browse/IGNITE-11704
> > > > > > > > [5] https://issues.apache.org/jira/browse/IGNITE-6642
> > > > > > > > [6] https://issues.apache.org/jira/browse/IGNITE-13143
> > > > > > > > [7]
> > > > > > >
> > > > > >
> > >
> > https://cwiki.apache.org/confluence/display/IGNITE/IEP-47%3A+Native+persistence+defragmentation
> > > > > > > >
> > > > > > > > On Tue, 10 Nov 2020 at 15:58, Maxim Muzafarov <
> > mmu...@apache.org
> > > >
> > > > > > wrote:
> > > > > > > >>
> > > > > > > >> Folks,
> > > > > > > >>
> > > > > > > >> I've created the 

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

[Никита Сафонов]

Hi guys,

I'd be more than happy to support the 2.10 release and contribute to the
documentation.
So could you please give me a scope of documentation tasks for 2.10 with
the approximate time estimates?

Regards,
Nikita

пн, 7 дек. 2020 г. в 16:23, Alexey Zinoviev :

> Support it
>
> пн, 7 дек. 2020 г. в 14:03, Maxim Muzafarov :
>
> > Folks,
> >
> >
> > I propose to shift a bit the release date since 2.9.1 has not released
> yet.
> >
> >
> > Scope Freeze: December 28, 2020
> > Code Freeze: December 28, 2020
> > Voting Date: January 25, 2021
> > Release Date: February 1, 2021
> >
> > WDYT?
> >
> > On Tue, 17 Nov 2020 at 12:59, Maxim Muzafarov  wrote:
> > >
> > > Folks,
> > >
> > > I've marked all the valuable features of 2.10 release with an
> > > appropriate label. Please, let me know if I've missed anything.
> > >
> > > Here is the link to the JIRA:
> > > https://s.apache.org/1hyfu
> > >
> > >
> > > On Thu, 12 Nov 2020 at 12:28, Anton Vinogradov  wrote:
> > > >
> > > > > - Distributed environment tests [2] (Nikolay Izhikov, Anton
> > > > > Vinogradov, Ivan Daschinskiy)
> > > > > Will all related issues be included in the 2.10?
> > > > We're at the final preparations phase. Going to start the merge
> > discussion
> > > > soon.
> > > >
> > > > On Wed, Nov 11, 2020 at 4:48 PM Alexey Zinoviev <
> > zaleslaw@gmail.com>
> > > > wrote:
> > > >
> > > > > Yes, Model Export/Import for ML will be finished, now it's ready,
> > but under
> > > > > testing on my side.
> > > > >
> > > > > ср, 11 нояб. 2020 г. в 16:08, Nikolay Izhikov  >:
> > > > >
> > > > > > I suggest to include CDC feature to the 2.10 scope.
> > > > > >
> > > > > > > 11 нояб. 2020 г., в 16:06, Maxim Muzafarov 
> > > > > > написал(а):
> > > > > > >
> > > > > > > Igniters,
> > > > > > >
> > > > > > >
> > > > > > > Can you clarify the issue statuses according to the Apache
> Ignite
> > > > > > > Roadmap [1] and the 2.10 Apache Ignite Release? Here are some
> > major
> > > > > > > issues which are expected to be included in 2.10 with the
> unknown
> > > > > > > status:
> > > > > > >
> > > > > > > - Distributed environment tests [2] (Nikolay Izhikov, Anton
> > > > > > > Vinogradov, Ivan Daschinskiy)
> > > > > > > Will all related issues be included in the 2.10?
> > > > > > >
> > > > > > > - Native persistence defragmentation [6][7] (Anton Kalashnikov,
> > Sergey
> > > > > > Chugunov)
> > > > > > > Are we on the last mile with this for 2.10?
> > > > > > >
> > > > > > > - Consistency-related improvements for atomic caches [3]
> (Alexey
> > > > > > Scherbakov)
> > > > > > > Do we have the JIRA issue? Will the issue be included in 2.10?
> > > > > > >
> > > > > > > - Tombstone objects during rebalancing [4] (Alexey Scherbakov)
> > > > > > > The issue [4] is in progress state. Will it be finished prior
> to
> > code
> > > > > > freeze?
> > > > > > >
> > > > > > > - SQL runtime statistics (Konstantin Orlov)
> > > > > > > Do we have an IEP for this or JIRA issue?
> > > > > > >
> > > > > > > - ML Model export/import [5] (Alexey Zinoviev)
> > > > > > > - Will the issue be finished?
> > > > > > >
> > > > > > >
> > > > > > > [1]
> > > > > >
> > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+Roadmap
> > > > > > > [2]
> > > > > >
> > > > >
> >
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-56%3A+Distributed+environment+tests
> > > > > > > [3]
> > > > > >
> > > > >
> >
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-12+Make+ATOMIC+Caches+Consistent+Again
> > > > > > > [4] https://issues.apache.org/jira/browse/IGNITE-11704
> > > > > > > [5] https://issues.apache.org/jira/browse/IGNITE-6642
> > > > > > > [6] https://issues.apache.org/jira/browse/IGNITE-13143
> > > > > > > [7]
> > > > > >
> > > > >
> >
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-47%3A+Native+persistence+defragmentation
> > > > > > >
> > > > > > > On Tue, 10 Nov 2020 at 15:58, Maxim Muzafarov <
> mmu...@apache.org
> > >
> > > > > wrote:
> > > > > > >>
> > > > > > >> Folks,
> > > > > > >>
> > > > > > >> I've created the release page on the Confluence. Feel free to
> > mail in
> > > > > > >> case of any errors.
> > > > > > >>
> > > > > > >>
> > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.10
> > > > > > >>
> > > > > > >> On Fri, 6 Nov 2020 at 17:56, Maxim Muzafarov <
> mmu...@apache.org
> > >
> > > > > wrote:
> > > > > > >>>
> > > > > > >>> Igniters,
> > > > > > >>>
> > > > > > >>>
> > > > > > >>> Let's finalize the discussion [1] about the next upcoming
> major
> > > > > Apache
> > > > > > >>> Ignite 2.10  release. The major improvements related to the
> > proposed
> > > > > > >>> release:
> > > > > > >>> - Improvements for partition clearing related parts
> > > > > > >>> - Add tracing of SQL queries.
> > > > > > >>> - CPP: Implement Cluster API
> > > > > > >>> - .NET: Thin client: Transactions
> > > > > > >>> - .NET: Thin Client: Continuous Query
> > > > > > >>> - Java Thin client Kubernetes discovery
> > > > > > >>>
> > > > > > >>> 

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

[Alexey Zinoviev]

Support it

пн, 7 дек. 2020 г. в 14:03, Maxim Muzafarov :

> Folks,
>
>
> I propose to shift a bit the release date since 2.9.1 has not released yet.
>
>
> Scope Freeze: December 28, 2020
> Code Freeze: December 28, 2020
> Voting Date: January 25, 2021
> Release Date: February 1, 2021
>
> WDYT?
>
> On Tue, 17 Nov 2020 at 12:59, Maxim Muzafarov  wrote:
> >
> > Folks,
> >
> > I've marked all the valuable features of 2.10 release with an
> > appropriate label. Please, let me know if I've missed anything.
> >
> > Here is the link to the JIRA:
> > https://s.apache.org/1hyfu
> >
> >
> > On Thu, 12 Nov 2020 at 12:28, Anton Vinogradov  wrote:
> > >
> > > > - Distributed environment tests [2] (Nikolay Izhikov, Anton
> > > > Vinogradov, Ivan Daschinskiy)
> > > > Will all related issues be included in the 2.10?
> > > We're at the final preparations phase. Going to start the merge
> discussion
> > > soon.
> > >
> > > On Wed, Nov 11, 2020 at 4:48 PM Alexey Zinoviev <
> zaleslaw@gmail.com>
> > > wrote:
> > >
> > > > Yes, Model Export/Import for ML will be finished, now it's ready,
> but under
> > > > testing on my side.
> > > >
> > > > ср, 11 нояб. 2020 г. в 16:08, Nikolay Izhikov :
> > > >
> > > > > I suggest to include CDC feature to the 2.10 scope.
> > > > >
> > > > > > 11 нояб. 2020 г., в 16:06, Maxim Muzafarov 
> > > > > написал(а):
> > > > > >
> > > > > > Igniters,
> > > > > >
> > > > > >
> > > > > > Can you clarify the issue statuses according to the Apache Ignite
> > > > > > Roadmap [1] and the 2.10 Apache Ignite Release? Here are some
> major
> > > > > > issues which are expected to be included in 2.10 with the unknown
> > > > > > status:
> > > > > >
> > > > > > - Distributed environment tests [2] (Nikolay Izhikov, Anton
> > > > > > Vinogradov, Ivan Daschinskiy)
> > > > > > Will all related issues be included in the 2.10?
> > > > > >
> > > > > > - Native persistence defragmentation [6][7] (Anton Kalashnikov,
> Sergey
> > > > > Chugunov)
> > > > > > Are we on the last mile with this for 2.10?
> > > > > >
> > > > > > - Consistency-related improvements for atomic caches [3] (Alexey
> > > > > Scherbakov)
> > > > > > Do we have the JIRA issue? Will the issue be included in 2.10?
> > > > > >
> > > > > > - Tombstone objects during rebalancing [4] (Alexey Scherbakov)
> > > > > > The issue [4] is in progress state. Will it be finished prior to
> code
> > > > > freeze?
> > > > > >
> > > > > > - SQL runtime statistics (Konstantin Orlov)
> > > > > > Do we have an IEP for this or JIRA issue?
> > > > > >
> > > > > > - ML Model export/import [5] (Alexey Zinoviev)
> > > > > > - Will the issue be finished?
> > > > > >
> > > > > >
> > > > > > [1]
> > > > >
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+Roadmap
> > > > > > [2]
> > > > >
> > > >
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-56%3A+Distributed+environment+tests
> > > > > > [3]
> > > > >
> > > >
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-12+Make+ATOMIC+Caches+Consistent+Again
> > > > > > [4] https://issues.apache.org/jira/browse/IGNITE-11704
> > > > > > [5] https://issues.apache.org/jira/browse/IGNITE-6642
> > > > > > [6] https://issues.apache.org/jira/browse/IGNITE-13143
> > > > > > [7]
> > > > >
> > > >
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-47%3A+Native+persistence+defragmentation
> > > > > >
> > > > > > On Tue, 10 Nov 2020 at 15:58, Maxim Muzafarov  >
> > > > wrote:
> > > > > >>
> > > > > >> Folks,
> > > > > >>
> > > > > >> I've created the release page on the Confluence. Feel free to
> mail in
> > > > > >> case of any errors.
> > > > > >>
> > > > > >>
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.10
> > > > > >>
> > > > > >> On Fri, 6 Nov 2020 at 17:56, Maxim Muzafarov  >
> > > > wrote:
> > > > > >>>
> > > > > >>> Igniters,
> > > > > >>>
> > > > > >>>
> > > > > >>> Let's finalize the discussion [1] about the next upcoming major
> > > > Apache
> > > > > >>> Ignite 2.10  release. The major improvements related to the
> proposed
> > > > > >>> release:
> > > > > >>> - Improvements for partition clearing related parts
> > > > > >>> - Add tracing of SQL queries.
> > > > > >>> - CPP: Implement Cluster API
> > > > > >>> - .NET: Thin client: Transactions
> > > > > >>> - .NET: Thin Client: Continuous Query
> > > > > >>> - Java Thin client Kubernetes discovery
> > > > > >>>
> > > > > >>> etc.
> > > > > >>> Total: 166 RESOLVED issues [2].
> > > > > >>>
> > > > > >>>
> > > > > >>> Let's start the discussion about Time and Scope, and also I
> propose
> > > > > >>> myself as the release manager of the Apache Ignite 2.10. If
> you'd
> > > > like
> > > > > >>> to lead this release, please, let us know, I see no problems
> to chose
> > > > > >>> a better candidate.
> > > > > >>>
> > > > > >>>
> > > > > >>> Proposed release timeline:
> > > > > >>>
> > > > > >>> Scope Freeze: December 10, 2020
> > > > > >>> Code Freeze: December 24, 2020
> > > > > >>> Voting Date: January 18, 2021
> > > > > 

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

[Maxim Muzafarov]

Folks,


I propose to shift a bit the release date since 2.9.1 has not released yet.


Scope Freeze: December 28, 2020
Code Freeze: December 28, 2020
Voting Date: January 25, 2021
Release Date: February 1, 2021

WDYT?

On Tue, 17 Nov 2020 at 12:59, Maxim Muzafarov  wrote:
>
> Folks,
>
> I've marked all the valuable features of 2.10 release with an
> appropriate label. Please, let me know if I've missed anything.
>
> Here is the link to the JIRA:
> https://s.apache.org/1hyfu
>
>
> On Thu, 12 Nov 2020 at 12:28, Anton Vinogradov  wrote:
> >
> > > - Distributed environment tests [2] (Nikolay Izhikov, Anton
> > > Vinogradov, Ivan Daschinskiy)
> > > Will all related issues be included in the 2.10?
> > We're at the final preparations phase. Going to start the merge discussion
> > soon.
> >
> > On Wed, Nov 11, 2020 at 4:48 PM Alexey Zinoviev 
> > wrote:
> >
> > > Yes, Model Export/Import for ML will be finished, now it's ready, but 
> > > under
> > > testing on my side.
> > >
> > > ср, 11 нояб. 2020 г. в 16:08, Nikolay Izhikov :
> > >
> > > > I suggest to include CDC feature to the 2.10 scope.
> > > >
> > > > > 11 нояб. 2020 г., в 16:06, Maxim Muzafarov 
> > > > написал(а):
> > > > >
> > > > > Igniters,
> > > > >
> > > > >
> > > > > Can you clarify the issue statuses according to the Apache Ignite
> > > > > Roadmap [1] and the 2.10 Apache Ignite Release? Here are some major
> > > > > issues which are expected to be included in 2.10 with the unknown
> > > > > status:
> > > > >
> > > > > - Distributed environment tests [2] (Nikolay Izhikov, Anton
> > > > > Vinogradov, Ivan Daschinskiy)
> > > > > Will all related issues be included in the 2.10?
> > > > >
> > > > > - Native persistence defragmentation [6][7] (Anton Kalashnikov, Sergey
> > > > Chugunov)
> > > > > Are we on the last mile with this for 2.10?
> > > > >
> > > > > - Consistency-related improvements for atomic caches [3] (Alexey
> > > > Scherbakov)
> > > > > Do we have the JIRA issue? Will the issue be included in 2.10?
> > > > >
> > > > > - Tombstone objects during rebalancing [4] (Alexey Scherbakov)
> > > > > The issue [4] is in progress state. Will it be finished prior to code
> > > > freeze?
> > > > >
> > > > > - SQL runtime statistics (Konstantin Orlov)
> > > > > Do we have an IEP for this or JIRA issue?
> > > > >
> > > > > - ML Model export/import [5] (Alexey Zinoviev)
> > > > > - Will the issue be finished?
> > > > >
> > > > >
> > > > > [1]
> > > > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+Roadmap
> > > > > [2]
> > > >
> > > https://cwiki.apache.org/confluence/display/IGNITE/IEP-56%3A+Distributed+environment+tests
> > > > > [3]
> > > >
> > > https://cwiki.apache.org/confluence/display/IGNITE/IEP-12+Make+ATOMIC+Caches+Consistent+Again
> > > > > [4] https://issues.apache.org/jira/browse/IGNITE-11704
> > > > > [5] https://issues.apache.org/jira/browse/IGNITE-6642
> > > > > [6] https://issues.apache.org/jira/browse/IGNITE-13143
> > > > > [7]
> > > >
> > > https://cwiki.apache.org/confluence/display/IGNITE/IEP-47%3A+Native+persistence+defragmentation
> > > > >
> > > > > On Tue, 10 Nov 2020 at 15:58, Maxim Muzafarov 
> > > wrote:
> > > > >>
> > > > >> Folks,
> > > > >>
> > > > >> I've created the release page on the Confluence. Feel free to mail in
> > > > >> case of any errors.
> > > > >>
> > > > >> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.10
> > > > >>
> > > > >> On Fri, 6 Nov 2020 at 17:56, Maxim Muzafarov 
> > > wrote:
> > > > >>>
> > > > >>> Igniters,
> > > > >>>
> > > > >>>
> > > > >>> Let's finalize the discussion [1] about the next upcoming major
> > > Apache
> > > > >>> Ignite 2.10  release. The major improvements related to the proposed
> > > > >>> release:
> > > > >>> - Improvements for partition clearing related parts
> > > > >>> - Add tracing of SQL queries.
> > > > >>> - CPP: Implement Cluster API
> > > > >>> - .NET: Thin client: Transactions
> > > > >>> - .NET: Thin Client: Continuous Query
> > > > >>> - Java Thin client Kubernetes discovery
> > > > >>>
> > > > >>> etc.
> > > > >>> Total: 166 RESOLVED issues [2].
> > > > >>>
> > > > >>>
> > > > >>> Let's start the discussion about Time and Scope, and also I propose
> > > > >>> myself as the release manager of the Apache Ignite 2.10. If you'd
> > > like
> > > > >>> to lead this release, please, let us know, I see no problems to 
> > > > >>> chose
> > > > >>> a better candidate.
> > > > >>>
> > > > >>>
> > > > >>> Proposed release timeline:
> > > > >>>
> > > > >>> Scope Freeze: December 10, 2020
> > > > >>> Code Freeze: December 24, 2020
> > > > >>> Voting Date: January 18, 2021
> > > > >>> Release Date: January 25, 2021
> > > > >>>
> > > > >>>
> > > > >>> Proposed release scope:
> > > > >>> [2]
> > > > >>>
> > > > >>>
> > > > >>> WDYT?
> > > > >>>
> > > > >>>
> > > > >>> [1]
> > > >
> > > http://apache-ignite-developers.2346864.n4.nabble.com/2-9-1-release-proposal-tp49769p49867.html
> > > > >>> [2]
> > > >
> > > 

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

[Maxim Muzafarov]

Folks,

I've marked all the valuable features of 2.10 release with an
appropriate label. Please, let me know if I've missed anything.

Here is the link to the JIRA:
https://s.apache.org/1hyfu


On Thu, 12 Nov 2020 at 12:28, Anton Vinogradov  wrote:
>
> > - Distributed environment tests [2] (Nikolay Izhikov, Anton
> > Vinogradov, Ivan Daschinskiy)
> > Will all related issues be included in the 2.10?
> We're at the final preparations phase. Going to start the merge discussion
> soon.
>
> On Wed, Nov 11, 2020 at 4:48 PM Alexey Zinoviev 
> wrote:
>
> > Yes, Model Export/Import for ML will be finished, now it's ready, but under
> > testing on my side.
> >
> > ср, 11 нояб. 2020 г. в 16:08, Nikolay Izhikov :
> >
> > > I suggest to include CDC feature to the 2.10 scope.
> > >
> > > > 11 нояб. 2020 г., в 16:06, Maxim Muzafarov 
> > > написал(а):
> > > >
> > > > Igniters,
> > > >
> > > >
> > > > Can you clarify the issue statuses according to the Apache Ignite
> > > > Roadmap [1] and the 2.10 Apache Ignite Release? Here are some major
> > > > issues which are expected to be included in 2.10 with the unknown
> > > > status:
> > > >
> > > > - Distributed environment tests [2] (Nikolay Izhikov, Anton
> > > > Vinogradov, Ivan Daschinskiy)
> > > > Will all related issues be included in the 2.10?
> > > >
> > > > - Native persistence defragmentation [6][7] (Anton Kalashnikov, Sergey
> > > Chugunov)
> > > > Are we on the last mile with this for 2.10?
> > > >
> > > > - Consistency-related improvements for atomic caches [3] (Alexey
> > > Scherbakov)
> > > > Do we have the JIRA issue? Will the issue be included in 2.10?
> > > >
> > > > - Tombstone objects during rebalancing [4] (Alexey Scherbakov)
> > > > The issue [4] is in progress state. Will it be finished prior to code
> > > freeze?
> > > >
> > > > - SQL runtime statistics (Konstantin Orlov)
> > > > Do we have an IEP for this or JIRA issue?
> > > >
> > > > - ML Model export/import [5] (Alexey Zinoviev)
> > > > - Will the issue be finished?
> > > >
> > > >
> > > > [1]
> > > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+Roadmap
> > > > [2]
> > >
> > https://cwiki.apache.org/confluence/display/IGNITE/IEP-56%3A+Distributed+environment+tests
> > > > [3]
> > >
> > https://cwiki.apache.org/confluence/display/IGNITE/IEP-12+Make+ATOMIC+Caches+Consistent+Again
> > > > [4] https://issues.apache.org/jira/browse/IGNITE-11704
> > > > [5] https://issues.apache.org/jira/browse/IGNITE-6642
> > > > [6] https://issues.apache.org/jira/browse/IGNITE-13143
> > > > [7]
> > >
> > https://cwiki.apache.org/confluence/display/IGNITE/IEP-47%3A+Native+persistence+defragmentation
> > > >
> > > > On Tue, 10 Nov 2020 at 15:58, Maxim Muzafarov 
> > wrote:
> > > >>
> > > >> Folks,
> > > >>
> > > >> I've created the release page on the Confluence. Feel free to mail in
> > > >> case of any errors.
> > > >>
> > > >> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.10
> > > >>
> > > >> On Fri, 6 Nov 2020 at 17:56, Maxim Muzafarov 
> > wrote:
> > > >>>
> > > >>> Igniters,
> > > >>>
> > > >>>
> > > >>> Let's finalize the discussion [1] about the next upcoming major
> > Apache
> > > >>> Ignite 2.10  release. The major improvements related to the proposed
> > > >>> release:
> > > >>> - Improvements for partition clearing related parts
> > > >>> - Add tracing of SQL queries.
> > > >>> - CPP: Implement Cluster API
> > > >>> - .NET: Thin client: Transactions
> > > >>> - .NET: Thin Client: Continuous Query
> > > >>> - Java Thin client Kubernetes discovery
> > > >>>
> > > >>> etc.
> > > >>> Total: 166 RESOLVED issues [2].
> > > >>>
> > > >>>
> > > >>> Let's start the discussion about Time and Scope, and also I propose
> > > >>> myself as the release manager of the Apache Ignite 2.10. If you'd
> > like
> > > >>> to lead this release, please, let us know, I see no problems to chose
> > > >>> a better candidate.
> > > >>>
> > > >>>
> > > >>> Proposed release timeline:
> > > >>>
> > > >>> Scope Freeze: December 10, 2020
> > > >>> Code Freeze: December 24, 2020
> > > >>> Voting Date: January 18, 2021
> > > >>> Release Date: January 25, 2021
> > > >>>
> > > >>>
> > > >>> Proposed release scope:
> > > >>> [2]
> > > >>>
> > > >>>
> > > >>> WDYT?
> > > >>>
> > > >>>
> > > >>> [1]
> > >
> > http://apache-ignite-developers.2346864.n4.nabble.com/2-9-1-release-proposal-tp49769p49867.html
> > > >>> [2]
> > >
> > https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%202.10%20and%20status%20in%20(Resolved%2C%20Closed)%20and%20resolution%20%3D%20Fixed%20order%20by%20priority%20
> > >
> > >
> >

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

[Anton Vinogradov]

> - Distributed environment tests [2] (Nikolay Izhikov, Anton
> Vinogradov, Ivan Daschinskiy)
> Will all related issues be included in the 2.10?
We're at the final preparations phase. Going to start the merge discussion
soon.

On Wed, Nov 11, 2020 at 4:48 PM Alexey Zinoviev 
wrote:

> Yes, Model Export/Import for ML will be finished, now it's ready, but under
> testing on my side.
>
> ср, 11 нояб. 2020 г. в 16:08, Nikolay Izhikov :
>
> > I suggest to include CDC feature to the 2.10 scope.
> >
> > > 11 нояб. 2020 г., в 16:06, Maxim Muzafarov 
> > написал(а):
> > >
> > > Igniters,
> > >
> > >
> > > Can you clarify the issue statuses according to the Apache Ignite
> > > Roadmap [1] and the 2.10 Apache Ignite Release? Here are some major
> > > issues which are expected to be included in 2.10 with the unknown
> > > status:
> > >
> > > - Distributed environment tests [2] (Nikolay Izhikov, Anton
> > > Vinogradov, Ivan Daschinskiy)
> > > Will all related issues be included in the 2.10?
> > >
> > > - Native persistence defragmentation [6][7] (Anton Kalashnikov, Sergey
> > Chugunov)
> > > Are we on the last mile with this for 2.10?
> > >
> > > - Consistency-related improvements for atomic caches [3] (Alexey
> > Scherbakov)
> > > Do we have the JIRA issue? Will the issue be included in 2.10?
> > >
> > > - Tombstone objects during rebalancing [4] (Alexey Scherbakov)
> > > The issue [4] is in progress state. Will it be finished prior to code
> > freeze?
> > >
> > > - SQL runtime statistics (Konstantin Orlov)
> > > Do we have an IEP for this or JIRA issue?
> > >
> > > - ML Model export/import [5] (Alexey Zinoviev)
> > > - Will the issue be finished?
> > >
> > >
> > > [1]
> > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+Roadmap
> > > [2]
> >
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-56%3A+Distributed+environment+tests
> > > [3]
> >
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-12+Make+ATOMIC+Caches+Consistent+Again
> > > [4] https://issues.apache.org/jira/browse/IGNITE-11704
> > > [5] https://issues.apache.org/jira/browse/IGNITE-6642
> > > [6] https://issues.apache.org/jira/browse/IGNITE-13143
> > > [7]
> >
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-47%3A+Native+persistence+defragmentation
> > >
> > > On Tue, 10 Nov 2020 at 15:58, Maxim Muzafarov 
> wrote:
> > >>
> > >> Folks,
> > >>
> > >> I've created the release page on the Confluence. Feel free to mail in
> > >> case of any errors.
> > >>
> > >> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.10
> > >>
> > >> On Fri, 6 Nov 2020 at 17:56, Maxim Muzafarov 
> wrote:
> > >>>
> > >>> Igniters,
> > >>>
> > >>>
> > >>> Let's finalize the discussion [1] about the next upcoming major
> Apache
> > >>> Ignite 2.10  release. The major improvements related to the proposed
> > >>> release:
> > >>> - Improvements for partition clearing related parts
> > >>> - Add tracing of SQL queries.
> > >>> - CPP: Implement Cluster API
> > >>> - .NET: Thin client: Transactions
> > >>> - .NET: Thin Client: Continuous Query
> > >>> - Java Thin client Kubernetes discovery
> > >>>
> > >>> etc.
> > >>> Total: 166 RESOLVED issues [2].
> > >>>
> > >>>
> > >>> Let's start the discussion about Time and Scope, and also I propose
> > >>> myself as the release manager of the Apache Ignite 2.10. If you'd
> like
> > >>> to lead this release, please, let us know, I see no problems to chose
> > >>> a better candidate.
> > >>>
> > >>>
> > >>> Proposed release timeline:
> > >>>
> > >>> Scope Freeze: December 10, 2020
> > >>> Code Freeze: December 24, 2020
> > >>> Voting Date: January 18, 2021
> > >>> Release Date: January 25, 2021
> > >>>
> > >>>
> > >>> Proposed release scope:
> > >>> [2]
> > >>>
> > >>>
> > >>> WDYT?
> > >>>
> > >>>
> > >>> [1]
> >
> http://apache-ignite-developers.2346864.n4.nabble.com/2-9-1-release-proposal-tp49769p49867.html
> > >>> [2]
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%202.10%20and%20status%20in%20(Resolved%2C%20Closed)%20and%20resolution%20%3D%20Fixed%20order%20by%20priority%20
> >
> >
>

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

[Alexey Zinoviev]

Yes, Model Export/Import for ML will be finished, now it's ready, but under
testing on my side.

ср, 11 нояб. 2020 г. в 16:08, Nikolay Izhikov :

> I suggest to include CDC feature to the 2.10 scope.
>
> > 11 нояб. 2020 г., в 16:06, Maxim Muzafarov 
> написал(а):
> >
> > Igniters,
> >
> >
> > Can you clarify the issue statuses according to the Apache Ignite
> > Roadmap [1] and the 2.10 Apache Ignite Release? Here are some major
> > issues which are expected to be included in 2.10 with the unknown
> > status:
> >
> > - Distributed environment tests [2] (Nikolay Izhikov, Anton
> > Vinogradov, Ivan Daschinskiy)
> > Will all related issues be included in the 2.10?
> >
> > - Native persistence defragmentation [6][7] (Anton Kalashnikov, Sergey
> Chugunov)
> > Are we on the last mile with this for 2.10?
> >
> > - Consistency-related improvements for atomic caches [3] (Alexey
> Scherbakov)
> > Do we have the JIRA issue? Will the issue be included in 2.10?
> >
> > - Tombstone objects during rebalancing [4] (Alexey Scherbakov)
> > The issue [4] is in progress state. Will it be finished prior to code
> freeze?
> >
> > - SQL runtime statistics (Konstantin Orlov)
> > Do we have an IEP for this or JIRA issue?
> >
> > - ML Model export/import [5] (Alexey Zinoviev)
> > - Will the issue be finished?
> >
> >
> > [1]
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+Roadmap
> > [2]
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-56%3A+Distributed+environment+tests
> > [3]
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-12+Make+ATOMIC+Caches+Consistent+Again
> > [4] https://issues.apache.org/jira/browse/IGNITE-11704
> > [5] https://issues.apache.org/jira/browse/IGNITE-6642
> > [6] https://issues.apache.org/jira/browse/IGNITE-13143
> > [7]
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-47%3A+Native+persistence+defragmentation
> >
> > On Tue, 10 Nov 2020 at 15:58, Maxim Muzafarov  wrote:
> >>
> >> Folks,
> >>
> >> I've created the release page on the Confluence. Feel free to mail in
> >> case of any errors.
> >>
> >> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.10
> >>
> >> On Fri, 6 Nov 2020 at 17:56, Maxim Muzafarov  wrote:
> >>>
> >>> Igniters,
> >>>
> >>>
> >>> Let's finalize the discussion [1] about the next upcoming major Apache
> >>> Ignite 2.10  release. The major improvements related to the proposed
> >>> release:
> >>> - Improvements for partition clearing related parts
> >>> - Add tracing of SQL queries.
> >>> - CPP: Implement Cluster API
> >>> - .NET: Thin client: Transactions
> >>> - .NET: Thin Client: Continuous Query
> >>> - Java Thin client Kubernetes discovery
> >>>
> >>> etc.
> >>> Total: 166 RESOLVED issues [2].
> >>>
> >>>
> >>> Let's start the discussion about Time and Scope, and also I propose
> >>> myself as the release manager of the Apache Ignite 2.10. If you'd like
> >>> to lead this release, please, let us know, I see no problems to chose
> >>> a better candidate.
> >>>
> >>>
> >>> Proposed release timeline:
> >>>
> >>> Scope Freeze: December 10, 2020
> >>> Code Freeze: December 24, 2020
> >>> Voting Date: January 18, 2021
> >>> Release Date: January 25, 2021
> >>>
> >>>
> >>> Proposed release scope:
> >>> [2]
> >>>
> >>>
> >>> WDYT?
> >>>
> >>>
> >>> [1]
> http://apache-ignite-developers.2346864.n4.nabble.com/2-9-1-release-proposal-tp49769p49867.html
> >>> [2]
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%202.10%20and%20status%20in%20(Resolved%2C%20Closed)%20and%20resolution%20%3D%20Fixed%20order%20by%20priority%20
>
>

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

[Nikolay Izhikov]

I suggest to include CDC feature to the 2.10 scope.

> 11 нояб. 2020 г., в 16:06, Maxim Muzafarov  написал(а):
> 
> Igniters,
> 
> 
> Can you clarify the issue statuses according to the Apache Ignite
> Roadmap [1] and the 2.10 Apache Ignite Release? Here are some major
> issues which are expected to be included in 2.10 with the unknown
> status:
> 
> - Distributed environment tests [2] (Nikolay Izhikov, Anton
> Vinogradov, Ivan Daschinskiy)
> Will all related issues be included in the 2.10?
> 
> - Native persistence defragmentation [6][7] (Anton Kalashnikov, Sergey 
> Chugunov)
> Are we on the last mile with this for 2.10?
> 
> - Consistency-related improvements for atomic caches [3] (Alexey Scherbakov)
> Do we have the JIRA issue? Will the issue be included in 2.10?
> 
> - Tombstone objects during rebalancing [4] (Alexey Scherbakov)
> The issue [4] is in progress state. Will it be finished prior to code freeze?
> 
> - SQL runtime statistics (Konstantin Orlov)
> Do we have an IEP for this or JIRA issue?
> 
> - ML Model export/import [5] (Alexey Zinoviev)
> - Will the issue be finished?
> 
> 
> [1] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+Roadmap
> [2] 
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-56%3A+Distributed+environment+tests
> [3] 
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-12+Make+ATOMIC+Caches+Consistent+Again
> [4] https://issues.apache.org/jira/browse/IGNITE-11704
> [5] https://issues.apache.org/jira/browse/IGNITE-6642
> [6] https://issues.apache.org/jira/browse/IGNITE-13143
> [7] 
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-47%3A+Native+persistence+defragmentation
> 
> On Tue, 10 Nov 2020 at 15:58, Maxim Muzafarov  wrote:
>> 
>> Folks,
>> 
>> I've created the release page on the Confluence. Feel free to mail in
>> case of any errors.
>> 
>> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.10
>> 
>> On Fri, 6 Nov 2020 at 17:56, Maxim Muzafarov  wrote:
>>> 
>>> Igniters,
>>> 
>>> 
>>> Let's finalize the discussion [1] about the next upcoming major Apache
>>> Ignite 2.10  release. The major improvements related to the proposed
>>> release:
>>> - Improvements for partition clearing related parts
>>> - Add tracing of SQL queries.
>>> - CPP: Implement Cluster API
>>> - .NET: Thin client: Transactions
>>> - .NET: Thin Client: Continuous Query
>>> - Java Thin client Kubernetes discovery
>>> 
>>> etc.
>>> Total: 166 RESOLVED issues [2].
>>> 
>>> 
>>> Let's start the discussion about Time and Scope, and also I propose
>>> myself as the release manager of the Apache Ignite 2.10. If you'd like
>>> to lead this release, please, let us know, I see no problems to chose
>>> a better candidate.
>>> 
>>> 
>>> Proposed release timeline:
>>> 
>>> Scope Freeze: December 10, 2020
>>> Code Freeze: December 24, 2020
>>> Voting Date: January 18, 2021
>>> Release Date: January 25, 2021
>>> 
>>> 
>>> Proposed release scope:
>>> [2]
>>> 
>>> 
>>> WDYT?
>>> 
>>> 
>>> [1] 
>>> http://apache-ignite-developers.2346864.n4.nabble.com/2-9-1-release-proposal-tp49769p49867.html
>>> [2] 
>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%202.10%20and%20status%20in%20(Resolved%2C%20Closed)%20and%20resolution%20%3D%20Fixed%20order%20by%20priority%20

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

[Maxim Muzafarov]

Igniters,


Can you clarify the issue statuses according to the Apache Ignite
Roadmap [1] and the 2.10 Apache Ignite Release? Here are some major
issues which are expected to be included in 2.10 with the unknown
status:

- Distributed environment tests [2] (Nikolay Izhikov, Anton
Vinogradov, Ivan Daschinskiy)
Will all related issues be included in the 2.10?

- Native persistence defragmentation [6][7] (Anton Kalashnikov, Sergey Chugunov)
Are we on the last mile with this for 2.10?

- Consistency-related improvements for atomic caches [3] (Alexey Scherbakov)
Do we have the JIRA issue? Will the issue be included in 2.10?

- Tombstone objects during rebalancing [4] (Alexey Scherbakov)
The issue [4] is in progress state. Will it be finished prior to code freeze?

- SQL runtime statistics (Konstantin Orlov)
Do we have an IEP for this or JIRA issue?

- ML Model export/import [5] (Alexey Zinoviev)
- Will the issue be finished?


[1] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+Roadmap
[2] 
https://cwiki.apache.org/confluence/display/IGNITE/IEP-56%3A+Distributed+environment+tests
[3] 
https://cwiki.apache.org/confluence/display/IGNITE/IEP-12+Make+ATOMIC+Caches+Consistent+Again
[4] https://issues.apache.org/jira/browse/IGNITE-11704
[5] https://issues.apache.org/jira/browse/IGNITE-6642
[6] https://issues.apache.org/jira/browse/IGNITE-13143
[7] 
https://cwiki.apache.org/confluence/display/IGNITE/IEP-47%3A+Native+persistence+defragmentation

On Tue, 10 Nov 2020 at 15:58, Maxim Muzafarov  wrote:
>
> Folks,
>
> I've created the release page on the Confluence. Feel free to mail in
> case of any errors.
>
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.10
>
> On Fri, 6 Nov 2020 at 17:56, Maxim Muzafarov  wrote:
> >
> > Igniters,
> >
> >
> > Let's finalize the discussion [1] about the next upcoming major Apache
> > Ignite 2.10  release. The major improvements related to the proposed
> > release:
> > - Improvements for partition clearing related parts
> > - Add tracing of SQL queries.
> > - CPP: Implement Cluster API
> > - .NET: Thin client: Transactions
> > - .NET: Thin Client: Continuous Query
> > - Java Thin client Kubernetes discovery
> >
> > etc.
> > Total: 166 RESOLVED issues [2].
> >
> >
> > Let's start the discussion about Time and Scope, and also I propose
> > myself as the release manager of the Apache Ignite 2.10. If you'd like
> > to lead this release, please, let us know, I see no problems to chose
> > a better candidate.
> >
> >
> > Proposed release timeline:
> >
> > Scope Freeze: December 10, 2020
> > Code Freeze: December 24, 2020
> > Voting Date: January 18, 2021
> > Release Date: January 25, 2021
> >
> >
> > Proposed release scope:
> > [2]
> >
> >
> > WDYT?
> >
> >
> > [1] 
> > http://apache-ignite-developers.2346864.n4.nabble.com/2-9-1-release-proposal-tp49769p49867.html
> > [2] 
> > https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%202.10%20and%20status%20in%20(Resolved%2C%20Closed)%20and%20resolution%20%3D%20Fixed%20order%20by%20priority%20

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

[Maxim Muzafarov]

Folks,

I've created the release page on the Confluence. Feel free to mail in
case of any errors.

https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.10

On Fri, 6 Nov 2020 at 17:56, Maxim Muzafarov  wrote:
>
> Igniters,
>
>
> Let's finalize the discussion [1] about the next upcoming major Apache
> Ignite 2.10  release. The major improvements related to the proposed
> release:
> - Improvements for partition clearing related parts
> - Add tracing of SQL queries.
> - CPP: Implement Cluster API
> - .NET: Thin client: Transactions
> - .NET: Thin Client: Continuous Query
> - Java Thin client Kubernetes discovery
>
> etc.
> Total: 166 RESOLVED issues [2].
>
>
> Let's start the discussion about Time and Scope, and also I propose
> myself as the release manager of the Apache Ignite 2.10. If you'd like
> to lead this release, please, let us know, I see no problems to chose
> a better candidate.
>
>
> Proposed release timeline:
>
> Scope Freeze: December 10, 2020
> Code Freeze: December 24, 2020
> Voting Date: January 18, 2021
> Release Date: January 25, 2021
>
>
> Proposed release scope:
> [2]
>
>
> WDYT?
>
>
> [1] 
> http://apache-ignite-developers.2346864.n4.nabble.com/2-9-1-release-proposal-tp49769p49867.html
> [2] 
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%202.10%20and%20status%20in%20(Resolved%2C%20Closed)%20and%20resolution%20%3D%20Fixed%20order%20by%20priority%20

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

[Maxim Muzafarov]

Igniters,


Let's finalize the discussion [1] about the next upcoming major Apache
Ignite 2.10  release. The major improvements related to the proposed
release:
- Improvements for partition clearing related parts
- Add tracing of SQL queries.
- CPP: Implement Cluster API
- .NET: Thin client: Transactions
- .NET: Thin Client: Continuous Query
- Java Thin client Kubernetes discovery

etc.
Total: 166 RESOLVED issues [2].


Let's start the discussion about Time and Scope, and also I propose
myself as the release manager of the Apache Ignite 2.10. If you'd like
to lead this release, please, let us know, I see no problems to chose
a better candidate.


Proposed release timeline:

Scope Freeze: December 10, 2020
Code Freeze: December 24, 2020
Voting Date: January 18, 2021
Release Date: January 25, 2021


Proposed release scope:
[2]


WDYT?


[1] 
http://apache-ignite-developers.2346864.n4.nabble.com/2-9-1-release-proposal-tp49769p49867.html
[2] 
https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%202.10%20and%20status%20in%20(Resolved%2C%20Closed)%20and%20resolution%20%3D%20Fixed%20order%20by%20priority%20