Dmitriy,
Thank you for details. Yes it looks really troublesome to start Ignite
development with Java 9+. I am not happy to say that but even more
hacky workarounds could help us. In short term.
I will try to do an exercise of setting up development environment
from scratch to feel the real
Ivan Rakov created IGNITE-11465:
---
Summary: Multiple client leave/join events may wipe affinity
assignment history and cause transactions fail
Key: IGNITE-11465
URL:
In a standalone mode user have to specify options. He or she may use
application templates to simplify launch just like
https://github.com/apache/ignite/tree/master/examples#running-examples-on-jdk-91011
but
it is anyway required.
As a user in the past (and currently) I may say: Ignite-based (or
Yes, sure.
Ignite ML algorithms actively use data sending between nodes and in several
cases uses per class loading mechanism.
I want to exclude failures when algorithms use unserializable data or try
to send lambdas with big context etc.
>From this point of view we can just run ML examples on a
Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
If your changes can lead to this failure(s): We're grateful that you were a
volunteer to make the contribution to this project, but things change and you
may no longer be able to
