Hi Randy, There is no "must" for having indexes, but indexes in many cases can speed up the execution. If you remove index from 'salary' field in the example, it will still work, but will imply full scan. However, sometimes there can be queries that do not benefit from any indexes. Like calculating some aggregation value for the whole table, for example.
Scan queries always do the scan and they do not support indexes at all. If you need indexed search, use SQL. As for loading from the store, you're not required to finish it before query execution (i.e. it's safe to execute these two processes concurrently). However, keep in mind that for any query (SQL or scan) you need to make sure that all the data required by this query is in memory before the query is executed. So in case you're loading the data for this query, you have to wait. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Indexing-operational-performance-and-data-eviction-tp9617p9629.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
