Ok. So this means that the index maintenance is done in the background. Is there some kind of flag that stops the index usage by any queries executed after the transaction commit and before the indexes are completely rebuilt? If not, would the queries that use these indexes give wrong results?
Assuming T1 is the transaction that updated the data and after it committed a background thread(?) started rebuilding the data. Another parallel request tries to query the cache such that one or more indexes get used. Would this query use stale indexes and lead to incorrect results or not use any indexes at all? Thanks. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Index-Maintenance-During-Transactions-tp10088p10110.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
