Hi All,
I'm not sure to have well-understood Ignite affinity colocation. I have several questions. 1/ Does sql queries benefit from affinity colocation? 2/ The use case is an sql query like : SELECT SUBSET1.KEY AS SET1_KEY, SUBSET2.KEY AS SET2_KEY FROM WHOLESET AS SUBSET1, WHOLESET AS SUBSET2 WHERE SUBSET1.KEY = "key1" AND SUBSET2.KEY = "key2" AND (some other conditions) I know that items with keys "key1" and "key2" will be crossed together almost all the time and I plan to define an affinity key so: - items with "key1" and "key2" => affinity key 1 - items with "key3" and "key4" => another affinity key and so on... Does this work and will speed up the request? 3/ If I define an affinity key on an object, should the field marked also as [SqlQueryField] although it will not be part of the sql query? If yes, should it be indexed? 4/ Or, this doesn't work but it will if I split each subset in different caches and define affinity key as above. cache1 = subset items with key "key1" cache2 = subset items with key "key2" ... 5/ Or, nope, there is no way to achieve that. Regards, Stéphane Gayet
