Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
*Test with high flaky rate in master
IgniteWalRecoveryWithCompactionTest.testLargeRandomCrash
Hi, Igniters
I've prepared an IEP for Ignite 3 Client Lifecycle [1]. The main idea is to
define client lifecycle as well as core algorithms and mechanisms used by
clients. This proposal can be used as a reference for implementation of a
new client for Ignite when dealing with such problems as:
Hello, Igniters.
I would like to start a discussion about Java Code Style Guide [1] changes that
are going to be a part of IEP-87 [2] implementation. The set of libraries and
frameworks that are going to be allowed to be used in production:
- Micronaut for REST Server [3]
-
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
+1
Checked build from sources.
Checked tests and some examples.
Found minor issue: ignite-spring-data-ext RELEASE_NOTES.txt file contains
information about version 2.2.0 instead of 2.0.0
пт, 13 мая 2022 г. в 12:59, Anton Vinogradov :
> +1
>
> On Fri, May 13, 2022 at 12:59 PM Николай Ижиков
>
Dear Igniters,
I just published IEP-89 [1] that proposes a new feature to Ignite - (point
in time recovery) PITR. I propose to implement the Consistent Cut algorithm
for this, actually I achieved a working PoC for Ignite. And based on my
research I wrote this IEP.
Let's start a discussion here.
