Hi, Igniters
ignite-spark3.2-ext is ready for release. We have to make some steps to do
that:
- Create a branch
- Run some jobs on github
https://github.com/apache/ignite-extensions/blob/master/DEVNOTES.md
Who can help me with that?
--
Best Regards, Ivan
Guys, any more feedback?
On Tue, Oct 18, 2022 at 12:42 PM Aleksandr Polovtsev <
alexpolovt...@gmail.com> wrote:
> My guess is that it reduces the node shutdown time. We may want to keep it
> for compatibility purposes, because I'm afraid that changing the default
> behaviour is not that easy.
>
>
Hi, Stan!
>> Say, I have an ATOMIC and TRANSACTIONAL caches in my system, and I need
to change them at the same time
Looks very unreliable. Which guarantees users expect from Ignite in this
case? For example - transaction rollbacks but atomic change (within this
tx) succeeds, and vice versa. I'm
>> WDYT?
+1
On Tue, Oct 25, 2022 at 11:40 AM Stanislav Lukyanov
wrote:
> Nikita,
>
> The system property isn't really the problem, right? The problem is the
> default behavior?
> Do you suggest that the future behavior change will be added to the
> release notes?
> Can you add a proposed release
Nikita,
The system property isn't really the problem, right? The problem is the default
behavior?
Do you suggest that the future behavior change will be added to the release
notes?
Can you add a proposed release note text to the ticket so that we are on the
same page about what will be announce
