Hello Igniters !
In the process of Ignite usage i found that some part of Compute functionality
are thread unsafe and seems was designed with such limitations initially.
Example : one (client, but it doesn`t matter at all) instance is shared between
numerous of fabric, all of them calls
Hi Ivan, Pavel
Thank you for updating the wiki page.
Yes, label do help to find newbie issues.
My thoughts related to the Board is to provide a different perspective to
find and filter issues. The Kanban board or the Backlog board help in
finding issues at Epic / Version level. I observed that
Hi Maxim et al,
thank you!
The rest of the documentation tasks for important features are also
completed.
Nevertheless, there are still some items (the ones on my list that do not
have any doc tasks) that can be done for the 2.10 release.
If you want them to be included, I will try to provide
Igor Sapego created IGNITE-14075:
Summary: Python client incorrect hash code calculation for classes
as composite keys
Key: IGNITE-14075
URL: https://issues.apache.org/jira/browse/IGNITE-14075
Ivan Daschinskiy created IGNITE-14074:
-
Summary: Add ability to skip affinity tests for testing with older
ignite versions.
Key: IGNITE-14074
URL: https://issues.apache.org/jira/browse/IGNITE-14074
Vladislav Pyatkov created IGNITE-14073:
--
Summary: False alarm to lose all transaction nodes
Key: IGNITE-14073
URL: https://issues.apache.org/jira/browse/IGNITE-14073
Project: Ignite
Hi,
Saikat, will "newbie" label work fine for you? I am curious what
benefits of having a board do you see? For example I can think it can
be useful if someone would like to see if there is much activity with
such tickets. Is it interesting for someone?
2021-01-24 12:20 GMT+03:00, Pavel Tupitsyn
Ivan Daschinskiy created IGNITE-14072:
-
Summary: Remove copy-paste of response for different versions
Key: IGNITE-14072
URL: https://issues.apache.org/jira/browse/IGNITE-14072
Project: Ignite
Yaroslav Molochkov created IGNITE-14071:
---
Summary: .NET: Ignite messaging interoperability
Key: IGNITE-14071
URL: https://issues.apache.org/jira/browse/IGNITE-14071
Project: Ignite
Stanislav,
> I think the most compatibility impact will be on the in-memory caches with
> SQL and without explicitly specified inline sizes.
I don't think that this is `true` compatibility issue. But I think we
should at least mentioned it on our documentation pages and in the
release notes.
Denis Garus created IGNITE-14070:
Summary: Protecting a snapshot from from unauthorized changes
Key: IGNITE-14070
URL: https://issues.apache.org/jira/browse/IGNITE-14070
Project: Ignite
11 matches
Mail list logo