Hi Tejas, I don't see anything obvious in the plan. Note that when you join, you still have to scan one of the sides, so if intermediate datasets after applying conditions are still large, performance can be not very good. Joins are applied in the order they appear in the plan, so you can go through the execution flow and find out where is the bottleneck.
-Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Affinity-tp9744p10013.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
