Well, I would agree that the flag is confusing, but your understanding is not correct. When used incorrectly, this flag does breaks query result because it forces Ignite to change execution plan to more optimal. This optimization doesn't always work though (that's actually the reason why it's configurable).
-Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/NOT-IN-in-ignite-tp9861p10458.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
