You don’t need to override the RendezvousAffinityFunction to do what you’re asking. Instead, if you define an affinity key to your table, it will guarantee that related records will be kept together. However, make sure your groups are not too coarse or you’ll get poor distribution across your cluster.
> On 26 Jan 2023, at 11:37, Colin Cassidy via user <user@ignite.apache.org> > wrote: > > I would like to override the Ignite AffinityFunction to delegate to Kafka's > partitioning algorithm. Possibly also the node assignment - but definitely > the partitioning > > This will allow me to ensure that events are processed local to where the > data is stored. > > I think this is possible in Ignite 2.x but there appear to be significant > changes in Ignite 3.x. Could I confirm - if I follow this path, will it be > possible to override the cache partitioning still in 3.x? > > Thanks in advance, > Colin.
