Hello! SQL query planner will not understand the locality if you use surrogate value as affinity key.
Maybe you need to define your own affinity function (extends RendezvousAffinityFunction) which will map keys to partitions. I'm not sure that it will help query planner though. Regards, -- Ilya Kasnacheev вт, 27 апр. 2021 г. в 09:01, Pavel Tupitsyn <ptupit...@apache.org>: > Hi William, > > Can you describe the use case and domain model in more detail? > > 1. AffinityKey is used to colocate some data with other data. > What do you achieve with user-id being the affinity key? > > 2. If you'd like to put all users for a given tenant/group > to the same node for efficiency, then use tenant-id as the user > affinity key. > UUID is fine, no need for extra logic with ints. > > On Tue, Apr 27, 2021 at 5:33 AM William.L <wil...@gmail.com> wrote: > >> Came across this statement in the Data Partitioning documents: >> >> "The affinity function determines the mapping between keys and partitions. >> Each partition is identified by a number from a limited set (0 to 1023 by >> default)." >> >> Looks like there is no point for adding another layer of mapping unless I >> am >> going for a smaller number. >> Are there other ways in ignite to get more locality for subset of the >> data? >> >> >> >> >> -- >> Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >> >
