i>commented by yakov zhdanov/ Basically you are right, collocation can be a limiting factor. The only solution here is to choose collocation strategy wisely. For example do you have that many Products, so you need to store them in /partitioned/ cache? If this is mostly read-only and not that large dataset, it can be stored in /replicated/ cache and you will not be required to setup this collocation at all. Another more complex option is to choose another collocation key, for example artificially split Product into multiple Products (e.g. store it multiple times under different keys) and randomize Orders across these collocation keys.
----- /This post is migrated from now discontinued Apache Ignite forum at http://apacheignite.readme.io/v1.0/discuss/ -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Partitioned-dataset-join-and-large-number-of-related-keys-tp207p208.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
