/commented by dmitriy setrakyan/

I also want to add that there are only 2 ways to solve this problem
efficiently:

1. using /REPLICATED/ caches to store some data. This way you can do joins
between /replicated/ and /partitioned/ caches at will.
2. choosing a proper collocation strategy for /partitioned/ caches.

A much slower alternative would be to move large data sets around to do
joins, but that is specifically avoided in Ignite as it will be very slow
and offers no performance advantage over disk-based databases.

----- 
/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-tp207p209.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Reply via email to