/asked by mshah/ Referring to the following from the document: "join between two PARTITIONED data sets, then you must make sure that the keys you are joining on are collocated."
What does it mean by collocated the keys partitioned dataset? Specifically around memory. By collocating in the suggested manner, is the scaling of the application limited? For example, let's say that I have a Product and for which I have a million Orders. If I had to model the Product object to have collocated the Orders, does it mean that all million Order objects will be on the same node as the 1 Product object, or are the keys on the one node, but the detailed Order objects are distributed? If, so, does this not create some sort of an upper limit? Does the same carry over, when I have a product object that needs to have a join with two types of other data, lets say orders and returns? ----- /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-tp207.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
