I've prepared a PR, please have a look:
https://github.com/apache/ignite/pull/9817
On Mon, Feb 7, 2022 at 6:37 PM Ivan Daschinsky wrote:
> I see potential in this feature, especially if we use something like
> continuous query. Stale clients can consume a lot of resources and it is
> worth kick
My congratulations, Pavel!
чт, 10 февр. 2022 г. в 18:53, Дмитрий Сорокин :
>
> Great job Pavel, my congrats!
>
>
> Чт, 10 февр. 2022 г. в 18:29, Nikolay Izhikov :
>
> > Great news! Congratulations!
> >
> > > 10 февр. 2022 г., в 18:26, Maksim Timonin
> > написал(а):
> > >
> > > Hi Pavel,
> > >
>
Great job Pavel, my congrats!
Чт, 10 февр. 2022 г. в 18:29, Nikolay Izhikov :
> Great news! Congratulations!
>
> > 10 февр. 2022 г., в 18:26, Maksim Timonin
> написал(а):
> >
> > Hi Pavel,
> >
> > Congratulations!
> >
> > On Thu, Feb 10, 2022 at 6:16 PM Maxim Muzafarov
> wrote:
> >
> >> The
Great news! Congratulations!
> 10 февр. 2022 г., в 18:26, Maksim Timonin
> написал(а):
>
> Hi Pavel,
>
> Congratulations!
>
> On Thu, Feb 10, 2022 at 6:16 PM Maxim Muzafarov wrote:
>
>> The Project Management Committee (PMC) for Apache Ignite has invited
>> Pavel Pereslegin to become a
Hi Pavel,
Congratulations!
On Thu, Feb 10, 2022 at 6:16 PM Maxim Muzafarov wrote:
> The Project Management Committee (PMC) for Apache Ignite has invited
> Pavel Pereslegin to become a committer and we are pleased to announce that
> he has accepted.
>
> He made a lot of major contributions to
Congrats, Pasha!
чт, 10 февр. 2022 г. в 18:16, Maxim Muzafarov :
> The Project Management Committee (PMC) for Apache Ignite has invited
> Pavel Pereslegin to become a committer and we are pleased to announce that
> he has accepted.
>
> He made a lot of major contributions to the Apache Ignite
The Project Management Committee (PMC) for Apache Ignite has invited
Pavel Pereslegin to become a committer and we are pleased to announce that
he has accepted.
He made a lot of major contributions to the Apache Ignite codebase
like a snapshot restore procedure, batch update operation to the
Guys,
+1 to await merge of the Calcite SQL engine before code-freeze phase
and release branch cutting. Other features and fixes can be awaited
too, it's discussable.
But the 2.12 branch was cut on October 15, 2021. There are many fixes
and features that were merged into the master during this
> I «vote» for more frequent releases.
+1
Hotfixes, eg. 2.12.1, should be released asap (no need to wait for 2.13).
And it's ok to release 2.13 without fixes planned for 2.12.1 since not all
users are affected but some wait for features like "Consistency check &
repair".
On Thu, Feb 10, 2022
Maxim, i think that more frequent releases are useful.
Ready to release branch means that it passed all known tests and also have an
appropriate votes.
More code changes creates more difficulties in final tests and sometimes
migration.
No need to switch between neighbor minor versions for user
Hi, guys!
Ignite 2.12 was released on 17th Jan. And here is a plan to release 2.13 on
28 Mar. It is only 2.5 months between those versions. IMHO, it's better to
have more time between releases:
1. We had some bug reports after releasing 2.11, and it can be worth
waiting for users feedback about
11 matches
Mail list logo
