Hi, Scan query doesn't lock anything. It behaves like any concurrent map - if concurrent update happened on an entry that is not visited by the iterator yet, you will then get new value.
What kind of locking are you looking for? It sounds like you want to block the whole cache, which is generally a very bad idea. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Behavior-of-ScanQuery-while-updating-tp10032p10036.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
