+1
On Tue, 16 Jul 2024 at 13:41, Alex Plehanov wrote:
>
> +1
>
> вт, 16 июл. 2024 г. в 14:14, Вячеслав Коптилин :
> >
> > +1
> >
> > Thanks,
> > S.
> >
> > вт, 16 июл. 2024 г. в 09:46, Maksim Timonin :
> >
> > > Hi Igniters,
> > >
> > > I'd like to start a voting process about moving Ignite 2.x
+1
On Fri, 21 Jun 2024 at 14:01, Alexandr Shapkin wrote:
>
> Hi Andei,
>
> +1
>
> Thanks for working on the releases.
>
> > On 21 Jun 2024, at 11:43, Nusrat Shakarov wrote:
> >
> > Hi!
> >
> > +1
> > Waiting for spring 6 support in ignite extensions!
> >
> > пт, 21 июн. 2024 г. в 10:39,
Congratulations, Iurii!
On Thu, 15 Feb 2024 at 09:31, Юрий wrote:
>
> Thank you everyone, I'm very pleased!
>
> ср, 14 февр. 2024 г. в 17:28, Pavel Pereslegin :
>
> > Congratulations, Iurii!
> >
> > ср, 14 февр. 2024 г. в 09:29, Pavel Tupitsyn :
> > >
> > > Congratulations Iurii!
> > >
> > > On
+1
On Fri, 26 Jan 2024 at 13:05, Alex Plehanov wrote:
>
> +1
>
> Checked sha512, signature. Built from sources. Checked examples.
>
> чт, 25 янв. 2024 г. в 20:56, Nikita Amelchev :
>
> >
> > +1 (binding)
> >
> > Checked compilation, tests and some examples.
> >
> > вт, 23 янв. 2024 г. в 16:57,
+1
Checked checksums, run locally.
On Sun, 24 Dec 2023 at 13:33, Anton Vinogradov wrote:
>
> +1
>
> Вс, 24 дек. 2023 г. в 15:19, Николай Ижиков :
>
> > +1 (binding)
> >
> > Отправлено с iPhone
> >
> > > 24 дек. 2023 г., в 00:13, Ivan Daschinsky
> > написал(а):
> > >
> > > +1 from me (binding)
My congratulations, Nikita!
On Tue, 21 Nov 2023 at 15:20, Dmitriy Pavlov wrote:
>
> Hello Igniters,
>
> The Project Management Committee (PMC) for Apache Ignite
> has invited Nikita Amelchev to become a member of PMC and we are pleased
> to announce that he has accepted.
>
> We appreciate his
+1
On Fri, 28 Apr 2023 at 09:54, Vladimir Steshin wrote:
>
> + 1
>
> 26.04.2023 22:51, Alex Plehanov пишет:
> > Dear Community,
> >
> > The release candidate is ready.
> >
> > I have uploaded release candidate to
> > https://dist.apache.org/repos/dist/dev/ignite/2.15.0-rc0/
> >
+1
On Wed, 29 Mar 2023 at 20:57, Alex Plehanov wrote:
>
> Dear Ignite Community!
>
> I suggest starting Apache Ignite 2.15 release activities.
>
> We've accumulated more than two hundred resolved issues [1] with new
> features and bug fixes which are waiting for release.
> The major changes
+1
On Wed, 15 Feb 2023 at 11:17, Вячеслав Коптилин
wrote:
>
> +1
>
>
> ср, 15 февр. 2023 г. в 10:21, Ivan Daschinsky :
>
> > Dear Igniters!
> >
> > This is a patch release that contains an important fix for users of
> > pyignite
> >
> > https://issues.apache.org/jira/browse/IGNITE-18788
> >
> >
/community/resources.html#ask
--
Best Regards,
Maxim Muzafarov
on behalf of Apache Ignite PMC
+1
On Mon, 12 Dec 2022 at 09:59, Andrey Gura wrote:
>
> +1
>
> On Fri, Dec 9, 2022 at 10:36 AM Nikita Amelchev wrote:
> >
> > +1
> >
> > Checked compilation, ran some examples.
> >
> > пт, 9 дек. 2022 г. в 03:53, Alexandr Shapkin :
> > >
> > > Dear Community,
> > >
> > >
> > > The release
+1
> GridClient and related classes are not used by visorcmd, but used by
> control.sh and can't be removed.
I think it should not be too difficult to migrate GridClient ->
IgniteClient and once it will happen the removal becomes be possible.
On Thu, 1 Dec 2022 at 07:30, Alex Plehanov wrote:
+1
On Tue, 15 Nov 2022 at 11:07, Anton Vinogradov wrote:
>
> +1
>
> On Tue, Nov 15, 2022 at 11:25 AM Ilya Shishkov
> wrote:
>
> > Hi,
> >
> > +1 from me.
> >
> > Checked out pyignite-0.6.0.zip with
> > pyignite-0.6.0-cp310-cp310-win_amd64.whl:
> > 1. Whl package installed via pip.
> > 2. All
, and congratulating him on the
new role in the Apache Ignite Community!
Best Regards,
Maxim Muzafarov
on behalf of Apache Ignite PMC
Folks,
I can help with releasing this module (and actually it's pretty easy
to do a release using GA), but I have some notes according to
contribution:
1. We should merge spark3.2-ext and spark-ext and separate development
streams of different versions using branches with appropriate spark
+1 (binding)
On Mon, 3 Oct 2022 at 14:05, Ivan Daschinsky wrote:
>
> +1 (binding)
>
> Checked C++ module and C++ examples compilation on windows 10 (msvc 2017)
> and ubuntu 22.04 (gcc 11.2.0).
> Checked ODBC on windows 10 and ubuntu 22.04 (unixodbc) by pyodbc and python
> script (both H2 and
Hello,
Probably you're using a wrong dependency version.
Use the repository below for the ignite-spark integration.
https://github.com/apache/ignite-extensions
On Fri, 12 Aug 2022 at 14:35, Ivan Gagarkin wrote:
>
> Hi, Igniters
> I created a pull request, but the build failed with the next
Igniters,
I'd like to discuss with you some thoughts about getting colocated
data [1] from nodes via thin client (mostly the java thin client).
- We do have partition awareness enabled for non-transactional data [2].
- We do have from now on partition awareness for caches with custom
affinity
arrass newcomers and brings a lot of frustration.
> >>
> >> It is much more safe to ban a creation of LOCAL caches from thin clients.
> >>
> >> But it can survive for a while for ignite cluster nodes, client and
> >> server.
> >>
> >> вт, 14 сент.
es inline
>
> On 11.07.2022 15:57, Maxim Muzafarov wrote:
> > Hello Łukasz,
> >
> >
> >> One of major problems which are hard to solve without cooperation is
> >> mentioned "split package" which is currently found in the sources.
> >
> > Can
> release. Is there a plan to make a 1.1.0 release?
>
> > On 14 Jul 2022, at 14:01, Maxim Muzafarov wrote:
> >
> > Hello Stephen,
> >
> > Why do you think they haven't been released yet?
> >
> > https://mvnrepository.com/artifact/org.apache.igni
Hello Stephen,
Why do you think they haven't been released yet?
https://mvnrepository.com/artifact/org.apache.ignite/ignite-spring-boot-thin-client-autoconfigure-ext/1.0.0
https://mvnrepository.com/artifact/org.apache.ignite/ignite-spring-boot-autoconfigure-ext/1.0.0
On Thu, 14 Jul 2022 at
will be able to stabilize
> osgi integration to guarantee it will work reliably if these stay.
>
> Kind regards,
> Łukasz
>
> On 4.07.2022 19:43, Maxim Muzafarov wrote:
> > Hello Łukasz,
> >
> > Nice to meet you!
> >
> > Currently there are some know
> > >>>>>>> AffinityKeyMapper (I doubt about this case);
> > >>>>>>>
> > >>>>>>> I'd like to provide a general solution that solves all the cases
> > >>>>>>> mentioned above, thus we can't discus
o be
> present on the client.
> Can you please clarify the "tricky" part?
>
> All you need is to provide AffinityFunction implementation with a proper
> class name
> (or even use nameMapper/idMapper to map to a different name), it is no
> different from the ToIntF
will work for all of the cases.
I think it is better to avoid such an issues and leave it up to a
user. Nevertheless, the worst scenario for the user would be having 2
hops on each put/get as it was before this thread.
On Thu, 7 Jul 2022 at 21:12, Maxim Muzafarov wrote:
>
> Folks,
&
> > Then simply instantiate it on the client and call `partition(Object key)`
> > on it?
> >
> > On Thu, Jul 7, 2022 at 8:32 PM Maxim Muzafarov wrote:
> >
> > > Pavel,
> > >
> > > Here is my thoughts.
> > >
> > > As I mention
cky.
> IMO we should either develop a proper feature with a good public API, or
> not add anything at all.
>
> On Thu, Jul 7, 2022 at 6:34 PM Maxim Muzafarov wrote:
>
> > Folks,
> >
> >
> > Thank you for your comments.
> >
> > First of all, I'd l
gt; +1 to have ability to specify custom affinity for PA on thin client.
> >
> > It seems to me custom affinity is a rare use-case of Ignite API.
> > Propose to have SystemProperty that can specify affinity implementation
> > for a thin client.
> >
> >
> > > 2
Hello Łukasz,
Nice to meet you!
Currently there are some known issues with the Apache Ignite OSGi
integration. We have a lack of time and knowledg to support it, so any
help are very appreciated. I also have a a plan to move this
integration to the Apache Ignite Extensions project [1] and
Igniters,
I've faced with a customer's cluster which has more than 150 nodes and
most for them are the thick-client nodes. Due to each thick-client is
a full-fledged cluster topology participant it affects the cluster
discovery machinery during the system operation and adding an
additional
Folks,
I've merged the issue
https://issues.apache.org/jira/browse/IGNITE-17180
On Thu, 16 Jun 2022 at 18:12, Nikita Amelchev wrote:
>
> +1 to remove.
>
> чт, 16 июн. 2022 г. в 07:46, Maxim Muzafarov :
> >
> > Folks,
> >
> > I've prepared the patch
On Mon, Jun 13, 2022 at 4:16 PM Maxim Muzafarov wrote:
>
> > Pavel,
> >
> >
> > I've found some minor issue with the last digits in thin client
> > version - 2.14.0.62943. The last digits is the number of hours passed
> > since 01-01-2015 [1]. Due to the last
Folks,
I've prepared the patch. Please, take a look.
https://issues.apache.org/jira/browse/IGNITE-17180
https://github.com/apache/ignite/pull/10096/files
On Fri, 10 Jun 2022 at 19:21, Maxim Muzafarov wrote:
>
> Folks,
>
> I've found the 'dev-tools' [1] directory in the projects roo
tps://github.com/apache/ignite/pull/10087/files
[3]
https://github.com/apache/ignite/pull/10087/files#diff-b5a06276719e759fe07dfe6f75d781be5f83d2215179d82bdb195ad035348214R660
On Wed, 8 Jun 2022 at 20:06, Maxim Muzafarov wrote:
>
> Folks,
>
> Make sense.
> Another tricky questio
Folks,
I've found the 'dev-tools' [1] directory in the projects root,
however, I'm not sure the reals usages of these scripts.
Can anyone clarify the purpose of existing these scripts or can we
remove them instead?
The facts about this directory:
- it hasn't been changed since 2015;
- the issue
et doesn't have
> > functionality a-la maven's 'snapshots'
> >
> > ср, 8 июн. 2022 г. в 16:07, Ivan Daschinsky :
> >
> > > Since nuget packages have been built on the same linux agent as the main
> > > release, it sounds logical to me that t
Hello Igniters,
I'd like to simplify the release build for the Apache Ignite.
My suggestion here are:
1. Mavenize the building procedure of the 'platform/donet' thin client
(use maven with Ant task)
2. Change it's versions to fit the Ignite style.
= 1. Build =
Add a pom.xml sub-project with
Folks,
Let's extend a bit the list of modules for moving to the Ignite Extensions.
The list:
- ignite-yarn
- ignite-geospatial
- ignite-mesos
- ignite-cloud
- ignite-osgi*
- ignite-schedule (deletion proposed)
On Thu, 19 May 2022 at 09:20, Maxim Muzafarov wrote:
>
> Ilya,
>
> Sho
focus of Ignite.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> пт, 13 мая 2022 г. в 17:51, Maxim Muzafarov :
>
> > Folks,
> >
> > I've found that the following modules are rarely used and haven't been
> > change for a few years, but they are released each time Ign
://ignite.apache.org/community/resources.html#ask
Regards,
Maxim Muzafarov on behalf of the Apache Ignite community.
/ignite-spring-data-ext/2.0.0/
On Tue, 17 May 2022 at 15:44, Maxim Muzafarov wrote:
>
> Hello, Igniters!
>
> Th Ignite Spring Data 2.2.0 RC1, Ignite Spring Session 1.0.0 RC1,
> Ignite Zookeeper IP Finder 1.0.0 RC1 extensions have been accepted.
>
> 3 - "+1" votes rece
Hello, Igniters!
Th Ignite Spring Data 2.2.0 RC1, Ignite Spring Session 1.0.0 RC1,
Ignite Zookeeper IP Finder 1.0.0 RC1 extensions have been accepted.
3 - "+1" votes received.
Here are the +1 votes received:
- Anton Vinogradov (binding)
- Alexey Plehanov (binding)
- Nikolay Izhikov
Folks,
I've found that the following modules are rarely used and haven't been
change for a few years, but they are released each time Ignite being
released. It seems we can safely move all of them to the Extensions
project.
The list:
- ignite-yarn
- ignite-geospatial
- ignite-schedule
WDYT?
Hello Aleksanrd,
The description looks good. A few questions below:
- Can the CLI also be run in non-interactive mode to support scripts
execution (like the WildFly it does [1])? Will it be possible though
the REST it used?
- What is the benefits and drawbacks of using REST for this tool? Are
-lgpl.xml does.
I've created an issue for that [2].
[1] https://ignite.apache.org/docs/latest/setup#enabling-modules
[2] https://issues.apache.org/jira/browse/IGNITE-16981
On Thu, 28 Apr 2022 at 15:43, Maxim Muzafarov wrote:
>
> Folks,
>
> I've created a task:
> https://issues.
Dear Community,
The release candidates are ready.
The ignite-zookeeper-ip-finder and ignite-spring-session haven't been
changed since the last vote. All the issues mentioned in the previous
vote related to the ignite-spring-data-ext have also fixed.
See the links below.
== Ignite Spring Data
Hello, Igniters!
The Ignite AWS 1.0.0 RC1, Ignite Azure 1.0.0 RC1, Ignite GCE 1.0.0 RC1
extensions have been accepted.
4 - "+1" votes received.
1 - "0" vote received.
Here are the +1 votes received:
- Anton Vinogradov (binding)
- Nikita Amelchev
- Nikolay Izhikov (binding)
- Andrey Gura
The vote is cancelled.
The following issues must be fixed:
https://issues.apache.org/jira/browse/IGNITE-16927
https://issues.apache.org/jira/browse/IGNITE-16968
released zip file, but
> "spring-data-ext" (with the same content) in the master branch.
>
>
> ср, 4 мая 2022 г. в 17:43, Andrey Gura :
>
> > +1
> >
> > On Fri, Apr 29, 2022 at 7:22 PM Nikita Amelchev
> > wrote:
> > >
> > &
Dear Community,
The release candidates are ready. See the links below.
== Ignite Spring Data Extension Module 2.2.0 ==
The release candidate is uploaded to:
https://dist.apache.org/repos/dist/dev/ignite/ignite-extensions/ignite-spring-data-ext-2.2.0-rc1/
The following Maven staging can be
Dear Community,
The release candidates are ready. See the links below.
== Ignite AWS Extension Module 1.0.0 ==
The release candidate is uploaded to:
https://dist.apache.org/repos/dist/dev/ignite/ignite-extensions/ignite-aws-ext-1.0.0-rc1
The following Maven staging can be used:
wrote:
> >
> > > +1
> > >
> > > > 26 апр. 2022 г., в 16:24, Maxim Muzafarov
> > > написал(а):
> > > >
> > > > Hello Igniters,
> > > >
> > > >
> > > > Currently we have a batch of ignite-hi
extensions?
> And use Ignite sources as dependencies?
>
> > 18 февр. 2022 г., в 00:30, Maxim Muzafarov написал(а):
> >
> > Hello Igniters,
> >
> >
> > We have a lot of Ignite extensions waiting to be released (e.g. aws,
> > gce, topology-va
Hello Igniters,
Currently we have a batch of ignite-hibernate modules which provide
Hibernate second-level cache (L2 cache) implementation based on the
Apache Ignite for different version of hibernate.
The following list of modules we have:
- ignite-hibernate_4.2
- ignite-hibernate_5.1
-
+1 (binding)
Checked parent project, versions, dependencies.
On Mon, 25 Apr 2022 at 12:06, Ilya Kasnacheev wrote:
>
> +1 (binding)
>
> Ran a slim node, built from sources, built and ran c++ node.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> пн, 25 апр. 2022 г. в 08:55, Николай Ижиков :
>
> > +1
Hello,
+1, great improvement.
On Sat, 23 Apr 2022 at 17:26, Nikita Amelchev wrote:
>
> Hello, Igniters.
>
> I propose to add a GitHub action to update documentation for released
> Ignite versions by a click. [1]
>
> For now, this is a complex manual work that requires understanding all
> the
Hello Roman,
+1 to your suggestion.
If you need any help with a review, please let me know.
On Mon, 18 Apr 2022 at 13:17, Roman Puchkovskiy
wrote:
>
> Hi guys.
>
> This thread has been hanging for quite some time (no pun intended).
> While it was hanging, CVE-2022-22965 [1] was discovered which
Agree with Anton.
Since the Ignite-3 is a completely different database and have nothing
in common with the Ignite-2 projects it seems it will be better to
have all the related stuff on its own Jira and Wiki pages.
On Mon, 21 Feb 2022 at 13:29, Anton Vinogradov wrote:
>
> Andrey,
>
> Could we
Hello Igniters,
We have a lot of Ignite extensions waiting to be released (e.g. aws,
gce, topology-validator, ignite-spring-tx-ext etc.). I think it is a
good point in time to make some kind of automation and simplify our
release process for Ignite extension modules removing manual steps
from
on the new role in
the Apache Ignite Community.
Best Regards,
Maxim Muzafarov
Nikita,
Thank you for starting this thread.
+1 for these dates, but I think it's better to start the code freeze
date when the Calcite engine will be actually merged to the master
branch.
On Tue, 8 Feb 2022 at 13:10, Nikita Amelchev wrote:
>
> Dear Ignite Community!
>
> I suggest starting
Hello,
>From my point of view, it's better to reduce the scope of features to
be supported and focus on those ones that a really important for
production e.g. Calcite for Ignite 2.x. However, talking in terms of
open-source development it's better to find a volunteer who will fix
all the issues
out where the ignite-aws-ext module is now that Ignite 2.12 is
> out.
>
> Regards,
> Stephen
>
> > On 24 Nov 2021, at 11:11, Maxim Muzafarov wrote:
> >
> > Petr,
> >
> > There is only the GCE suite left to be configured. I've created an
> >
+1
On Tue, 11 Jan 2022 at 11:31, Nikolay Izhikov wrote:
>
> +1
>
> > 11 янв. 2022 г., в 02:38, Vladimir Steshin написал(а):
> >
> > +1
> >
> > 10.01.2022 15:52, Nikita Amelchev пишет:
> >> Dear Community,
> >>
> >> The release candidate (2.12.0-rc2) is ready.
> >>
> >> I have uploaded a release
/download.cgi
Please let us know if you encounter any problems:
https://ignite.apache.org/community/resources.html#ask
Regards,
Maxim Muzafarov on behalf of the Apache Ignite community.
e.
> > >
> > https://cwiki.apache.org/confluence/display/IGNITE/Website+Development#WebsiteDevelopment-SettingUp
> > >
> > > On Tue, Dec 21, 2021 at 8:01 AM Erlan Aytpaev wrote:
> > >
> > > > Hi Maxim,
> > > >
> > > > What v
ite.
> https://cwiki.apache.org/confluence/display/IGNITE/Website+Development#WebsiteDevelopment-SettingUp
>
> On Tue, Dec 21, 2021 at 8:01 AM Erlan Aytpaev wrote:
>
> > Hi Maxim,
> >
> > What version of node js version did you use?
> >
> > On Tue, Dec 21,
nd then generate
>> > the HTML version following this updated instruction. If you have any
>> > questions, please reach out to Erlan (CC-ed).
>> >
>> > [1] https://github.com/apache/ignite-website/blob/master/_src/download.pug
>> > [2] https://cwi
te-website/blob/master/_src/download.pug
> [2] https://cwiki.apache.org/confluence/display/IGNITE/Website+Development
>
> On Tue, Dec 21, 2021 at 4:36 AM Maxim Muzafarov wrote:
>>
>> Hello, Igniters!
>>
>>
>> Thanks to everyone. The vote is closed.
>> The emergency
Hello, Igniters!
Thanks to everyone. The vote is closed.
The emergency Apache Ignite 2.11.1 release (RC2) has been accepted.
I will continue on with the release.
5 - "+1" votes received and no "0", "-1" votes.
Here are the votes received:
- Ilya Kasnacheev (binding)
- Pavel Tupitsyn
yn wrote:
> >> > Igniters,
> >> >
> >> > Looks like we need to update to 2.16, there is an additional attack
> >> vector
> >> > [1]
> >> >
> >> > [1]
> >> >
> >> https://www.lunasec.io/docs/
The second release candidate for the 2.11.1 version is ready.
Since this is an emergency release the vote will remain open for as
short an amount as time as required to vet the release. All votes are
welcome and we encourage everyone to test the release, but only PMC
votes are “officially”
Cancelling the vote.
I'll cherry-pick the following [1] to the release branch and prepare a
new RC today.
[1] https://issues.apache.org/jira/browse/IGNITE-16153
overed
> a few days later?
>
> сб, 18 дек. 2021 г. в 18:04, Maxim Muzafarov :
>
> > Folks,
> >
> >
> > I've found that LOG4J2 2.17.0 version is released [1]. According to
> > the description and risk mitigation [2] it is recommended the version
> >
buildConfiguration/Releases_ApacheIgniteMain_ReleaseBuild/6329862
>
> > On 17 Dec 2021, at 13:24, Maxim Muzafarov wrote:
> >
> > Petr,
> >
> > Thank you.
> >
> > Yes, I've added changes related to the new release build actions
> > (IGNITE-15678, IGNITE-15677). The ignite-2.
4j issues.
>
> Thanks,
> S.
>
>
> пт, 17 дек. 2021 г. в 15:20, Maxim Muzafarov :
>
> > The release candidate for the 2.11.1 version is ready.
> >
> >
> > I have uploaded a release candidate to:
> > https://dist.apache.org/repos/dist/dev/ignite/2.11.
The release candidate for the 2.11.1 version is ready.
I have uploaded a release candidate to:
https://dist.apache.org/repos/dist/dev/ignite/2.11.1-rc1/
https://dist.apache.org/repos/dist/dev/ignite/packages_2.11.1-rc1/
The following staging can be used for testing:
ration/Releases_ApacheIgniteMain_ReleaseBuild/6329822
> >> [2]
> >> https://ci.ignite.apache.org/buildConfiguration/Releases_ApacheIgniteMain_ReleaseBuild/6329824
> >>
> >>> On 17 Dec 2021, at 12:11, Maxim Muzafarov wrote:
> >>>
> >>> He
; Check the following links below.
> Looks good to me.
>
>
> чт, 16 дек. 2021 г. в 20:19, Maxim Muzafarov :
>
> > Folks,
> >
> >
> > I'm OK with this. Let's go through the fastest way we have.
> >
> >
> > Check the following links below. I'll
gt; log4j 2.16 instead of 2.14 is a quite small change that only requires a
> > "sanity" check and can be quickly released. A wider release scope requires
> > full testing, IMHO.
> >
> > Thanks,
> > S.
> >
> >
> > чт, 16 дек. 2021 г. в 16:0
Given that 2.12 is so close, my preference would be to limit the scope of
> 2.11.1 to just the log4j update. Would that help bring the vote/release date
> forward?
>
> > On 16 Dec 2021, at 12:44, Maxim Muzafarov wrote:
> >
> > Dear Ignite Community!
> >
> >
I think we can even start the vote today or tomorrow, given the severity of
> log4j issue.
>
> Pavel
>
> On Thu, Dec 16, 2021 at 3:44 PM Maxim Muzafarov wrote:
>
> > Dear Ignite Community!
> >
> > I suggest preparing the Apache Ignite 2.11.1 release and I w
Dear Ignite Community!
I suggest preparing the Apache Ignite 2.11.1 release and I want to
propose myself to be the release manager of the minor release.
* RELEASE TIMELINE *
Scope Freeze: December 16, 2021
Code Freeze: December 16, 2021
Voting Date: December 21, 2021
Release Date: December 24,
Folks,
Should we describe all the WA available for the issue [1]? There is
already a lot of information about CVE, and nevertheless, it will not
be superfluous.
[1] https://issues.apache.org/jira/browse/IGNITE-16101
On Mon, 13 Dec 2021 at 15:37, Ivan Daschinsky wrote:
>
> Unfortunately, we
+1 for the 2.11.1
On Mon, 13 Dec 2021 at 15:21, Anton Vinogradov wrote:
>
> Folks,
>
> My 200 rubles here,
> > I want to include it to the 2.12 scope.
> Why not 2.11.1 as well?
> We should provide a fixed version for current customers asap.
> 2.12 require migration, while 2.11.1 can be applied
>>>>>>>>>>> I don't understand why you are using *backwards compatibility*
> >> for
> >>>>>>>>>> completely internal things.
> >>>>>>>>>>> Why you are thinking in terms of users usage when are talking
> >
ou think we should do with this?
> > >>
> > >> сб, 27 нояб. 2021 г. в 23:32, Vyacheslav Daradur :
> > >>
> > >>> LGTM. Merged to master.
> > >>>
> > >>> Thank you for your contribution!
> > >>>
>
king change should be carried out carefully and gradually.
>
>
> On Thu, Dec 2, 2021 at 12:34 PM Maxim Muzafarov wrote:
>
> > Slava,
> >
> > Thank you for the comments.
> >
> > > Maxim, the community must provide a reasonable time interval in order to
> > noti
ons on this API).
> >
> > Perhaps, it would be nice to plan to remove the system cache on 2.14 or
> > even 2.15. What do you think?
> >
> > Thanks,
> > S.
> >
> >
> > вт, 30 нояб. 2021 г. в 13:58, Maxim Muzafarov :
> >
> > > Hello
alternative, and then complete the removal
> sometime in the future?
>
> -Val
>
> On Sun, Nov 28, 2021 at 6:49 AM Maxim Muzafarov wrote:
>
> > Igniters,
> >
> >
> > Since the legacy service grid implementation was removed [2] I'd like
> > to remove the
Igniters,
Since the legacy service grid implementation was removed [2] I'd like
to remove the ignite-sys-cache also. It is still possible that some of
Ignite plugins (e.g. security plugin) are still using this cache,
however, AFAIK this is not the reason to keep the outdated system
cache and
Folks,
This is a friendly reminder :-)
PR [1] is ready for review. Will anyone take a look?
[1] https://github.com/apache/ignite/pull/9577/files
On Sat, 20 Nov 2021 at 03:17, Maxim Muzafarov wrote:
>
> Folks,
>
>
> I've prepared the changes related to the legacy Servi
Igniters,
I'd like to propose a new internal cluster management API that will
simplify new cluster management commands creation and expose new
commands to CLI, REST, JMX Ignite interfaces without any additional
actions from the engineer adding a new command. This main goal of the
IEP is supposed
Petr,
For the RunAll - 0.2
For the RunAll(Nightly) - 1.0 (the 1.0 is better that 0.2 for sure)
On Thu, 25 Nov 2021 at 15:54, Petr Ivanov wrote:
>
> 0.2 or 1.0?
>
> > On 25 Nov 2021, at 14:34, Maxim Muzafarov wrote:
> >
> > Pert,
> >
> > I think for night
t; On 25 Nov 2021, at 14:22, Maxim Muzafarov wrote:
> >
> > Folks,
> >
> > I've merged the PR [1] to the master branch and applied scale factor
> > 0.2 to the tests that were moved to dedicated suites.
> > I've created two suites and added them to the Run.Al
Nov 2021 at 15:30, Maxim Muzafarov wrote:
>
> Igniters,
>
> Currently, there are a lot of snapshot tests running under the
> `Basic3` test suite. Since the amount of tests is actually growing it
> is not good to run them at the basic Ignite test suite.
>
> I prop
Igniters,
Currently, there are a lot of snapshot tests running under the
`Basic3` test suite. Since the amount of tests is actually growing it
is not good to run them at the basic Ignite test suite.
I propose moving all the tests to a dedicated test suite and running
them independently taking
ing test suites for extensions, please?
> I will attend to it in nearest time.
>
>
> > On 23 Nov 2021, at 17:14, Maxim Muzafarov wrote:
> >
> > Hello Petr,
> >
> > Can you assist me with configuring the GCE [1] suite on the TC
> > Extensions project? Curr
://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_GceOld_IgniteTests24Java8=ignite-2.12=buildTypeStatusDiv
On Mon, 25 Oct 2021 at 14:22, Maxim Muzafarov wrote:
>
> Folks,
>
> I've moved the azure, gce, aws modules to the ignite-extensions project.
> https://issues.apache.org/jir
1 - 100 of 759 matches
Mail list logo
