Sergey Chugunov created IGNITE-13674:
Summary: Document Persistent store defragmentation
Key: IGNITE-13674
URL: https://issues.apache.org/jira/browse/IGNITE-13674
Project: Ignite
Issue
We actually use different mappers assigned to different caches using the
same source key, eg:
public class Key
{
p,
x,
y
}
public class AffinityFunctionOne : IAffinityFunction
{
public int GetPartition(object key)
{
return PartitionHash((object as Key).p)
}
}
public class
For our case, we have a stateful instance associated with each user session,
that actually handles user requests. That stateful instance is usually
long-lived. In this case, we want the data for that instance to be stored on
other nodes - at the dispatch stage, we choose a node to host the session
Matthijs van der Graaf created IGNITE-13673:
---
Summary: Docker: EXTERNAL_LIBS not working
Key: IGNITE-13673
URL: https://issues.apache.org/jira/browse/IGNITE-13673
Project: Ignite
Alexey Zinoviev created IGNITE-13672:
Summary: [ML] Add initial JSON export/import support for all models
Key: IGNITE-13672
URL: https://issues.apache.org/jira/browse/IGNITE-13672
Project: Ignite
Could you give an example of such mapping?
If that’s possible, it might also be very helpful to see the implementation
of your mapper. Looking at the code is often the best way to understand a
use case :)
-Val
On Wed, Nov 4, 2020 at 12:29 PM Raymond Wilson
wrote:
> Actually, it's worse than
Actually, it's worse than that...
We have more than one key -> partition mapping for the same key (part of a
CQRS pattern we use).
Aren't key affinity functions essentially an API in any event?
Cheers,
Raymond.
On Wed, Nov 4, 2020 at 9:54 PM Valentin Kulichenko <
I've created a ticket for this:
https://issues.apache.org/jira/browse/IGNITE-13671
-Val
On Wed, Nov 4, 2020 at 12:53 AM Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:
> Thanks, Raymond. So the reason why you couldn't use the @AffinityKeyMapped
> annotation or the
Valentin Kulichenko created IGNITE-13671:
Summary: Support collocation based on multiple fields
Key: IGNITE-13671
URL: https://issues.apache.org/jira/browse/IGNITE-13671
Project: Ignite
Thanks, Raymond. So the reason why you couldn't use the @AffinityKeyMapped
annotation or the CacheKeyConfiguration is that collocation is based on
*two fields*, not just one field. Is my understanding correct?
If that's the case, I believe it can be easily improved by providing ways
to specify
10 matches
Mail list logo
