Page History

...

1. Public Ignite Java API (IgniteCache, ClientCache) for direct querying secondary indexes:
   1. Query result is Iterator<Cache.Entry<K.V>>, result data is sorted by an index conditions;
   2. Decrease an overhead on SQL stuff like query parsing, query planning, etc;
   3. Guarantee to run queries on index (Ignite SQL does not support index hints to force IndexScan operations); Actually SQL do support index hints https://ignite.apache.org/docs/latest/perf-and-troubleshooting/sql-tuning#index-hints)
   4. Clear Java syntax instead of sometimes non-intuitive Ignite SQL;
   5. Flexibility in returned fields (cache key, cache val, both, only indexed fields). It helps improve performance for some cases even more.
2. Improved public Ignite Java API for creating secondary indexes:
   1. Functional indexes with Java functional interfaces;
   2. New Java API for dynamic creation of secondary indexes;
   3. Remove SQL dependency (annotation QuerySqlField) if only index feature is required and SQL is not needed.
3. Transactional support for "select for update" index queries:
   1. User will able to update cache entries for result of an index query within same transaction.

...