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
Hello Maxim,
My replies inline
On 11.07.2022 15:57, Maxim Muzafarov wrote:
Hello Łukasz,
One of major problems which are hard to solve without cooperation is mentioned
"split package" which is currently found in the sources.
Can you clarify details of what is the issue of having such a
Hello Łukasz,
> One of major problems which are hard to solve without cooperation is
> mentioned "split package" which is currently found in the sources.
Can you clarify details of what is the issue of having such a case? I
my understanding it will be better to consider ignite-core +
No objections to the AffinityFunctionFactory approach from my side.
I think it should be based on cacheName, not groupId.
On Mon, Jul 11, 2022 at 3:52 PM Maxim Muzafarov wrote:
> Folks,
>
> I've done research about the proposed solution and I'd like to discuss
> with you a possible options we
Folks,
I've done research about the proposed solution and I'd like to discuss
with you a possible options we may have. After we agreed on a solution
design I'll create a new IEP with everything we've discussed above.
So, let's consider the most completed case:
the RendezvousAffinityFunction with
Still don't understand how type id can help me to obtain valid mapper from
key to int32. Especially when we are talking about non-jvm languages.
пн, 11 июл. 2022 г., 12:33 Николай Ижиков :
> Pavel.
>
> > It is not cryptic, it is very straightforward and builds on existing
> binary type
Pavel.
> It is not cryptic, it is very straightforward and builds on existing binary
> type mechanism.
I see the Ivan’s point here.
As I said earlier - It must be absolutely clear for user - PA works or not.
With the logic you propose it will be hiding inside Ignite machinery and logs.
>
