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

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

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

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

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

[BLOG] Apache Ignite Extensions

Hi, I have published a blog on Apache Ignite Extensions and about migration of existing integration modules to new Ignite Extensions repository. https://samaitra.blogspot.com/2020/08/apache-ignite-extensions.html Please review and share if you have any feedback. Regards, Saikat

Ignite-extensions repository structure

Nikolay, Saikat, Igniters, I started migrating the OSGi modules to the ignite-extensions repository and I've got some questions regarding the ignite-extensions project: - We agreed that ignite extensions have their own release cycle, so why do we reference a -snapshot version of Igni

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

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

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

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

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

Apache Ignite Extensions - aiex

Hi Team, Do we have latest version of code for below repo ? there are still some open issues. If we already have fixes for them could you please provide the same. https://github.com/sumeet70/aiex major issue: Websocket connection error when running Thanks and Regards, Kamlesh Joshi "Confident

Re: [BLOG] Apache Ignite Extensions

and the summary of this undergoing project. Keep it up! - Denis On Sat, Aug 8, 2020 at 1:37 PM Saikat Maitra wrote: > Hi, > > I have published a blog on Apache Ignite Extensions and about migration of > existing integration modules to new Ignite Extensions repositor

Re: [BLOG] Apache Ignite Extensions

and the summary of this undergoing project. Keep it up! > > - > Denis > > > On Sat, Aug 8, 2020 at 1:37 PM Saikat Maitra > wrote: > > > Hi, > > > > I have published a blog on Apache Ignite Extensions and about migration > of > > exis

Re: Ignite-extensions repository structure

20 г., в 13:24, Alexey Goncharuk > написал(а): > > Nikolay, Saikat, Igniters, > > I started migrating the OSGi modules to the ignite-extensions repository > and I've got some questions regarding the ignite-extensions project: > > - We agreed that ignite extensio

Re: Ignite-extensions repository structure

Nikolay, > > I thought the extensions should be tested against the latest released > Ignite version > > It seems, we should try to keep extension Ignite version agnostic. > If it impossible, then yes, we should use latest Ignite version. > I doubt it's possible at least for OSGi: the published art

Re: Ignite-extensions repository structure

build using the nightly SNAPSHOT version of ignite-core modules. Here is the discussion thread related to the release process: http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-dependencies-and-release-process-for-Ignite-Extensions-td44478.html 2. I am thinking we can keep the extensions

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

[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: Apache Ignite Extensions - aiex

Hi Kamlesh, Nice web console. I see it for the first time. Mentioned repo is not part of Apache Ignite project yet. Probably author of the extensions Sumeet Singh may help with answering this question. Sincerely, Dmitriy Pavlov вт, 29 янв. 2019 г. в 19:50, : > Hi Team, > > Do we have latest ve

Re: Apache Ignite Extensions - aiex

Hi Kamlesh, Have you tried Web Console as an alternative? It's workable and production ready and is maintained by the community. https://ignite.apache.org/addons.html#web-console - Denis On Tue, Jan 29, 2019 at 8:50 AM wrote: > Hi Team, > > Do we have latest version of code for below repo ? t

Ignite extensions - ignite-spring-data release.

Hello, Igniters. Since the migration of Ignite Spring Data modules to extensions, thin client support for Spring Data integration was implemented. - [1]. To make this feature available for users, I propose to start the release process of the following modules: * ignite-spring-data * ignite-

[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: 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

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

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

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

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

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

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: Ignite extensions - ignite-spring-data release.

+1 > 18 нояб. 2020 г., в 14:38, Mikhail Petrov написал(а): > > Hello, Igniters. > > Since the migration of Ignite Spring Data modules to extensions, thin client > support for Spring Data integration was implemented. - [1]. > > To make this feature available for users, I propose to start the r

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

Are we keeping the original names of theses Spring modules? In separate threads I saw that the names of other extensions end with “ext”. Also, how about making a single release of all the extensions that were migrated from the main Ignite repo. There are many of them waiting for this to happen. Sa

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

Denis, I omitted "-ext" for simplicity. Currently, this suffix is present in the name of  all Spring Data integration 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-exten

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

uffix is present in > the name of all Spring Data integration 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

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

rently, this suffix is present in >> the name of all Spring Data integration modules [1], [2], [3]. >> >> [1] - >> >> https://github.com/apache/ignite-extensions/tree/master/modules/spring-data-2.2-ext >> >> [2] - >> >> https://github.co

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

t; > > On Wed, Nov 18, 2020 at 8:00 AM Mikhail Petrov > > wrote: > > > >> Denis, > >> > >> I omitted "-ext" for simplicity. Currently, this suffix is present in > >> the name of all Spring Data integration modules [1], [2], [3]. > >

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

;>> Saikat >>> >>> >>> >>> >>> >>> >>> >>> On Wed, Nov 18, 2020 at 8:00 AM Mikhail Petrov >>> wrote: >>> >>>> Denis, >>>> >>>> I omitted "-ext" for simpli

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

mel-ext >>> ignite-jms11-ext >>> ignite-kafka-ext >>> >>> It will be great if we can release all these modules also together. >>> >>> Regards, >>> Saikat >>> >>> >>> >>> >>> >>&

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

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.

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.

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.

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

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

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

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

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

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

IGNITE-12362 Migrate MQTT module to ignite-extensions

Hi, I have created PRs for the following jira issue. https://issues.apache.org/jira/browse/IGNITE-12362 IGNITE-12362 Migrate MQTT module to ignite-extensions PRs https://github.com/apache/ignite-extensions https://github.com/apache/ignite/pull/7950 Please review and share your feedback

IGNITE-12360 Migrate Storm module to ignite-extensions

Hi, I have raised PRs for the following issue. Jira IGNITE-12360 Migrate Storm module to ignite-extensions PRs: https://github.com/apache/ignite-extensions/pull/18 https://github.com/apache/ignite/pull/8083 Please review and share feedback. Regards, Saikat

IGNITE-12363 Migrate Camel module to ignite-extensions

Hi, I have created the following PRs for migration of camel module. Jira https://issues.apache.org/jira/browse/IGNITE-12363 PRs https://github.com/apache/ignite/pull/8132 https://github.com/apache/ignite-extensions/pull/19 Please review and share feedback. Regards, Saikat

IGNITE-12364 Migrate JMS module to ignite-extensions

Hi, I have created PR for migrating JMS module to ignite-extensions. Jira https://issues.apache.org/jira/browse/IGNITE-12355 PR https://github.com/apache/ignite/pull/8198 https://github.com/apache/ignite-extensions/pull/20 Please review and share feedback. Regards, Saikat

IGNITE-13394 Migrate Kafka module to ignite-extensions

Hi, I have raised the PR for the migration of kafka module from ignite to ignite-extensions repo. Please review and share feedback. Jira: https://issues.apache.org/jira/browse/IGNITE-13394 PR: https://github.com/apache/ignite-extensions/pull/23 https://github.com/apache/ignite/pull/8222

Migration of spring-data modules to ignite-extensions

Igniters, I propose to migrate spring-data modules from ignite main repository to ignite-extensions. Are there any objections? I've created ticket [1] and PR to both ignite [2] and ignite-extensions [3] repositories. [1] - https://issues.apache.org/jira/browse/IGNITE-13559 [2] -

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

IGNITE-12356 Migrate Flink module to ignite-extensions

Hi I have raised a PR to migrate Flink module to ignite-extensions. PR https://github.com/apache/ignite-extensions/pull/1 Jira : https://issues.apache.org/jira/browse/IGNITE-12356 Please review and share feedback. I am observing error with initialization of GridAbstractTest as

[DISCUSS] dependencies and release process for Ignite Extensions

Hello, I wanted to connect and discuss on the release process for ignite-extensions. As of today all our integrations since released together were able to run build based on latest snapshot for example the current build depends on 2.8.0-SNAPSHOT. If we are making ignite-extensions as separate

IGNITE-12356 Migrate Flink module to ignite-extensions

Hi, I have raised a PR for removal of flink module from ignite main repo. I have already moved flink module in ignite-extensions repo ( https://github.com/apache/ignite-extensions). PR https://github.com/apache/ignite/pull/7222 jira : IGNITE-12356 Migrate Flink module to ignite-extensions

IGNITE-12361 Migrate Flume module to ignite-extensions

Hi, I have raised PR for Ignite Flume migration to Ignite Extensions repo. Jira https://issues.apache.org/jira/browse/IGNITE-12361 PR https://github.com/apache/ignite-extensions/pull/4 https://github.com/apache/ignite/pull/7227 Please review and share feedback. This is part of our

IGNITE-12358 Migrate ZeroMQ module to ignite-extensions

Hi, I have raised PR for Ignite zeromq migration to Ignite Extensions repo. Jira https://issues.apache.org/jira/browse/IGNITE-12358 PR https://github.com/apache/ignite-extensions/pull/5 https://github.com/apache/ignite/pull/7240 Please review and share feedback. This is part of our

[jira] [Created] (IGNITE-12926) [ignite-extensions] build failed

Nikolay Izhikov created IGNITE-12926: Summary: [ignite-extensions] build failed Key: IGNITE-12926 URL: https://issues.apache.org/jira/browse/IGNITE-12926 Project: Ignite Issue Type: Test

IGNITE-12357 Migrate Twitter module to ignite-extensions

Hi, I have raised PRs for migration of twitter module in ignite-extensions repository. Jira https://issues.apache.org/jira/browse/IGNITE-12357 PRs https://github.com/apache/ignite-extensions/pull/12 https://github.com/apache/ignite/pull/7733 Please review and share your feedback. Regards

IGNITE-12359 Migrate RocketMQ module to ignite-extensions

Hi, I have raised PRs for the following issue: IGNITE-12359 Migrate RocketMQ module to ignite-extensions https://issues.apache.org/jira/browse/IGNITE-12359 PR https://github.com/apache/ignite-extensions/pull/14 https://github.com/apache/ignite/pull/7809 Please take a look and share feedback

IGNITE-12952 Enable travis ci for ignite-extensions

Hi, I have raised a PR to enable travis CI build. Jira : https://issues.apache.org/jira/browse/IGNITE-12952 PR : https://github.com/apache/ignite-extensions/pull/15 I need more info about how travis build was enabled for ignite repo. I tried to execute the travis CI build for ignite-extensions

Re: IGNITE-12952 Enable travis ci for ignite-extensions

Hi Maxim, Pavel Can you please share more info about how travis build was enabled for ignite repo? I tried to execute the travis CI build for ignite-extensions but I do not have sufficient access to enable the travis build for ignite-extensions repo. Regards, Saikat On Sun, May 31, 2020 at 4

Re: IGNITE-12952 Enable travis ci for ignite-extensions

n you please share more info about how travis build was enabled for > ignite repo? > > I tried to execute the travis CI build for ignite-extensions but I do not > have sufficient access to enable the travis build for ignite-extensions > repo. > > Regards, > Saikat > >

Re: IGNITE-12952 Enable travis ci for ignite-extensions

Thank you for the information Maxim. I have created the below INFRA ticket for enabling travis CI for Apache Ignite Extensions repository. https://issues.apache.org/jira/browse/INFRA-20420 Regards, Saikat On Thu, Jun 11, 2020 at 7:03 AM Maxim Muzafarov wrote: > Saikat, > > > Pl

Re: IGNITE-12952 Enable travis ci for ignite-extensions

Hi, Travis build has been enabled for ignite extensions repo. Regards, Saikat On Fri, Jun 12, 2020 at 8:50 PM Saikat Maitra wrote: > Thank you for the information Maxim. > > I have created the below INFRA ticket for enabling travis CI for Apache > Ignite Extensions repositor

Re: IGNITE-12362 Migrate MQTT module to ignite-extensions

Hi I have created PRs for the following jira issue. https://issues.apache.org/jira/browse/IGNITE-12362 IGNITE-12362 Migrate MQTT module to ignite-extensions PRs https://github.com/apache/ignite-extensions https://github.com/apache/ignite/pull/7950 Please review and share your feedback

Re: IGNITE-12362 Migrate MQTT module to ignite-extensions

IGNITE-12362 Migrate MQTT module to ignite-extensions > > PRs > https://github.com/apache/ignite-extensions > https://github.com/apache/ignite/pull/7950 > > > Please review and share your feedback. > > Regards, > Saikat > > On Sun, Jun 21, 2020 at 3:44 PM Saikat

Re: IGNITE-12362 Migrate MQTT module to ignite-extensions

ted PRs for the following jira issue. > > > > https://issues.apache.org/jira/browse/IGNITE-12362 > > > > IGNITE-12362 Migrate MQTT module to ignite-extensions > > > > PRs > > https://github.com/apache/ignite-extensions > > https://github.com/apache/ignite/

Re: IGNITE-12362 Migrate MQTT module to ignite-extensions

> Hi > > > > > > I have created PRs for the following jira issue. > > > > > > https://issues.apache.org/jira/browse/IGNITE-12362 > > > > > > IGNITE-12362 Migrate MQTT module to ignite-extensions > > > > > > PRs > > > https://github.

Re: IGNITE-12362 Migrate MQTT module to ignite-extensions

> > > > > > пт, 3 июл. 2020 г. в 21:50, Saikat Maitra : > > > > > > > Hi > > > > > > > > I have created PRs for the following jira issue. > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-12362 > >

Re: IGNITE-12360 Migrate Storm module to ignite-extensions

odule to ignite-extensions > > PRs: > https://github.com/apache/ignite-extensions/pull/18 > https://github.com/apache/ignite/pull/8083 > > Please review and share feedback. > > Regards, > Saikat >

Re: IGNITE-12360 Migrate Storm module to ignite-extensions

hanges. > > - > Denis > > > On Sun, Jul 26, 2020 at 3:28 PM Saikat Maitra > wrote: > > > Hi, > > > > I have raised PRs for the following issue. > > > > Jira IGNITE-12360 Migrate Storm module to ignite-extensions > > > > PRs: > &

Re: IGNITE-12363 Migrate Camel module to ignite-extensions

apache.org/jira/browse/IGNITE-12363 > > PRs > > https://github.com/apache/ignite/pull/8132 > https://github.com/apache/ignite-extensions/pull/19 > > Please review and share feedback. > > Regards, > Saikat >

Re: IGNITE-12363 Migrate Camel module to ignite-extensions

t; > > > https://github.com/apache/ignite/pull/8132 > > https://github.com/apache/ignite-extensions/pull/19 > > > > Please review and share feedback. > > > > Regards, > > Saikat > > >

Re: IGNITE-13394 Migrate Kafka module to ignite-extensions

ignite to > ignite-extensions repo. > > Please review and share feedback. > > Jira: https://issues.apache.org/jira/browse/IGNITE-13394 > > PR: > https://github.com/apache/ignite-extensions/pull/23 > https://github.com/apache/ignite/pull/8222 > > Regards, > Saikat >

Re: Migration of spring-data modules to ignite-extensions

Mikhail, +1 for migrate чт, 8 окт. 2020 г. в 18:34, Mikhail Petrov : > > Igniters, > > I propose to migrate spring-data modules from ignite main repository to > ignite-extensions. > > > Are there any objections? > > > I've created ticket [1] and PR to both

Re: Migration of spring-data modules to ignite-extensions

ules from ignite main repository to >> ignite-extensions. >> >> >> Are there any objections? >> >> >> I've created ticket [1] and PR to both ignite [2] and ignite-extensions >> [3] repositories. >> >> >> [1] - https://issues.apache.

Re: Migration of spring-data modules to ignite-extensions

ake a look? > > > 9 окт. 2020 г., в 11:54, Nikita Amelchev > написал(а): > > > > Mikhail, > > > > +1 for migrate > > > > чт, 8 окт. 2020 г. в 18:34, Mikhail Petrov : > >> > >> Igniters, > >> > >> I propose t

Re: Migration of spring-data modules to ignite-extensions

писал(а): >>> >>> Mikhail, >>> >>> +1 for migrate >>> >>> чт, 8 окт. 2020 г. в 18:34, Mikhail Petrov : >>>> >>>> Igniters, >>>> >>>> I propose to migrate spring-data modules from ignite main repo

Re: Migration of spring-data modules to ignite-extensions

. в 12:10, Nikolay Izhikov : >> >>>  +1. >>> >>>  Saikat, can you, please, take a look? >>> >>>>  9 окт. 2020 г., в 11:54, Nikita Amelchev >>>  написал(а): >>>>  Mikhail, >>>> >>>>  +1 for migrate >

Re: Migration of spring-data modules to ignite-extensions

Hello! I mean the Apache Ignite 2.9 release and Ignite Extensions 1.0 release. Once we get that in the wild and gather a few months of feedback (or lack thereof) then we can go on with it. Regards, -- Ilya Kasnacheev пт, 9 окт. 2020 г. в 12:42, Nikolay Izhikov : > Ilya, we should m

Re: Migration of spring-data modules to ignite-extensions

Ilya, I haven't meant that removal of spring-data from Ignite main repository should be done before the 2.9 release and be included in it. Migration of spring-data to ignite-extensions could help us to make SpringData integration updates available for users earlier then the next I

Re: Migration of spring-data modules to ignite-extensions

Ilya. My understanding is the following - there is no such thing as «Ignite Extensions release» We can and should release each module separately. You can take as an example - spring-boot-autoconfigure extension release. I made it without releasing any other modules. This mean - we can release

Re: Migration of spring-data modules to ignite-extensions

+1 I said about it few months ago. пт, 9 окт. 2020 г., 15:13 Nikolay Izhikov : > Ilya. > > My understanding is the following - there is no such thing as «Ignite > Extensions release» > We can and should release each module separately. > > You can take as an example - spri

Re: Migration of spring-data modules to ignite-extensions

ng is the following - there is no such thing as «Ignite > Extensions release» > We can and should release each module separately. > > You can take as an example - spring-boot-autoconfigure extension release. > I made it without releasing any other modules. > > This mean - we can

Re: Migration of spring-data modules to ignite-extensions

How do we release all the modules that have already been moved to the extensions repository? https://github.com/apache/ignite-extensions/tree/master/modules For instance, when 2.9 comes out and the users start bumping up their Ignite versions in pom.xml, what should they set for Kafka, camel, etc

Re: Migration of spring-data modules to ignite-extensions

Hi Nikolay, I have reviewed the PR and shared my comments. Ilya, My thoughts are that as soon the ignite 2.9.0 is released we should be able to release the ignite-extensions module 1st version pointing to ignite-core 2.9.0 version. So, for example ignite-flink-ext version 1.0.0 will be

Re: Migration of spring-data modules to ignite-extensions

lya, I haven't meant that removal of spring-data from Ignite main > repository should be done before the 2.9 release and be included in it. > > Migration of spring-data to ignite-extensions could help us to make > SpringData integration updates available for users earlier then the n

Re: Migration of spring-data modules to ignite-extensions

Saikat, Thanks a lot for the review. Anyone else want to review PR [1] with migration of spring-data to ignite-extensions repository? [1] - https://github.com/apache/ignite-extensions/pull/25 On 10.10.2020 07:15, Saikat Maitra wrote: Hi Nikolay, I have reviewed the PR and shared my

[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

  1   2   3   >