Re: Apache Ignite 2.12 RELEASE [Time, Scope, Manager]

2021-12-15 Thread Вячеслав Коптилин
Hello,

Nikita, it seems that we have to add the following ticket
https://issues.apache.org/jira/browse/IGNITE-16127 to Apache Ignite 2.12
release.

Thanks,
S.


вт, 14 дек. 2021 г. в 09:54, Nikita Amelchev :

> +1 to move these auth issues to the next release. I will prepare RC at
> the nearest time.
>
> пн, 13 дек. 2021 г. в 16:13, Pavel Tupitsyn :
> >
> > Agree with Nikolay, let's proceed with the release.
> >
> > On Mon, Dec 13, 2021 at 3:31 PM Nikolay Izhikov 
> wrote:
> >
> > > Nikita.
> > >
> > > I don’t think IGNITE-16068 is a release blocker.
> > >
> > > 1. It only happens when authentication enabled.
> > > 2. There is at lease 2 workarounds:
> > > a. Use the same file.encoding for all Ignite nodes.
> > > b. Use only latin characters in user login.
> > >
> > > I propose to postpone this ticket and move on with the release.
> > >
> > > > 13 дек. 2021 г., в 15:28, Nikita Amelchev 
> > > написал(а):
> > > >
> > > > Hello.
> > > >
> > > > I have cherry-picked the blocked [1] to the 2.12. It updates the
> log4j
> > > > version to 2.15.
> > > >
> > > > The release is blocked by one blocker issue with auth.
> > > >
> > > > [1] https://issues.apache.org/jira/browse/IGNITE-16101
> > > > [2] https://issues.apache.org/jira/browse/IGNITE-16068
> > > >
> > > > чт, 9 дек. 2021 г. в 12:44, Nikita Amelchev :
> > > >>
> > > >> Hello, Nikolay.
> > > >>
> > > >> I have cherry-picked the issue fix.
> > > >>
> > > >> Thank you.
> > > >>
> > > >> ср, 8 дек. 2021 г. в 18:47, Nikolay Izhikov :
> > > >>>
> > > >>> Hello.
> > > >>>
> > > >>> Let’s include [1] in 2.12 scope.
> > > >>>
> > > >>> After migrations authentication processor to security API we have
> an
> > > issue.
> > > >>> Persistent data region should exists on client node if
> authentication
> > > is enabled.
> > > >>>
> > > >>> It seems very annoying for the users.
> > > >>>
> > > >>> [1] https://issues.apache.org/jira/browse/IGNITE-15969
> > > >>>
> > >  2 дек. 2021 г., в 19:50, Nikita Amelchev 
> > > написал(а):
> > > 
> > >  I would like to formally announce code freeze for 2.12.0. Only
> > >  blockers are accepted to be included to the scope. [1]
> > > 
> > >  We have one blocker issue [2] that will be fixed soon.
> > > 
> > >  [1]
> > >
> https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-P3.Stabilization
> > >  [2] https://issues.apache.org/jira/browse/IGNITE-15966
> > > 
> > >  чт, 2 дек. 2021 г. в 16:01, Nikita Amelchev  >:
> > > >
> > > > Hi, Igniters.
> > > >
> > > > The release is blocked by the auth issue [1] discussed above. The
> > > > patch will be prepared at the nearest time.
> > > >
> > > > I want to include the useful issue that adds the ability to
> configure
> > > > snapshot thread pool size if nobody minds.
> > > >
> > > > [1] https://issues.apache.org/jira/browse/IGNITE-15966
> > > > [2] https://issues.apache.org/jira/browse/IGNITE-16014
> > > >
> > > > пт, 26 нояб. 2021 г. в 11:44, Nikita Amelchev <
> namelc...@apache.org
> > > >:
> > > >>
> > > >> Hello,
> > > >>
> > > >> I want to include the issue [1] to the 2.12 scope. It fixes some
> > > >> metrics according to the JSR107.
> > > >>
> > > >> Any objections?
> > > >>
> > > >> [1] https://issues.apache.org/jira/browse/IGNITE-16002 The
> remove
> > > >> cache method should update statistics if the method returns true
> > > >>
> > > >> чт, 25 нояб. 2021 г. в 17:12, Nikita Amelchev <
> namelc...@apache.org
> > > >:
> > > >>>
> > > >>> Hello Ivan,
> > > >>>
> > > >>> +1, the issue can be cherry-picked to the 2.12.
> > > >>>
> > > >>> чт, 25 нояб. 2021 г. в 17:07, Ivan Bessonov <
> bessonov...@gmail.com
> > > >:
> > > 
> > >  Hello everyone,
> > > 
> > >  is there a chance to add this issue to the release scope? [1]
> > >  Currently, defragmentation of certain types of indexes can
> > > corrupt them.
> > >  Fix is straightforward and should not cause any problems.
> > >  Thank you!
> > > 
> > >  [1] https://issues.apache.org/jira/browse/IGNITE-15968
> > > 
> > >  вт, 23 нояб. 2021 г. в 20:44, Nikita Amelchev <
> > > namelc...@apache.org>:
> > > 
> > > > Ivan,
> > > >
> > > > I have cherry-picked the issue:
> > > > https://issues.apache.org/jira/browse/IGNITE-15767
> > > >
> > > > вт, 23 нояб. 2021 г. в 20:31, Nikolay Izhikov <
> > > nizhi...@apache.org>:
> > > >>
> > > >>> [1] https://issues.apache.org/jira/browse/IGNITE-15951
> > > >>
> > > >> Cherry-picked to 2.12
> > > >>
> > > >>> 23 нояб. 2021 г., в 16:38, Nikita Amelchev <
> > > namelc...@apache.org>
> > > > написал(а):
> > > >>>
> > > >>> Hi, +1 to cherry-pick.
> > > >>>
> > > >>> вт, 23 ноя

A new feedback has been added : 45

2021-12-15 Thread Bugyard
A new feedback has been added, go to bugyard.io to see all the details...

https://bugyard.io

A new feedback has been added 

"It should be IgniteCallable for #affinityCall instead of IgniteRunnable"   by 
timonin.maxim 

View feedback 
https://app.bugyard.io/web/app/rycqZJDyY/f/61ba2c459fe6b90014a9387c

Re: Apache Ignite 2.12 RELEASE [Time, Scope, Manager]

2021-12-15 Thread Nikita Amelchev
I have cherry-picked the issue [1] to the 2.12. It updates the log4j
version to 2.16.

Slava, thank you.

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

ср, 15 дек. 2021 г. в 14:14, Вячеслав Коптилин :
>
> Hello,
>
> Nikita, it seems that we have to add the following ticket
> https://issues.apache.org/jira/browse/IGNITE-16127 to Apache Ignite 2.12
> release.
>
> Thanks,
> S.
>
>
> вт, 14 дек. 2021 г. в 09:54, Nikita Amelchev :
>
> > +1 to move these auth issues to the next release. I will prepare RC at
> > the nearest time.
> >
> > пн, 13 дек. 2021 г. в 16:13, Pavel Tupitsyn :
> > >
> > > Agree with Nikolay, let's proceed with the release.
> > >
> > > On Mon, Dec 13, 2021 at 3:31 PM Nikolay Izhikov 
> > wrote:
> > >
> > > > Nikita.
> > > >
> > > > I don’t think IGNITE-16068 is a release blocker.
> > > >
> > > > 1. It only happens when authentication enabled.
> > > > 2. There is at lease 2 workarounds:
> > > > a. Use the same file.encoding for all Ignite nodes.
> > > > b. Use only latin characters in user login.
> > > >
> > > > I propose to postpone this ticket and move on with the release.
> > > >
> > > > > 13 дек. 2021 г., в 15:28, Nikita Amelchev 
> > > > написал(а):
> > > > >
> > > > > Hello.
> > > > >
> > > > > I have cherry-picked the blocked [1] to the 2.12. It updates the
> > log4j
> > > > > version to 2.15.
> > > > >
> > > > > The release is blocked by one blocker issue with auth.
> > > > >
> > > > > [1] https://issues.apache.org/jira/browse/IGNITE-16101
> > > > > [2] https://issues.apache.org/jira/browse/IGNITE-16068
> > > > >
> > > > > чт, 9 дек. 2021 г. в 12:44, Nikita Amelchev :
> > > > >>
> > > > >> Hello, Nikolay.
> > > > >>
> > > > >> I have cherry-picked the issue fix.
> > > > >>
> > > > >> Thank you.
> > > > >>
> > > > >> ср, 8 дек. 2021 г. в 18:47, Nikolay Izhikov :
> > > > >>>
> > > > >>> Hello.
> > > > >>>
> > > > >>> Let’s include [1] in 2.12 scope.
> > > > >>>
> > > > >>> After migrations authentication processor to security API we have
> > an
> > > > issue.
> > > > >>> Persistent data region should exists on client node if
> > authentication
> > > > is enabled.
> > > > >>>
> > > > >>> It seems very annoying for the users.
> > > > >>>
> > > > >>> [1] https://issues.apache.org/jira/browse/IGNITE-15969
> > > > >>>
> > > >  2 дек. 2021 г., в 19:50, Nikita Amelchev 
> > > > написал(а):
> > > > 
> > > >  I would like to formally announce code freeze for 2.12.0. Only
> > > >  blockers are accepted to be included to the scope. [1]
> > > > 
> > > >  We have one blocker issue [2] that will be fixed soon.
> > > > 
> > > >  [1]
> > > >
> > https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-P3.Stabilization
> > > >  [2] https://issues.apache.org/jira/browse/IGNITE-15966
> > > > 
> > > >  чт, 2 дек. 2021 г. в 16:01, Nikita Amelchev  > >:
> > > > >
> > > > > Hi, Igniters.
> > > > >
> > > > > The release is blocked by the auth issue [1] discussed above. The
> > > > > patch will be prepared at the nearest time.
> > > > >
> > > > > I want to include the useful issue that adds the ability to
> > configure
> > > > > snapshot thread pool size if nobody minds.
> > > > >
> > > > > [1] https://issues.apache.org/jira/browse/IGNITE-15966
> > > > > [2] https://issues.apache.org/jira/browse/IGNITE-16014
> > > > >
> > > > > пт, 26 нояб. 2021 г. в 11:44, Nikita Amelchev <
> > namelc...@apache.org
> > > > >:
> > > > >>
> > > > >> Hello,
> > > > >>
> > > > >> I want to include the issue [1] to the 2.12 scope. It fixes some
> > > > >> metrics according to the JSR107.
> > > > >>
> > > > >> Any objections?
> > > > >>
> > > > >> [1] https://issues.apache.org/jira/browse/IGNITE-16002 The
> > remove
> > > > >> cache method should update statistics if the method returns true
> > > > >>
> > > > >> чт, 25 нояб. 2021 г. в 17:12, Nikita Amelchev <
> > namelc...@apache.org
> > > > >:
> > > > >>>
> > > > >>> Hello Ivan,
> > > > >>>
> > > > >>> +1, the issue can be cherry-picked to the 2.12.
> > > > >>>
> > > > >>> чт, 25 нояб. 2021 г. в 17:07, Ivan Bessonov <
> > bessonov...@gmail.com
> > > > >:
> > > > 
> > > >  Hello everyone,
> > > > 
> > > >  is there a chance to add this issue to the release scope? [1]
> > > >  Currently, defragmentation of certain types of indexes can
> > > > corrupt them.
> > > >  Fix is straightforward and should not cause any problems.
> > > >  Thank you!
> > > > 
> > > >  [1] https://issues.apache.org/jira/browse/IGNITE-15968
> > > > 
> > > >  вт, 23 нояб. 2021 г. в 20:44, Nikita Amelchev <
> > > > namelc...@apache.org>:
> > > > 
> > > > > Ivan,
> > > > >
> > > > > I have cherry-picked the issue:
> > > > > https://issues.apache.org/jira/browse/IGNITE-15767