[ML] IGNITE-9282 Naive Bayes task split

Hi Team, I work on implementing Naive Bayes classifiers. Withing IGNITE-9282 I implemented a Gaussian Bayes and created a PR https://github.com/apache/ignite/pull/4869 But there are already a lot of changes That's' why I'd like to create separa

[GitHub] ignite pull request #4875: IGNITE-9742 Illegal change of DiscoveryCustomEven...

GitHub user daradurvs opened a pull request: https://github.com/apache/ignite/pull/4875 IGNITE-9742 Illegal change of DiscoveryCustomEvent in GridDhtPartitionsExchangeFuture#onDone You can merge this pull request into a Git repository by running: $ git pull https://github.com

[jira] [Created] (IGNITE-9742) Illegal change of DiscoveryCustomEvent in GridDhtPartitionsExchangeFuture#onDone

Vyacheslav Daradur created IGNITE-9742: -- Summary: Illegal change of DiscoveryCustomEvent in GridDhtPartitionsExchangeFuture#onDone Key: IGNITE-9742 URL: https://issues.apache.org/jira/browse/IGNITE-9742

Danger (?) change of DiscoveryCustomEvent in GridDhtPartitionsExchangeFuture#onDone

Hi Igniters! I think I found an illegal behavior in GridDhtPartitionsExchangeFuture#onDone, the following code is called here: ((DiscoveryCustomEvent)firstDiscoEvt).customMessage(null); That means a global instance of 'DiscoveryCustomEvent' is being mutated outside discovery-spi infrastructure. I

Re: [QUESTION] SegmentAware holder initialization (fix of WAL blocked rollOver)

Anton, Thank you for your reply and clarification. I've created a ticket [1] for this fix. Can you take it, please? Probably, I have the solution for the issue described above and at the first the glance it looks not too bad. But I can't guarantee the completeness of my fix and the fact that I t

[jira] [Created] (IGNITE-9741) SegmentArchivedStorage and SegmentCompressStorage remain `iterrupted` after de-activation occurs before activation

Maxim Muzafarov created IGNITE-9741: --- Summary: SegmentArchivedStorage and SegmentCompressStorage remain `iterrupted` after de-activation occurs before activation Key: IGNITE-9741 URL: https://issues.apache.org/j

Published articles on Data streaming in Dzone and Tech@Target

Hi, We have published an article on Data streaming at Dzone. Thank you Prachi for help for publishing the article https://dzone.com/articles/data-streaming-using-apache-flink-and-apache-ignit Also wrote an post at Tech@Target about how I started with Apache Ignite https://tech.target.com/2018/0

Re: Apache Ignite 2.7 release

I fully support Dmitry's concerns. I do not see a single chance for Service Grid to be included into 2.7 scope, but we are still keeping hope alive. What for? Our experience shows, that any feature involving consensus algorithms typically take weeks to be finalized after initial public review. Yes,

Re: [Discussion] revert of commit MVCC, ignite-9320

Vladimir, I agree more with Andrey's fix in the parity test, because it disables only specific property failure. If we keep .NET parity test failed for a long time, some other contributor will introduce new property- it will begin to fail always - it is like a snowball. I hope the metrics test wi

Re: [MTCGA]: new failures in builds [1871897] needs to be handled

Folks, both tests are failed in ignite-2.7 IgniteStandByClusterTest.testSimple & IgniteChangeGlobalStateFailOverTest.testActivateDeActivateOnFixTopologyWithPut