Yeah the key thing is to be able to be notified when all records have been updated in the cache. We've tried using IgniteLock or this too by the way (e.g. the writer locks, writes the records, unlocks).
Then the client app, internally queues all updates as they arrive from the continuous query. If it can acquire the lock, then it knows all updates have arrived (because the writer has finished). However this doesn't work either, because even though the writer has unlocked, the written records are still in transit to the continuous query (e.g. they don't exist in the internal client side queue yet) -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
