Ignite Extensions compilation on jdk < 17

ticket (and at least provide a couple of words why we need it). Thank you for understanding. [1]: https://github.com/apache/ignite-extensions/commit/8f50f512ac48fe8be9660b4c78e99a55a7a41ae2 [2]: https://github.com/apache/ignite-extensions/commit/49cec55354df85ad592ed14d28d2e1dda53e072b [3]: https

Re: Spring 6 support for ignite extensions

e: Hello everyone. I've created an epic to implement spring 6 support for ignite extensions. https://issues.apache.org/jira/browse/IGNITE-22096 Spring 5 support is ending(and has already ended for some modules). And not all spring-extensions work correctly in the spring 6 environment. In

Re: Spring 6 support for ignite extensions

> On Thu, Apr 25, 2024 at 11:31 PM Nusrat Shakarov > wrote: > > > Hello everyone. > > > > I've created an epic to implement spring 6 support for ignite extensions. > > https://issues.apache.org/jira/browse/IGNITE-22096 > > > > Spring 5 support is ending(

Re: Spring 6 support for ignite extensions

but it is fine to change that major version for the module On Thu, Apr 25, 2024 at 11:31 PM Nusrat Shakarov wrote: > Hello everyone. > > I've created an epic to implement spring 6 support for ignite extensions. > https://issues.apache.org/jira/browse/IGNITE-22096 > > Sp

Spring 6 support for ignite extensions

Hello everyone. I've created an epic to implement spring 6 support for ignite extensions. https://issues.apache.org/jira/browse/IGNITE-22096 Spring 5 support is ending(and has already ended for some modules). And not all spring-extensions work correctly in the spring 6 environment. In the

Re: Ignite Extensions

preparing an initial release of the ML extension. Just thinking about creating a new thread and here you are :) The release branch is ready, I just need to prepare artifacts and upload them to staging. Then I am going to start the vote thread. https://github.com/apache/ignite-extensions/tree

Re: Ignite Extensions

t; > > > > > https://github.com/apache/ignite-extensions/tree/release/ignite-ml-ext-1.0.0 > > > > пн, 22 янв. 2024 г. в 18:15, Stephen Darlington >: > > > >> Hi all, > >> > >> With Ignite 2.16 now out, is there any movement towards releas

Re: Ignite Extensions

ou are :) > The release branch is ready, I just need to prepare artifacts and upload > them to staging. Then I am going to start the vote thread. > > > https://github.com/apache/ignite-extensions/tree/release/ignite-ml-ext-1.0.0 > > пн, 22 янв. 2024 г. в 18:15, Stephen Darlingto

Re: Ignite Extensions

/ignite-extensions/tree/release/ignite-ml-ext-1.0.0 пн, 22 янв. 2024 г. в 18:15, Stephen Darlington : > Hi all, > > With Ignite 2.16 now out, is there any movement towards releasing some of > the Ignite Extensions? > > We have a question in the user mailing list about the ML

Ignite Extensions

Hi all, With Ignite 2.16 now out, is there any movement towards releasing some of the Ignite Extensions? We have a question in the user mailing list about the ML extensions, which were moved from core to extensions. And I'd like to see the SpringBoot extensions released so that we can su

Re: [DISCUSSION] Move the ignite-yarn, ignite-geospatial, ignite-schedule to the Ignite Extensions

Hello! Can you arrange that? Regards, -- Ilya Kasnacheev чт, 19 мая 2022 г. в 09:20, Maxim Muzafarov : > Ilya, > > Should we start a formal vote about the ignite-schedule deletion? > > On Mon, 16 May 2022 at 14:28, Ilya Kasnacheev > wrote: > > > > Hello! > > > > In my opinion, the ignite-sch

Re: [DISCUSSION] Move the ignite-yarn, ignite-geospatial, ignite-schedule to the Ignite Extensions

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

Re: [DISCUSSION] Move the ignite-yarn, ignite-geospatial, ignite-schedule to the Ignite Extensions

Ilya, Should we start a formal vote about the ignite-schedule deletion? On Mon, 16 May 2022 at 14:28, Ilya Kasnacheev wrote: > > Hello! > > In my opinion, the ignite-schedule module needs to be dropped - it has bad > API, outdated GPL dependency and in general is out of focus of Ignite. > > Rega

[ANNOUNCE] Apache Ignite Extensions Released

The Apache Ignite Community is pleased to announce the release of the following Apache Ignite Extensions: - Ignite AWS Extension 1.0.0 - Ignite Azure Extension 1.0.0 - Ignite GCE Extension 1.0.0 - Ignite Spring Data Extension 2.0.0 - Ignite Spring Session Extension 1.0.0 - Ignite Zookeeper Ip

Re: [DISCUSSION] Move the ignite-yarn, ignite-geospatial, ignite-schedule to the Ignite Extensions

Hello! In my opinion, the ignite-schedule module needs to be dropped - it has bad API, outdated GPL dependency and in general is out of focus of Ignite. Regards, -- Ilya Kasnacheev пт, 13 мая 2022 г. в 17:51, Maxim Muzafarov : > Folks, > > I've found that the following modules are rarely used

Re: [DISCUSSION] Move the ignite-yarn, ignite-geospatial, ignite-schedule to the Ignite Extensions

ignite-mesos? 在 2022/5/13 22: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 Ignite being released. It seems we can safely move all of them to the Extensions project. The list: - igni

Re: [DISCUSSION] Move the ignite-yarn, ignite-geospatial, ignite-schedule to the Ignite Extensions

+1 > 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 Ignite being > released. It seems we can safely move all of them to the Extensions > project

[DISCUSSION] Move the ignite-yarn, ignite-geospatial, ignite-schedule to the Ignite Extensions

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?

Re: [DISCUSSION] Move ignite-hibernate modules to the Ignite Extensions

Folks, I've moved the hibernate modules to the Ignite Extension project, however, we can't deploy them to the Maven Central since they have the LGPL dependencies. This is also mentioned in the documentation [1]. Users must build them manually from the sources to use. Another problem I've faced wi

Re: [DISCUSSION] Move ignite-hibernate modules to the Ignite Extensions

Folks, I've created a task: https://issues.apache.org/jira/browse/IGNITE-16908 On Tue, 26 Apr 2022 at 23:16, Nikita Amelchev wrote: > > +1 > > вт, 26 апр. 2022 г. в 17:22, Anton Vinogradov : > > > > +1 > > > > On Tue, Apr 26, 2022 at 4:45 PM Николай Ижиков wrote: > > > > > +1 > > > > > > > 26 а

Re: [DISCUSSION] Move ignite-hibernate modules to the Ignite Extensions

+1 вт, 26 апр. 2022 г. в 17:22, Anton Vinogradov : > > +1 > > On Tue, Apr 26, 2022 at 4:45 PM Николай Ижиков wrote: > > > +1 > > > > > 26 апр. 2022 г., в 16:24, Maxim Muzafarov > > написал(а): > > > > > > Hello Igniters, > > > > > > > > > Currently we have a batch of ignite-hibernate modules whi

Re: [DISCUSSION] Move ignite-hibernate modules to the Ignite Extensions

+1 On Tue, Apr 26, 2022 at 4:45 PM Николай Ижиков wrote: > +1 > > > 26 апр. 2022 г., в 16:24, Maxim Muzafarov > написал(а): > > > > Hello Igniters, > > > > > > Currently we have a batch of ignite-hibernate modules which provide > > Hibernate second-level cache (L2 cache) implementation based on

Re: [DISCUSSION] Move ignite-hibernate modules to the Ignite Extensions

+1 > 26 апр. 2022 г., в 16:24, Maxim Muzafarov написал(а): > > 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

[DISCUSSION] Move ignite-hibernate modules to the Ignite Extensions

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

RE: Re: Move Azure, AWS, GCE to the ignite-extensions

Thank you it will very help us > Hello Stephen, > > I'm planning to release the extensions soon. Tests are OK, however, > some TC Suites still need to be configured. > > On Wed, 26 Jan 2022 at 21:07, Stephen Darlington > wrote: > > > > Do we know what happened with this thread? I just saw a quest

Re: Move Azure, AWS, GCE to the ignite-extensions

>> [1] > >>> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteExtensions_Tests_Gce&branch_IgniteExtensions_Tests=%3Cdefault%3E&tab=buildTypeStatusDiv > >>> [2] > >>> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24

Re: Move Azure, AWS, GCE to the ignite-extensions

d=IgniteExtensions_Tests_Gce&branch_IgniteExtensions_Tests=%3Cdefault%3E&tab=buildTypeStatusDiv >>> [2] >>> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_GceOld&branch_IgniteTests24Java8=ignite-2.12&tab=buildTypeStatusDiv >>> &g

Re: Move the Zookeeper IP-finder to the ignite-extensions

ср, 22 дек. 2021 г. в 12:09, Sergei Ryzhov : > > > > > Hi, igniters, > > > > > > I've created an issue [1] to move the zookeeper IP-finder to the > > > ignite-extensions. The motivation is the same as with migration of > > > cloud-based IP-find

Re: Move the Zookeeper IP-finder to the ignite-extensions

>>> it. >>> This code may break unnoticed if Zookeeper IP Finder is not built/tested >>> on >>> every commit. >>> >>> Regards, >>> -- >>> Ilya Kasnacheev >>> >>> >>> ср, 22 дек. 2021 г. в 12:09, Sergei

Re: Move the Zookeeper IP-finder to the ignite-extensions

ore code base is dedicated for enabling >> it. >> This code may break unnoticed if Zookeeper IP Finder is not built/tested >> on >> every commit. >> >> Regards, >> -- >> Ilya Kasnacheev >> >> >> ср, 22 дек. 2021 г. в 12:09, Serg

Re: Move the Zookeeper IP-finder to the ignite-extensions

ev > > > ср, 22 дек. 2021 г. в 12:09, Sergei Ryzhov : > > > Hi, igniters, > > > > I've created an issue [1] to move the zookeeper IP-finder to the > > ignite-extensions. The motivation is the same as with migration of > > cloud-based IP-finders - to remove

Re: Move the Zookeeper IP-finder to the ignite-extensions

12:09, Sergei Ryzhov : > Hi, igniters, > > I've created an issue [1] to move the zookeeper IP-finder to the > ignite-extensions. The motivation is the same as with migration of > cloud-based IP-finders - to remove integration dependency of the > release cycle on Ignite re

Re: Move the Zookeeper IP-finder to the ignite-extensions

Sergei, Please make sure this will not break the Ducktests. AFAIK, we have zookeeper tests there. On Wed, Dec 22, 2021 at 12:09 PM Sergei Ryzhov wrote: > Hi, igniters, > > I've created an issue [1] to move the zookeeper IP-finder to the > ignite-extensions. The motivation is

Move the Zookeeper IP-finder to the ignite-extensions

Hi, igniters, I've created an issue [1] to move the zookeeper IP-finder to the ignite-extensions. The motivation is the same as with migration of cloud-based IP-finders - to remove integration dependency of the release cycle on Ignite releases. Also, the log4j dependency with vulnerabil

Re: Move Azure, AWS, GCE to the ignite-extensions

buildTypeStatusDiv > > [2] > > https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_GceOld&branch_IgniteTests24Java8=ignite-2.12&tab=buildTypeStatusDiv > > > > On Mon, 25 Oct 2021 at 14:22, Maxim Muzafarov wrote: > >> > >>

Re: Move Azure, AWS, GCE to the ignite-extensions

/ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_GceOld&branch_IgniteTests24Java8=ignite-2.12&tab=buildTypeStatusDiv > > On Mon, 25 Oct 2021 at 14:22, Maxim Muzafarov wrote: >> >> Folks, >> >> I've moved the azure, gce, aws modules to the ignite

Re: Move Azure, AWS, GCE to the ignite-extensions

iv [2] https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_GceOld&branch_IgniteTests24Java8=ignite-2.12&tab=buildTypeStatusDiv On Mon, 25 Oct 2021 at 14:22, Maxim Muzafarov wrote: > > Folks, > > I've moved the azure, gce, aws modules to

Re: [DISCUSS] Release spring-tx-ext and spring-cache-ext Ignite extensions

> 1. Release the spring-data-commons 1.1.0, spring-tx 1.0.0, > > spring-cache 1.0.0 modules with separate source packages: > > > > /ignite/ignite-extensions/ignite-spring-data-commons/1.1.0/[src] > > /ignite/ignite-extensions/ignite-spring-tx-ext/1.0.0/[src] > > /ignite/ign

Re: Move Azure, AWS, GCE to the ignite-extensions

Folks, I've moved the azure, gce, aws modules to the ignite-extensions project. https://issues.apache.org/jira/browse/IGNITE-15541 Building the modules in the ignite-extension project will prepare an appropriate release zip file containing all the necessary dependencies: - ignite-aws-ex

Re: Move Azure, AWS, GCE to the ignite-extensions

nload.cgi >>>>>> <https://ignite.apache.org/download.cgi#extensions>). If I’m trying to >>>>>> start a cluster on Azure, how does that work? Do I need to build my own >>>>>> server? >>>>>> >>>>>> Regard

Re: Move Azure, AWS, GCE to the ignite-extensions

>> start a cluster on Azure, how does that work? Do I need to build my own >>>>> server? >>>>> >>>>> Regards, >>>>> Stephen >>>>> >>>>>> On 13 Oct 2021, at 11:35, Nikita Amelchev wrote: >>>>>> >>&

Re: Move Azure, AWS, GCE to the ignite-extensions

t;>> Stephen >>>> >>>>> On 13 Oct 2021, at 11:35, Nikita Amelchev wrote: >>>>> >>>>> +1 to migrate and include to the Ignite 2.12 scope >>>>> >>>>> пн, 20 сент. 2021 г. в 17:09, Denis Magd

Re: Move Azure, AWS, GCE to the ignite-extensions

021 г. в 17:09, Denis Magda : > >>>> > >>>> Perfect, thanks, Maxim! > >>>> > >>>> - > >>>> Denis > >>>> > >>>> > >>>> On Mon, Sep 20, 2021 at 8:29 AM

Re: Move Azure, AWS, GCE to the ignite-extensions

ite 2.12 scope >>> >>> пн, 20 сент. 2021 г. в 17:09, Denis Magda : >>>> >>>> Perfect, thanks, Maxim! >>>> >>>> - >>>> Denis >>>> >>>> >>>> On Mon, Sep 20, 2021 at 8:29 AM Maxim Muzaf

Re: Move Azure, AWS, GCE to the ignite-extensions

t;> - > >> Denis > >> > >> > >> On Mon, Sep 20, 2021 at 8:29 AM Maxim Muzafarov wrote: > >> > >>> Folks, > >>> > >>> > >>> I've created an issue [1] to move all cloud-based IP-finders to the > &g

Re: Move Azure, AWS, GCE to the ignite-extensions

thanks, Maxim! >> >> - >> Denis >> >> >> On Mon, Sep 20, 2021 at 8:29 AM Maxim Muzafarov wrote: >> >>> Folks, >>> >>> >>> I've created an issue [1] to move all cloud-based IP-finders to the >>> ignite-exte

Re: Move Azure, AWS, GCE to the ignite-extensions

+1 Those parts still very optional nowadays. > On 20 Sep 2021, at 15:29, Maxim Muzafarov wrote: > > Folks, > > > I've created an issue [1] to move all cloud-based IP-finders to the > ignite-extensions. The motivation is the same as with migration of > Spring

Re: Move Azure, AWS, GCE to the ignite-extensions

d an issue [1] to move all cloud-based IP-finders to the > > ignite-extensions. The motivation is the same as with migration of > > Spring Data integration - to remove integration dependency of the > > release cycle on Ignite releases. > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-15541 > > -- Best wishes, Amelchev Nikita

Re: [DISCUSS] Release spring-tx-ext and spring-cache-ext Ignite extensions

1. Release the spring-data-commons 1.1.0, spring-tx 1.0.0, > spring-cache 1.0.0 modules with separate source packages: > > /ignite/ignite-extensions/ignite-spring-data-commons/1.1.0/[src] > /ignite/ignite-extensions/ignite-spring-tx-ext/1.0.0/[src] > /ignite/ignite-extensions/ignite-spr

Re: Migration of CacheSpringStoreSessionListener to ignite-extensions

1 г. в 18:51, Mikhail Petrov : > > > > Igniters, I propose to migrate CacheSpringStoreSessionListener to > > ignite-extensions in the ignite-spring-tx module as part of Spring > > Transactions integration migration. It also helps to > > 1. Make the ignite-spring module

Re: [DISCUSS] Release spring-tx-ext and spring-cache-ext Ignite extensions

packages: /ignite/ignite-extensions/ignite-spring-data-commons/1.1.0/[src] /ignite/ignite-extensions/ignite-spring-tx-ext/1.0.0/[src] /ignite/ignite-extensions/ignite-spring-cache-ext/1.0.0/[src] (The spring-data-commons 1.0.0 was included in the ignite-spring-data-all-ext/1.0.0 source package) 2

Re: Migration of CacheSpringStoreSessionListener to ignite-extensions

Mikhail, +1 to migrate and include to the ignite-spring-tx 1.0.0, Ignite 2.12 scopes Please, create an issue. пн, 4 окт. 2021 г. в 18:51, Mikhail Petrov : > > Igniters, I propose to migrate CacheSpringStoreSessionListener to > ignite-extensions in the ignite-spring-tx module as part

Migration of CacheSpringStoreSessionListener to ignite-extensions

Igniters, I propose to migrate CacheSpringStoreSessionListener to ignite-extensions in the ignite-spring-tx module as part of Spring Transactions integration migration. It also helps to 1. Make the ignite-spring module responsible only for parsing XML configurations. 2. Reduce the number of

[DISCUSS] Release spring-tx-ext and spring-cache-ext Ignite extensions

Igniters, Since Ignite 2.11 has been released the following extension modules can be released too: spring-cache-ext spring-tx-ext I want to be a release manager for these if nobody minds. The release process can be started after checking documentation. -- Best wishes, Amelchev Nikita

Re: Move Azure, AWS, GCE to the ignite-extensions

Perfect, thanks, Maxim! - Denis On Mon, Sep 20, 2021 at 8:29 AM Maxim Muzafarov wrote: > Folks, > > > I've created an issue [1] to move all cloud-based IP-finders to the > ignite-extensions. The motivation is the same as with migration of > Spring Data integration

Move Azure, AWS, GCE to the ignite-extensions

Folks, I've created an issue [1] to move all cloud-based IP-finders to the ignite-extensions. The motivation is the same as with migration of Spring Data integration - to remove integration dependency of the release cycle on Ignite releases. [1] https://issues.apache.org/jira/browse/I

[jira] [Created] (IGNITE-14621) Ignite Extensions: change spring-data-*-ext modules names to align with a directory name

Amelchev Nikita created IGNITE-14621: Summary: Ignite Extensions: change spring-data-*-ext modules names to align with a directory name Key: IGNITE-14621 URL: https://issues.apache.org/jira/browse/IGNITE

[jira] [Created] (IGNITE-14570) Ignite Extensions: Add default checkpoint methods to the IgnitePerformanceStatisticsHandler handler

Amelchev Nikita created IGNITE-14570: Summary: Ignite Extensions: Add default checkpoint methods to the IgnitePerformanceStatisticsHandler handler Key: IGNITE-14570 URL: https://issues.apache.org/jira/browse

Re: [DISCUSS] Release performance-statistics-ext, spring-data-ext and spring-tx-ext Ignite extensions

Denis, If the initial release of some of the extension happens there is no need to release each time a new Ignite version is released (if there are no changes of a particular extension). So we should release the initial release as fast as possible and do the others according to needs. This is my v

Re: [DISCUSS] Release performance-statistics-ext, spring-data-ext and spring-tx-ext Ignite extensions

Hi Maxim, I would suggest we time a release of the Ignite core and the extensions in the future. As of now, I can't switch to Ignite 2.10 only due to the Spring Data module. Not the end of the world but delays the upgrade to the new version. - Denis On Mon, Apr 5, 2021 at 6:32 AM Maxim Muzafaro

Re: [DISCUSS] Release performance-statistics-ext, spring-data-ext and spring-tx-ext Ignite extensions

Denis, There is no spring data artifact for the 2.10 release. We should prepare the release of these extensions as fast as possible. On Fri, 2 Apr 2021 at 20:06, Denis Magda wrote: > > Is this the first time we're releasing spring data 2.2 as an ext? Can't > find any version available for 2.10?

Re: [DISCUSS] Release performance-statistics-ext, spring-data-ext and spring-tx-ext Ignite extensions

Is this the first time we're releasing spring data 2.2 as an ext? Can't find any version available for 2.10? What should I use if I need Spring Data integration now for Ignite 2.10? https://mvnrepository.com/artifact/org.apache.ignite/ignite-spring-data_2.2 - Denis On Fri, Mar 26, 2021 at 12:55

[jira] [Created] (IGNITE-14456) Ignite Extensions: change copyrights to 2021

Amelchev Nikita created IGNITE-14456: Summary: Ignite Extensions: change copyrights to 2021 Key: IGNITE-14456 URL: https://issues.apache.org/jira/browse/IGNITE-14456 Project: Ignite

Re: [DISCUSS] Release performance-statistics-ext, spring-data-ext and spring-tx-ext Ignite extensions

Hi, Denis. > - How is the performance stats ext is different from the profiling tool > released in 2.10? The performance statistics extension is a script to build an HTML report. The core module collects statistics to binary files and this feature was released in 2.10. чт, 25 мар. 2021 г. в 21

Re: [DISCUSS] Release performance-statistics-ext, spring-data-ext and spring-tx-ext Ignite extensions

+1 I missed our progress on the extensions frontier. Great to see more capabilities added to the Spring framework support. Several questions (but, I fully support the release of the extensions): - How is the performance stats ext is different from the profiling tool released in 2.10? -

Re: [DISCUSS] Release performance-statistics-ext, spring-data-ext and spring-tx-ext Ignite extensions

Hello Nikita, +1 to follow your suggestion. Please let me know if you need any help. I also think the issues mentioned by you can be done in parallel and they don't block the release :-) On Thu, 25 Mar 2021 at 17:26, Nikita Amelchev wrote: > > Igniters, > > Since Ignite 2.10 has been released,

[DISCUSS] Release performance-statistics-ext, spring-data-ext and spring-tx-ext Ignite extensions

Igniters, Since Ignite 2.10 has been released, I think we can now release new extension modules: performance-statistics-ext spring-data-ext spring-tx-ext I want to be a release manager for these if nobody minds. The release process can be started after resolving a few documentation issues: htt

[jira] [Created] (IGNITE-14273) ignite-extensions: Export data from snapshot to custom format

Maxim Muzafarov created IGNITE-14273: Summary: ignite-extensions: Export data from snapshot to custom format Key: IGNITE-14273 URL: https://issues.apache.org/jira/browse/IGNITE-14273 Project

[jira] [Created] (IGNITE-14264) Ignite extensions: Ignite client cache manager may create cache with incorrect name

Mikhail Petrov created IGNITE-14264: --- Summary: Ignite extensions: Ignite client cache manager may create cache with incorrect name Key: IGNITE-14264 URL: https://issues.apache.org/jira/browse/IGNITE-14264

[jira] [Created] (IGNITE-14249) Ignite extensions: Flaky IgniteSourceConnectorTest.testEventsInjectedIntoKafkaWithoutFilter test

Mikhail Petrov created IGNITE-14249: --- Summary: Ignite extensions: Flaky IgniteSourceConnectorTest.testEventsInjectedIntoKafkaWithoutFilter test Key: IGNITE-14249 URL: https://issues.apache.org/jira/browse

[jira] [Created] (IGNITE-14213) Ignite extensions: javadoc ignitelink tag is unsupported

Mikhail Petrov created IGNITE-14213: --- Summary: Ignite extensions: javadoc ignitelink tag is unsupported Key: IGNITE-14213 URL: https://issues.apache.org/jira/browse/IGNITE-14213 Project: Ignite

Re: Ignite Extensions tests

extra incompatible node that does not belong to the test. >>> But I think we could investigate it in a separate ticket. >>> >>> Could I ask you to create separate test suite for the Spring Cache >>> extension similar to Spring Transactions for the

Re: Ignite Extensions tests

to join extra incompatible node that does not belong to the test. But I think we could investigate it in a separate ticket. Could I ask you to create separate test suite for the Spring Cache extension similar to Spring Transactions for the following PR: https://github.com/apache/ignite-extensions

Re: Ignite Extensions tests

ilar to Spring Transactions for the following PR: > https://github.com/apache/ignite-extensions/pull/42 > > [1] - https://issues.apache.org/jira/browse/IGNITE-14150 > > [2] - > https://ci.ignite.apache.org/project.html?projectId=IgniteExtensions_Tests&branch_IgniteExtens

Re: Ignite Extensions tests

to create separate test suite for the Spring Cache extension similar to Spring Transactions for the following PR:  https://github.com/apache/ignite-extensions/pull/42 [1] - https://issues.apache.org/jira/browse/IGNITE-14150 [2] - https://ci.ignite.apache.org/project.html?projectId

Re: Ignite Extensions tests

I've updated Extensions template to use only Linux agents. Will wait for ticket in master, thanks! > On 10 Feb 2021, at 01:05, Mikhail Petrov wrote: > > Hi, Petr. > > It seems that the problem is in an outdated version of the maven surefire > plugin that is us

Re: Ignite Extensions tests

Hi, Petr. It seems that the problem is in an outdated version of the maven surefire plugin that is used in ignite-extensions. I created the corresponding ticket [1]. I also faced that current ignite-extensions build is broken on windows agents - [2]. It fails with the following error

[jira] [Created] (IGNITE-14150) Update version of surefire plugin in ignite-extensions

Mikhail Petrov created IGNITE-14150: --- Summary: Update version of surefire plugin in ignite-extensions Key: IGNITE-14150 URL: https://issues.apache.org/jira/browse/IGNITE-14150 Project: Ignite

Ignite Extensions tests

Hi, Nikolay. I've created a set of tests for extensions, and part of them are failing with: JUnit4Provider.invoke:159->executeTestSet:238->executeWithRerun:273->execute:365 » NoSuchMethod java.lang.NoSuchMethodError: org.apache.maven.surefire.report.SimpleReportEntry.withException(Ljava/lang/S

Re: Access to Ignite Extensions TeamCity project

Hi, Petr. Now I have access. Thanks! пн, 25 янв. 2021 г. в 11:28, Petr Ivanov : > Hi, Sergey. > > > Check you permissions, please. > > > On 24 Jan 2021, at 21:00, Sergey D wrote: > > > > Hi Igniters, > > > > I want to start work on a ticket in ignite extension project, but it > seems > > that

Re: Access to Ignite Extensions TeamCity project

Hi, Sergey. Check you permissions, please. > On 24 Jan 2021, at 21:00, Sergey D wrote: > > Hi Igniters, > > I want to start work on a ticket in ignite extension project, but it seems > that i don`t have permission to this project in TeamCity. > "You do not have enough permissions to access pr

Access to Ignite Extensions TeamCity project

Hi Igniters, I want to start work on a ticket in ignite extension project, but it seems that i don`t have permission to this project in TeamCity. "You do not have enough permissions to access project with id IgniteExtensions_Tests" My username is stalkxt . Can you help me please? -- *Best reg

[jira] [Created] (IGNITE-14010) Ignite-extensions: KafkaIgniteSteamerSelfTest is flaky

Mikhail Petrov created IGNITE-14010: --- Summary: Ignite-extensions: KafkaIgniteSteamerSelfTest is flaky Key: IGNITE-14010 URL: https://issues.apache.org/jira/browse/IGNITE-14010 Project: Ignite

[jira] [Created] (IGNITE-14009) Ignite-extensions: PubSubStreamerSelfTest is flaky

Mikhail Petrov created IGNITE-14009: --- Summary: Ignite-extensions: PubSubStreamerSelfTest is flaky Key: IGNITE-14009 URL: https://issues.apache.org/jira/browse/IGNITE-14009 Project: Ignite

[jira] [Created] (IGNITE-14007) Ignite-extensions: ignite-kafka integration test suite fails TC build

Mikhail Petrov created IGNITE-14007: --- Summary: Ignite-extensions: ignite-kafka integration test suite fails TC build Key: IGNITE-14007 URL: https://issues.apache.org/jira/browse/IGNITE-14007

Re: Apache Ignite Extensions TeamCity project

Hi Petr, I am able to access the project. Thank you Regards, Saikat On Wed, Jan 13, 2021 at 2:17 AM Petr Ivanov wrote: > Added you to Ignite Test Managers. > Please check access level. > > > > On 13 Jan 2021, at 03:49, Saikat Maitra wrote: > > > > Hi Petr, > > > > Thank you for your response

[jira] [Created] (IGNITE-13993) Ignite-extensions: Change version of Ignite dependency to 2.11.0

Mikhail Petrov created IGNITE-13993: --- Summary: Ignite-extensions: Change version of Ignite dependency to 2.11.0 Key: IGNITE-13993 URL: https://issues.apache.org/jira/browse/IGNITE-13993 Project

[jira] [Created] (IGNITE-13992) Migrate spring-transactions integration to ignite-extensions

Mikhail Petrov created IGNITE-13992: --- Summary: Migrate spring-transactions integration to ignite-extensions Key: IGNITE-13992 URL: https://issues.apache.org/jira/browse/IGNITE-13992 Project: Ignite

Migration of Spring Cache and Spring Transactions integrations to ignite-extensions.

Igniters, I propose to migrate the Spring Transactions [1] and Spring Cache [2] integrations, that are currently stored in the ignite-spring module [3], to the ignite-extensions repository and split them as two separate modules - ignite-spring-transactions-ext and ignite-spring-cache-ext

Re: Apache Ignite Extensions TeamCity project

Added you to Ignite Test Managers. Please check access level. > On 13 Jan 2021, at 03:49, Saikat Maitra wrote: > > Hi Petr, > > Thank you for your response. I am not able to access the project due to > error > > "You do not have enough permissions to access project with id > IgniteExtensions_

Re: Apache Ignite Extensions TeamCity project

Hi Petr, Thank you for your response. I am not able to access the project due to error "You do not have enough permissions to access project with id IgniteExtensions_Tests" Can you please provide me access? My username is samaitra Regards, Saikat On Mon, Jan 11, 2021 at 2:55 AM Petr Ivanov wr

Re: Apache Ignite Extensions TeamCity project

Hi. I've refactored the hierarchy of the project and moved it here: https://ci.ignite.apache.org/project/IgniteExtensions_Tests?mode=builds Check your permissions, please. > On 11 Jan 2021, at 01:01, Saikat Maitra wrote

Apache Ignite Extensions TeamCity project

Hi, We had a project for IgniteExtensions under Tests main project in TeamCity. https://ci.ignite.apache.org/project.html?projectId=Tests_IgniteExtensions I am no longer able to access the IgniteExtensions project. Was it refactored and moved to another location? Regards, Saikat

Re: [DISCUSS] Release pub-sub Ignite extensions

Thank you Alexey for preparing the release process. We should be good to release all the migrated modules. Regards, Saikat On Fri, Nov 20, 2020 at 5:43 AM Alexey Goncharuk wrote: > Igniters, > > I think we a bit overdue for releasing already migrated extension modules > which were removed in Ig

Re: Ignite extensions - ignite-spring-data release.

s modules is to store the general > classes needed by spring-data extensions to avoid redundant code > duplication between different version of Spring Data integration. I > don't think it can be reused outside the "extensions" scope. Why can't > it be placed in the

[DISCUSS] Release pub-sub Ignite extensions

Igniters, I think we a bit overdue for releasing already migrated extension modules which were removed in Ignite 2.9. As Saikat mentioned, I suggest releasing the following modules: ignite-flink-ext ignite-flume-ext ignite-pub-sub-ext ignite-zeromq-ext ignite-twitter-ext ignite-rocketmq-ext ignite

Re: Ignite extensions - ignite-spring-data release.

hy can't it be placed in the ignite-extensions repository? Alexey, I don't mind if all extensions are released. I proposed to release spring-data modules in the first place because Spring Data thin client support is not included in any Ignite release and is crucial for some users. Regard

Re: Ignite extensions - ignite-spring-data release.

If it is not an extensions, so why do we put it to ignite-extensions repository? Do we need additional separate ignite-utilities repository for modules like spring-data-commons? > On 19 Nov 2020, at 12:08, Mikhail Petrov wrote: > > Saikat, > > spring-data-commons is a utilit

Re: Ignite extensions - ignite-spring-data release.

ion modules [1], [2], [3]. [1] - https://github.com/apache/ignite-extensions/tree/master/ modules/spring-data-2.2-ext [2] - https://github.com/apache/ignite-extensions/tree/master/ modules/spring-data-2.0-ext [3] - https://github.com/apache/ignite-extensions/tree/master/ modules/spring-

Re: Ignite extensions - ignite-spring-data release.

release all these modules also together. > >>> > >>> Regards, > >>> Saikat > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> On Wed, Nov 18, 2020 at 8:00 AM Mikhail Petro

  1   2   3   >